Description
Some customers run our containers with a read-only root filesystem (Docker & K8s). Intel currently handled this with a custom readOnlyMode.enabled flag + an initContainer, which diverges from Collab (ex-Live), where mounts are gated only by securityContext.readOnlyRootFilesystem. This could cause failures like writes to /run/volatile and nginx pid/log issues when RO is enabled.
Goal
Make Intel behave like Collab: no initContainer, mount required writable paths only when securityContext.readOnlyRootFilesystem=true, and keep behavior off otherwise. Remove the redundant flag.
Description
Some customers run our containers with a read-only root filesystem (Docker & K8s). Intel currently handled this with a custom readOnlyMode.enabled flag + an initContainer, which diverges from Collab (ex-Live), where mounts are gated only by securityContext.readOnlyRootFilesystem. This could cause failures like writes to /run/volatile and nginx pid/log issues when RO is enabled.
Goal
Make Intel behave like Collab: no initContainer, mount required writable paths only when securityContext.readOnlyRootFilesystem=true, and keep behavior off otherwise. Remove the redundant flag.