Description
In order to run the controller in our environment, I need to run with readOnlyRootFilesystem: true. I know that's not officially supported (#9504). I'm not asking for support for that, I'm asking for the currently-hardcoded config file paths to take an env var if present, and use the current paths as the defaults if no env var is present.
The controller currently writes to hard-coded paths in the /etc directory: /etc/nginx/nginx.conf and /etc/nginx/lua/cfg.json. Because those directories also contain other files from the container filesystem, the combination makes it impossible to place the config file on an empty dir without significant effort.
I didn't see one, aside from the issue linked above, which is different.
Not related to a particular Kubernetes version.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Milestone
Relationships
Participants
Activity
k8s-ci-robot commentedon Feb 28, 2025
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.The
triage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
feat: Parameterize config paths. Fixes kubernetes#12911.
Gacko commentedon Mar 1, 2025
I think this is not the only thing blocking you from running Ingress NGINX with
readOnlyRootFilesystem: true. IIRC NGINX itself also requires writeable directories and I do not know if you can just mount volumes in all of these locations.github-actions commentedon Apr 1, 2025
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach
#ingress-nginx-devon Kubernetes Slack.