and although it did run, I still saw a warning related to the server trying to remove some openapi.war from a apps/ dir. So to avoid breaking something, I kept the root filesystem as writeable for now.
I ran the manifests through Polaris and it lifts the score from a B+ to an A-.
This makes both the container and pod security context configurable and sets the default values quite restrictive.
I've been trying to get
readOnlyRootFilesystem: true
to work, and it does to some extend if you mount all volumes the server tries to write to asemptyDir
(https://stackoverflow.com/questions/57274253/how-to-exempt-a-directory-when-using-readonlyrootfilesystem-in-kubernetes). I ended up mounting:and although it did run, I still saw a warning related to the server trying to remove some openapi.war from a apps/ dir. So to avoid breaking something, I kept the root filesystem as writeable for now.
I ran the manifests through Polaris and it lifts the score from a B+ to an A-.