Version
v0.4.0
Which installation method(s) does this occur on?
Source
Describe the bug.
When running helm template, against charts/topograph, the rendered manifests are missing metadata.namespace from namespace-scoped resources.
This does not affect topograph installations via Helm or ArgoCD where you can specify a destination namespace.
It does affect workflows where users are using kubectl diff to check changes against a specific resource, or kubectl apply to install topograph.
Omitting spec.metadata will default to the default namespace
I am using Helm v4.2.0
Minimum reproducible example
1. Clone repository
2. Run `helm template topograph charts/topograph --namespace topograph` > manifest.yaml
3. Reading `manifest.yaml` you will see namespaced scoped resources (such as ServiceAccount) missing `metadata.namespace`
3a.`kubectl diff` will show the namespace-scoped resources will be applied to the `default` namespace.
Relevant log output
Full env printout
Other/Misc.
No response
Code of Conduct
Version
v0.4.0
Which installation method(s) does this occur on?
Source
Describe the bug.
When running
helm template, againstcharts/topograph, the rendered manifests are missingmetadata.namespacefrom namespace-scoped resources.This does not affect topograph installations via Helm or ArgoCD where you can specify a destination namespace.
It does affect workflows where users are using
kubectl diffto check changes against a specific resource, orkubectl applyto install topograph.Omitting
spec.metadatawill default to thedefaultnamespaceI am using Helm v4.2.0
Minimum reproducible example
Relevant log output
Full env printout
Other/Misc.
No response
Code of Conduct