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

Upgrade PodDisruptionBudget from v1beta1 to v1 #5709

Merged
merged 9 commits into from
May 31, 2022

Conversation

barkbay
Copy link
Contributor

@barkbay barkbay commented May 30, 2022

Revives #5689 by adding a mechanism to detect which version of the policy group is available.

  • policy/v1beta1 API version of PodDisruptionBudget will no longer be served in 1.25
  • policy/v1 version is available since 1.21

The purpose of this new PR is then mostly for ECK 2.3.0 to be able to run on K8S 1.20

Note that the conversion code is not exported to k8s.io/api, which means that it's not possible to reuse the native conversion mechanism.

@barkbay barkbay added >enhancement Enhancement of existing functionality v2.3.0 labels May 30, 2022
@barkbay
Copy link
Contributor Author

barkbay commented May 30, 2022

Previous build failed with:

#13 1.149 pkg/controller/elasticsearch/nodespec/desired_nodes.go:12:2: cannot find module providing package go.elastic.co/apm: import lookup disabled by -mod=readonly

🤔

Copy link
Contributor

@thbkrkr thbkrkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@barkbay barkbay merged commit e0cc9eb into elastic:main May 31, 2022
fantapsody pushed a commit to fantapsody/cloud-on-k8s that referenced this pull request Feb 7, 2023
* Move PodDisruptionBudget from v1beta1 to v1

* Use reconciler.ReconcileResource(..) on PodDisruptionBudget

* Detect policy API version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality v2.3.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants