Skip to content
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

Update PodDisruptionBudget API path #2811

Closed
mbevc1 opened this issue Nov 7, 2022 · 2 comments · Fixed by kubernetes-sigs/karpenter#496
Closed

Update PodDisruptionBudget API path #2811

mbevc1 opened this issue Nov 7, 2022 · 2 comments · Fixed by kubernetes-sigs/karpenter#496
Assignees
Labels
feature New feature or request v1 Issues requiring resolution by the v1 milestone

Comments

@mbevc1
Copy link
Contributor

mbevc1 commented Nov 7, 2022

Tell us about your request

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
@mbevc1 mbevc1 added the feature New feature or request label Nov 7, 2022
@jonathan-innis
Copy link
Contributor

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

@mbevc1
Copy link
Contributor Author

mbevc1 commented Nov 7, 2022

Indeed, cheers 👍

@jonathan-innis jonathan-innis added the blocked Unable to make progress due to some dependency label Nov 8, 2022
@ellistarn ellistarn added the v1 Issues requiring resolution by the v1 milestone label Apr 18, 2023
@jonathan-innis jonathan-innis self-assigned this Aug 31, 2023
@jonathan-innis jonathan-innis removed the blocked Unable to make progress due to some dependency label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request v1 Issues requiring resolution by the v1 milestone
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants