-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow with PodDisruptionBudgetSpec fails #10649
Comments
For reference, this is one of the examples: https://github.com/argoproj/argo-workflows/blob/master/examples/default-pdb-support.yaml To add to this, the UI throws the same error: Setting minavailable to a int (which is what I'd expect it to be) also gives the same result. The k8s docs, and the workflows docs imply that a selector might be mandatory, although an empty one should work. I tested this and got the same result. So yes, I can confirm that this doesn't work in k8s 1.25+ |
This should be fixed in #10712 |
Signed-off-by: Yuan Tang <[email protected]>
Thanks for the fix! Can you please create a new release with this fix? That would be really great! |
I am not sure if there's any plan yet but for now you it should be available in the |
BTW, |
The docs say string or int is acceptable. String seems crazy to me, but that's what the docs say! |
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
Message: Unable to create PDB resource for workflow, pod-name error: the server could not find the requested resource |
Pre-requisites
:latest
What happened/what you expected to happen?
Workflow with PodDisruptionBudgetSpec fails in Kubernetes v1.25. No pod is created.
When I do same steps in Kubernetes v1.24, it works correctly.
The
policy/v1beta1
API version of PodDisruptionBudget is no longer served as of v1.25. It might cause this issue.Steps to reproduce issue
Version
v3.4.5 or latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
This is same as default-pdb-support.yaml
Logs from the workflow controller
Logs from in your workflow's wait container
None. No pod was created.
The text was updated successfully, but these errors were encountered: