Re: [kubernetes-users] How do you access configmaps created in non-default namespace?

One more observation worth mentioning. I can't access the configmap from a deployment which is created in non-default-namespace, even if the configmap is created in default namespace. I can access the configmaps only if both deployment and configmap created only in default namespace. Best Rega

Re: [kubernetes-users] How do you access configmaps created in non-default namespace?

AFAIK you can't reference config maps across namespaces. Try creating the configmap & deployment in the same namespace, & setting the configMapKeyRef.name to simply the name of the configmap (my-configmap in your example). On Wed, 21 Sep 2016 at 07:54 Manoj Khotele wrote: > Hello Brandon, > > Pl

Re: [kubernetes-users] How do you access configmaps created in non-default namespace?

Even one more observation. You can't use field 'namespace' in 'ConfigMapKeySelector'. Else you get error something like "error validating "my-logstash-deployment.yml": error validating data: found invalid field namespace for v1.ConfigMapKeySelector; if you choose to ignore these errors, turn v

Re: [kubernetes-users] How do you access configmaps created in non-default namespace?

Thanks a lot Jimmi. It worked. On Wednesday, September 21, 2016 at 3:01:22 PM UTC+5:30, Jimmi Dyson wrote: > > AFAIK you can't reference config maps across namespaces. Try creating the > configmap & deployment in the same namespace, & setting the > configMapKeyRef.name to simply the name of the

Re: [kubernetes-users] How do you access configmaps created in non-default namespace?

In general, try not to specify namespace in your resource manifests. That makes them more portable (i.e. able to create the same resources in different namespaces that the user chooses at deploy time via kubectl --namespace flag or similar). On Wed, 21 Sep 2016 at 10:42 Manoj Khotele wrote: > Th