You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Installing kube-state-metrics via Cluster -> Settings -> Features -> Metrics -> Install fails because it does not install Pod Security Policies. I mean, the install in the UI itself succeeds, but the end result of having kube-state-metrics running fails because of PSP.
To Reproduce
Steps to reproduce the behavior:
Have cluster that enforces PSP
Install metrics
Observe how pods are not running because of PSP violations (missing)
Expected behavior
Pods start OK with PSP.
Environment (please complete the following information):
Lens Version: 2.1.3
OS: Mojave
Download from website
The text was updated successfully, but these errors were encountered:
Why isn't the Lens Metrics installation done through Helm or provide any way to change the values? It is very confusing. I want to set up the Metrics without persistent volumes, and there is no way to change the variable persistance.enabled to false from the Settings menu?
I see where's it's located on the installation, i.e. my local copy of the config, but can I extend it with more files - i.e. does the installer simply list the files and apply each that it finds? i.e. I could juts add 07-me.yml to apply it?
If not I could just edit whats there to add the PSPs I need.
@alanbchristie Yes if you add in a file to that folder (which has now moved) it will be installed as well. Otherwise I would recommend installing via helm.
Describe the bug
Installing kube-state-metrics via
Cluster -> Settings -> Features -> Metrics -> Install
fails because it does not install Pod Security Policies. I mean, the install in the UI itself succeeds, but the end result of having kube-state-metrics running fails because of PSP.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Pods start OK with PSP.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: