github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Reformat Uninstall steps (#11040) 

* docs: Reformat Uninstall steps

Reformatting uninstall as steps to make uninstall instructions more clear.
pull/11145/head
David Yu 2021-09-15 11:59:02 -07:00 committed by hc-github-team-consul-core
parent 9e6dc0fe31
commit 93b846a83c
1 changed files with 55 additions and 55 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
website/content/docs/k8s/operations/uninstall.mdx
View File

@ -9,14 +9,14 @@ description: Uninstall Consul on Kubernetes
Uninstalling Consul requires running `helm delete` **and** then manually cleaning Uninstalling Consul requires running `helm delete` **and** then manually cleaning
up some resources that Helm does not delete. up some resources that Helm does not delete.
1. First, run `helm delete`: 1. First, run `helm delete`:
```shell-session ```shell-session
$ helm delete hashicorp $ helm delete hashicorp
release "hashicorp" uninstalled release "hashicorp" uninstalled
``` ```
1. After deleting the Helm release, you need to delete the `PersistentVolumeClaim`'s 2. After deleting the Helm release, you need to delete the `PersistentVolumeClaim`'s
for the persistent volumes that store Consul's data. These are not deleted by Helm due to a [bug](https://github.com/helm/helm/issues/5156). for the persistent volumes that store Consul's data. These are not deleted by Helm due to a [bug](https://github.com/helm/helm/issues/5156).
To delete, run: To delete, run:
@ -36,35 +36,35 @@ up some resources that Helm does not delete.
~> **NOTE:** This will delete **all** data stored in Consul and it can't be ~> **NOTE:** This will delete **all** data stored in Consul and it can't be
recovered unless you've taken other backups. recovered unless you've taken other backups.
1. If installing with ACLs enabled, you will need to then delete the ACL secrets: 3. If installing with ACLs enabled, you will need to then delete the ACL secrets:
```shell-session ```shell-session
$ kubectl get secret | grep consul | grep Opaque $ kubectl get secret | grep consul | grep Opaque
consul-acl-replication-acl-token Opaque 1 41m consul-acl-replication-acl-token Opaque 1 41m
consul-bootstrap-acl-token Opaque 1 41m consul-bootstrap-acl-token Opaque 1 41m
consul-client-acl-token Opaque 1 41m consul-client-acl-token Opaque 1 41m
consul-connect-inject-acl-token Opaque 1 37m consul-connect-inject-acl-token Opaque 1 37m
consul-controller-acl-token Opaque 1 37m consul-controller-acl-token Opaque 1 37m
consul-federation Opaque 4 41m consul-federation Opaque 4 41m
consul-mesh-gateway-acl-token Opaque 1 41m consul-mesh-gateway-acl-token Opaque 1 41m
``` ```
Ensure that the secrets you're about to delete are all created by Consul and not 4. Ensure that the secrets you're about to delete are all created by Consul and not
created by someone else that happen to have the word `consul`. created by someone else that happen to have the word `consul`:
```shell-session ```shell-session
$ kubectl get secret | grep consul | grep Opaque | awk '{print $1}' | xargs kubectl delete secret $ kubectl get secret | grep consul | grep Opaque | awk '{print $1}' | xargs kubectl delete secret
secret "consul-acl-replication-acl-token" deleted secret "consul-acl-replication-acl-token" deleted
secret "consul-bootstrap-acl-token" deleted secret "consul-bootstrap-acl-token" deleted
secret "consul-client-acl-token" deleted secret "consul-client-acl-token" deleted
secret "consul-connect-inject-acl-token" deleted secret "consul-connect-inject-acl-token" deleted
secret "consul-controller-acl-token" deleted secret "consul-controller-acl-token" deleted
secret "consul-federation" deleted secret "consul-federation" deleted
secret "consul-mesh-gateway-acl-token" deleted secret "consul-mesh-gateway-acl-token" deleted
secret "consul-gossip-encryption-key" deleted secret "consul-gossip-encryption-key" deleted
``` ```
If installing with `tls.enabled` then there will be a `ServiceAccount` that is left behind: 5. If installing with `tls.enabled` then there will be a `ServiceAccount` that is left behind:
```shell-session ```shell-session
$ kubectl get serviceaccount consul-tls-init $ kubectl get serviceaccount consul-tls-init