Closed v0lkan closed 9 months ago
I can work on this
I might have found the issue when we add this annotations value, helm template
adds the vsecm-system
Namespace resource to the bottom of the manifest. When I removed the podAnnotations
value from values.yml
and generated the manifests, deployment worked as expected.
Previously, the podAnnotations key was duplicated, so I guess it was overriding, and it had no effect.
podAnnotations:
"helm.sh/hook": pre-install
https://github.com/vmware-tanzu/secrets-manager/blob/main/helm-charts/0.21.5/values.yaml#L60-L61
@rohatcan it’s all yours. have fun :) .
Working as expected right now.
Closing.
Please let me know if it needs to be reopened.
Steps to Repo
Start with a fresh cluster.
Then, execute the following:
Expectation:
vsecm-system
namespace should be createdvsecm-system
namespace should have Safe and Sentinel up and running w/o any issues.What happens:
I get the following error log that indicates that the process cannot find
vsecm-system
namespace"Also, although the namespace is there, there are no pods in it: