Namespace of JSON loaded data about kube-mgmt HOT 4 CLOSED

What is the best way to get the namespace where I put the data ConfigMap? (Workaround I found: use opa.runtime() which gives me all the environment variables of OPA and then make OPA container consume the namespace using the downwardAPI)

I suspect that users are hardcoding the namespace in their policies today. @iverberk do you have any thoughts on this?

Can the data ConfigMap be created in other namespaces (not OPA's one) like policies (--policies flag)?

yes, the namespaces specified by --policies will get used.

from kube-mgmt.

We are indeed hardcoding the namespace because we know where we will put the data configmap beforehand. I don't have any other suggestions on how to do it dynamically unfortunately.

from kube-mgmt.

I'm going to close this because I don't think there's anything to be done at this point in time.

from kube-mgmt.

the issue is closed but maybe worth to discuss.

we use our policies in different environments like CloudFoundry, K8S, simple EC2 Instances and the developer, which generates the rego files, should not care about the landscape where the rego files are deployed.

From my point of view referencing the namespace and config-map name in the rego files is not a good pattern. You are mixing deployment and rules.

from kube-mgmt.