CODEWITHSUNDEEP
dockeropenshift
LeoR
LeoR

Reputation: 716

How to inject a configuration file into an openshift docker build (not a pod)

Before the docker build starts I am producing a configuration file which contains a lot of environment specific configuration. I don't want it in my repository because it changes frequently.

Openshift recommends for artifacts needed during a docker build to downloaded them directly from the container. Here. Since they are mostly unique for each deployment and immutably stored on the container I would like to avoid having to first push the config file to a artifact repo just to download it again from the container.

Additionally they may have sensitive data. (although that should be easy to inject via environment variables)

Is there a different way to pass small configuration files (<10KB) to the openshift docker build context?

Update: I only use openshift in this case as a docker builder and push the target to an external repository. From there the container is picked up for deployment. (The situation is we are in the middle of a migration where the target architecture is not yet defined, but some specific parts must be already used. Like Openshift for cicd)

Upvotes: 0

Views: 907

Answers (1)

Graham Dumpleton
Graham Dumpleton

Reputation: 58523

Is the configuration affecting the build, or just the deployment?

If it is just the deployment, use config maps or secrets. These can be used as source for setting environment variables, or mounted as files in the container for the deployment.

Upvotes: 1

Related Questions