-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Remove step for deleting webhook-cert-manager secret on Consul K8s uninstall #11035
Conversation
🤔 This PR has changes in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can remove the bullet points but this looks good!! Thanks for doing this David!!
Co-authored-by: mrspanishviking <kcardenas@hashicorp.com>
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/444871. |
🍒✅ Cherry pick of commit 4e26d94 onto |
…K8s uninstall (#11035) * Remove step for deleting webhook-cert-manager secret * Update website/content/docs/k8s/operations/uninstall.mdx
🍒✅ Cherry pick of commit 4e26d94 onto |
…K8s uninstall (#11035) * Remove step for deleting webhook-cert-manager secret * Update website/content/docs/k8s/operations/uninstall.mdx
As of Consul Helm 0.26.0, for Consul 1.8.x, we no longer need to manually remove the
consul-controller-webhook-cert
secret. This is a result of hashicorp/consul-k8s#530.