Menu
We are using one namespace for the develop environment and one for the staging environment. Inside each one of this namespaces we have several configMaps and secrets but there are a lot of share variables between the two environments so we will like to have a common file for those.
Is there a way to have a base configMap into the default namespace and refer to it using something like:
- envFrom: - configMapRef: name: default.base-config-map If this is not possible, is there no other way other than duplicate the variables through namespaces?
449
As being an API object kubernetes secrets can not be shared between the namespaces,so the other way would be to copy the Kubernetes secrets from one namespace to another namespace and we can achieve this by using the pipe “|” operator.
Namespaces are used to isolate resources within the control plane. For example if we were to deploy a pod in two different namespaces, an administrator running the “get pods” command may only see the pods in one of the namespaces. The pods could communicate with each other across namespaces however.
If you want to view the binaryData keys (and their values) in a ConfigMap, you can run kubectl get configmap -o jsonpath='{. binaryData}' <name> . Starting with Kubernetes v1. 23, kubectl supports the --from-env-file argument to be specified multiple times to create a ConfigMap from multiple data sources.
If you need to copy a secret from one namespace to another, you will get an error because the 'namespace' is still embedded in the yaml and cannot be overridden with the final apply. By using a sed replacement as a filter, you can do a quick transformation and get your desired result.
They cannot be shared, because they cannot be accessed from a pods outside of its namespace. Names of resources need to be unique within a namespace, but not across namespaces.
Workaround it is to copy it over.
kubectl get secret <secret-name> --namespace=<source-namespace> --export -o yaml \ | kubectl apply --namespace=<destination-namespace> -f - kubectl get configmap <configmap-name> --namespace=<source-namespace> --export -o yaml \ | kubectl apply --namespace=<destination-namespace> -f - The --export flag was deprecated in 1.14 Instead following command can be used:
kubectl get secret <secret-name> --namespace=<source-namespace> -o yaml \ | sed 's/namespace: <from-namespace>/namespace: <to-namespace>/' \ | kubectl create -f - If someone still see a need for the flag, there’s an export script written by @zoidbergwill.
190
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
