-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[kube-state-metrics] Installation failed #3228
Comments
I have the exact same error. helm: 3.7.1 |
The fields allowPrivilegeEscalation and capabilities are only defined in containerSecurityContext but the chart tries to set them in PodSecurityContext |
We do care and are generally doing tests, but everyone can make mistakes, being rude doesn't help anyone. Please use 5.3.0 or wait for 5.4.1 once #3233 is merged. |
@dotdc I sincerely apologize for my rude remarks and appreciate your quick action to fix it. |
Should be good in kube-state-metrics-5.5.0 |
Describe the bug a clear and concise description of what the bug is.
Kube-state-metrics installation failed in this new chart version
What's your helm version?
3.11.2
What's your kubectl version?
1.25.4
Which chart?
kube-state-metrics
What's the chart version?
5.4.0
What happened?
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(Deployment.spec.template.spec.securityContext): unknown field "allowPrivilegeEscalation" in io.k8s.api.core.v1.PodSecurityContext, ValidationError(Deployment.spec.template.spec.securityContext): unknown field "capabilities" in io.k8s.api.core.v1.PodSecurityContext]
What you expected to happen?
kube-state-metrics installed
How to reproduce it?
helm install kube-state-metrics prometheus-community/kube-state-metrics -n kube-system
Enter the changed values of values.yaml?
NONE
Enter the command that you execute and failing/misfunctioning.
helm install kube-state-metrics prometheus-community/kube-state-metrics -n kube-system
Anything else we need to know?
On deployments, maybe the securityContext should be under container spec, like Deployment.spec.template.spec.containers.securityContext.
https://v1-25.docs.kubernetes.io/docs/tasks/configure-pod-container/security-context/
The text was updated successfully, but these errors were encountered: