As of now, the /config/helfertool.yaml (see this line of the Dockerfile) is a single consolidated file containing all the configuration options.
When deploying with Kubernetes, we want to be able to generate a ConfigMap that contains all the configuration options in clear text and that can be mounted as a file onto the container, and Secrets that contain the credentials for e.g. the database, so we can mount them as files onto the container.
Right now we have to create one gigantic Secret that contains all the configuration options that we will mount as a file.
As of now, the
/config/helfertool.yaml(see this line of the Dockerfile) is a single consolidated file containing all the configuration options.When deploying with Kubernetes, we want to be able to generate a
ConfigMapthat contains all the configuration options in clear text and that can be mounted as a file onto the container, andSecrets that contain the credentials for e.g. the database, so we can mount them as files onto the container.Right now we have to create one gigantic
Secretthat contains all the configuration options that we will mount as a file.