-
Notifications
You must be signed in to change notification settings - Fork 967
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
policy/v1beta1
has been deprecated since kubectl version 1.25
#856
Comments
This is also affecting myself when deploying aws-for-fluent-bit
|
Same issue here, just upgraded my cluster to 1.25 and I can't upgrade or even delete the node termination handler anymore |
Same here, even though the message is slightly different:
I'm actually trying to use it from the EKS Blueprints for Terraform by configuring the value set {
name = "rbac.pspEnabled"
value = false
} but I'm getting the same error. Environment:
|
Are you sure about this Chart version? The latest eks-blueprints code references 0.1.22. aws_for_fluentbit_helm_config = {
version = "0.1.24"
} After I added that, pspEnabled will be set to false by default, so it JustWorks. |
You're right, I was thinking that importing the latest version of the blueprints would have involved using the latest version of the Helm chart too, instead 0.1.21 was used, which did not have the pspEnabled flag evaluation yet. Thank you! |
The PodSecurityPolicy configuration has a dependency on
policy/v1beta1
eks-charts/stable/aws-node-termination-handler/templates/psp.yaml
Line 2 in 8e82f74
However this has been deprecated in more recent
kubectl
versions PodDisruptionBudget, PodSecurityPolicy in https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25.This is causing the
aws-node-termination-handler
to fail during installation with messagePlease, see the original issue leading to this dandi/dandi-hub#52.
The text was updated successfully, but these errors were encountered: