-
Notifications
You must be signed in to change notification settings - Fork 106
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
Upgrading the Helm chart on Kubernetes v1.25 fails with podDisruptionsBudget enabled #184
Comments
elchenberg
added a commit
to elchenberg/kube-mgmt
that referenced
this issue
Feb 15, 2023
Previously the chart used the deprecated apiVersion policy/v1beta1 as long as it was avaiable in the cluster. This is against the recommendation of upgrading the release to a supported apiVersion prior to upgrading the cluster to a version that removes the deprecated apiVersion: <https://helm.sh/docs/topics/kubernetes_apis/#helm-users> Closes open-policy-agent#184 Signed-off-by: elchenberg <[email protected]>
elchenberg
added a commit
to elchenberg/kube-mgmt
that referenced
this issue
Feb 16, 2023
Previously the chart used the deprecated apiVersion policy/v1beta1 as long as it was avaiable in the cluster. This is against the recommendation of upgrading the release to a supported apiVersion prior to upgrading the cluster to a version that removes the deprecated apiVersion: <https://helm.sh/docs/topics/kubernetes_apis/#helm-users> Closes open-policy-agent#184 Signed-off-by: elchenberg <[email protected]>
eshepelyuk
pushed a commit
that referenced
this issue
Feb 16, 2023
Previously the chart used the deprecated apiVersion policy/v1beta1 as long as it was avaiable in the cluster. This is against the recommendation of upgrading the release to a supported apiVersion prior to upgrading the cluster to a version that removes the deprecated apiVersion: <https://helm.sh/docs/topics/kubernetes_apis/#helm-users> Closes #184 Signed-off-by: elchenberg <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is the error message:
And this is the reason:
So my pull request from a few months ago (#172) had the order wrong:
It would have been better to do it like this:
The text was updated successfully, but these errors were encountered: