Skip to content
This repository has been archived by the owner on Oct 13, 2021. It is now read-only.

PDBs fail to sync when switching between maxUnavailable <> minAvailable` #74

Open
wonderhoss opened this issue Dec 10, 2018 · 1 comment

Comments

@wonderhoss
Copy link
Contributor

When a pdb changes from maxUnavailable to minAvailable or vice versa, the update fails with

      is invalid: [spec: Invalid value: policy.PodDisruptionBudgetSpec{MinAvailable:(*intstr.IntOrString)(0xc425d44200),
      Selector:(*v1.LabelSelector)(0xc425d44220), MaxUnavailable:(*intstr.IntOrString)(0xc425d44240)}:
      minAvailable and maxUnavailable cannot be both set, spec: Forbidden: updates
      to poddisruptionbudget spec are forbidden.]'
@JoelSpeed
Copy link
Contributor

I think this should be fixed now that we have implemented #77, we should add a test for this case in pkg/utils/client

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants