Skip to content

Parameterize config file paths #12911

Closed
@emmanuel

Description

@emmanuel

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

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions