docs: consul-k8s uninstall with namespace (#11478)

* docs:  consul-k8s uninstall with namespace

Uninstall with namespace

* change release name to consul in uninstall

* Update website/content/docs/k8s/operations/uninstall.mdx

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>

* add --create-namespace command to install for custom values file

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
This commit is contained in:
David Yu 2021-11-03 16:48:48 -07:00 committed by GitHub
parent c5ecafdfde
commit a96a035973
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 4 deletions

View File

@ -124,7 +124,7 @@ controller:
Once you've created your `config.yaml` file, run `helm install` with the `-f` flag:
```shell-session
$ helm install consul hashicorp/consul -f config.yaml
$ helm install consul hashicorp/consul --create-namespace -n consul -f config.yaml
NAME: consul
...
```

View File

@ -12,11 +12,18 @@ You can uninstall Consul using Helm commands or the Consul K8s CLI.
Run the `helm uninstall` **and** manually remove resources that Helm does not delete.
1. First, run `helm uninstall`:
1. (Optional) If Consul is installed in a dedicated namespace, set the kubeConfig context to the `consul` namespace. Otherwise, subsequent commands will need to include `-n consul`.
```
kubectl config set-context --current --namespace=consul
```
1. Run the `helm uninstall <release-name>` command and specify the release name you've installed Consul with, e.g.,:
```shell-session
$ helm uninstall hashicorp
release "hashicorp" uninstalled
$ helm uninstall consul
release "consul" uninstalled
```
1. After deleting the Helm release, you need to delete the `PersistentVolumeClaim`'s