Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Overview of the Issue
When deploying consul using the helm chart and acl:manageSystemACLs = true a secret is created in Kubernetes with the name ${name}-bootstrap-acl-token. The problem comes when you uninstall the helm chart that the secret is not deleted.
Reproduction Steps
Deploy consul using this helm chart and acl:manageSystemACLs = true to create the bootstrap secret.
Execute helm uninstall and delete the chart.
Notice that the secret is not deleted.
Expected behavior
The secret is deleted after helm uninstall.
Environment details
consul-k8s version: 1.3.1
values.yaml: any values that creates a Kubernetes secret.
Community Note
Overview of the Issue
When deploying consul using the helm chart and
acl:manageSystemACLs = true
a secret is created in Kubernetes with the name${name}-bootstrap-acl-token
. The problem comes when you uninstall the helm chart that the secret is not deleted.Reproduction Steps
acl:manageSystemACLs = true
to create the bootstrap secret.Expected behavior
The secret is deleted after helm uninstall.
Environment details
consul-k8s
version:1.3.1
values.yaml
: any values that creates a Kubernetes secret.