Connect server components to enterprise systems
Connect OpenShift Dev Spaces server components to enterprise systems by injecting OpenShift Secrets and ConfigMaps into containers. Mount configuration files, credentials, and environment variables without modifying container images.
You can mount Secrets and ConfigMaps as files, as subpath volumes, or as environment variables. Each method requires specific annotations and labels on the OpenShift resource.
- Inject files from Secrets and ConfigMaps into containers
Inject an OpenShift Secret or a ConfigMap as a file into an OpenShift Dev Spaces container to provide configuration files, certificates, or credentials without embedding them in the container image. - Add individual files without replacing directories
Add individual files from an OpenShift Secret or a ConfigMap to a target directory without replacing existing contents. Use a subPath mount when the target directory already contains files that must be preserved. - Inject environment variables from Secrets and ConfigMaps
Inject configuration values from an OpenShift Secret or a ConfigMap as environment variables in an OpenShift Dev Spaces container, such as credentials, API keys, or feature flags, without modifying the container image. - Fine-tune the server
Fine-tune the OpenShift Dev Spaces server by setting environment variables or overriding properties that are not exposed through the standardCheClusterCustom Resource fields.