readOnlyRootFilesystem=true #2880
Replies: 3 comments 6 replies
-
It's for secured communication between the KEDA Metrics Server and Kuberentes apiserver |
Beta Was this translation helpful? Give feedback.
-
Summarizing: The FAQ answer says you can’t run KEDA with readOnlyRootFilesystem=true unless you create your own cert and configure metrics server to use it. However it is possible to run KEDA with readOnlyRootFilesystem=true simply by creating an emptyDir volume (default type) and mounting it to the path where, by default, metrics server writes its generated cert:
The helm command is: helm install keda kedacore/keda --namespace keda \
--set 'volumes.metricsApiServer.extraVolumes[0].name=keda-volume' \
--set 'volumes.metricsApiServer.extraVolumeMounts[0].name=keda-volume' \
--set 'volumes.metricsApiServer.extraVolumeMounts[0].mountPath=/apiserver.local.config/certificates/' \
--set 'securityContext.metricServer.readOnlyRootFilesystem=true' PR to improve FAQ answer: kedacore/keda-docs#830 |
Beta Was this translation helpful? Give feedback.
-
Answered? https://keda.sh/docs/2.15/reference/faq/#how-do-i-run-keda-with-readonlyrootfilesystemtrue |
Beta Was this translation helpful? Give feedback.
-
For security and compliance reasons we are trying to run keda with readOnlyRootFilesystem enabled
FAQs say the following:
We are struggling to understand why the metrics service needs this certificate? Can anyone please explain, or point to more detailed documentation in this area.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions