Skip to content

FR: Config file for the operatorΒ #13197

Open
@tomhjp

Description

What are you trying to do?

The operator is currently configured by flags and environment variables for global options like enabling the auth proxy. Updating these currently requires modifying the operator deployment directly, e.g. via a helm upgrade and a freshly created pod.

How should we solve this?

As the number of options grows, it might be useful to have a config file that can be updated separately from the operator deployment and without the need for restarts, e.g. something like a ConfigMap or a controller-specific configuration file like CertManager.

What is the impact of not solving this?

Without a config file, the natural solution to new config options will generally be to add more complexity to the helm chart.

Anything else?

No response

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions