Open MikaelSmith opened 2 years ago
Hi Mikael,
we've encountered the same issue, but we haven't had specified a namespace in the deployment object but instead on the netpols. The issue was easily fixed by replacing the hardcoded namespace through {{ .Release.Namespace }}
.
That's a little tricky to do in my case.
Are you running helm render
or something that replaces {{ .Release.Namespace }}
with an empty string?
No, kubeScore replaces it with the "default" Namespace. But yes our applications get deployed with ArgoCD so it takes care of inserting the correct value into {{ .Release.Namespace }}
But I don't see an issue with appending the namespace field in the netpols itself as they are namespaced anyway.
However it would be nice to have a parameter to set wanted namespace.
Which version of kube-score are you using?
What did you do?
Using a Helm chart that explicitly sets namespaces, with resources that rely on the execution context to set the namespace, means that resources that work together produce an error. For example
and
errors because the deployment and network policy don't both explicitly identify the same namespace.
What did you expect to see?
I expected kube-score to have a concept of the current namespace to use when not explicitly stated.
What did you see instead?
An error