You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PodDisruptionBudget is graduating from policy/v1beta1 to policy/v1. Couldn't find it tracked anywhere yet, so opening an issue :)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Avoid warnings in logs:
2022-11-07T14:23:11.721Z WARN controller API Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget {"commit": "51becf8-dirty"}
2022-11-07T14:29:45.724Z WARN controller API Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget {"commit": "51becf8-dirty"}
2022-11-07T14:35:40.728Z WARN controller API Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget {"commit": "51becf8-dirty"}
Are you currently working around this issue?
No.
Additional Context
No response
Attachments
No response
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
There's a couple API path upgrades that are being tracked as part of #2354. API upgrades are a bit tricky for client-side since we want to have wide support for all our users
Tell us about your request
PodDisruptionBudget is graduating from
policy/v1beta1
topolicy/v1
. Couldn't find it tracked anywhere yet, so opening an issue :)Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Avoid warnings in logs:
Are you currently working around this issue?
No.
Additional Context
No response
Attachments
No response
Community Note
The text was updated successfully, but these errors were encountered: