status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Remove Helm 2 mention in Consul K8s install and uninstall (#10517) 

* docs: Remove Helm 2 mention in Consul K8s install and uninstall
Helm 2 is no longer supported via Consul K8s. Helm 3 is now the supported version for Consul K8s.
This commit is contained in:
David Yu 2021-06-29 09:18:08 -07:00 committed by GitHub
parent d87263b5eb
commit 0c63a7b4d4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/content/docs/k8s/installation/install.mdx
View File

@ -54,9 +54,8 @@ manual configuration.
### Prerequisites
The Consul Helm chart works with Helm 2 and Helm 3. If using Helm 2, you will
need to install Tiller by following the
[Helm 2 Installation Guide](https://v2.helm.sh/docs/using_helm/#quickstart-guide).
The Consul Helm chart works only with Helm 3. Install the latest version of the Helm CLI here:
[Installing Helm](https://helm.sh/docs/intro/install/).
### Installing Consul
@ -72,7 +71,7 @@ Ensure you have access to the consul chart:
```shell-session
$ helm search repo hashicorp/consul
NAME CHART VERSION APP VERSION DESCRIPTION
hashicorp/consul 0.20.1 1.7.2 Official HashiCorp Consul Chart
hashicorp/consul 0.32.0 1.10.0 Official HashiCorp Consul Chart
```
Now you're ready to install Consul! To install Consul with the default
@ -84,8 +83,6 @@ NAME: consul
...
```
-> If using Helm 2, run: `helm install --name consul hashicorp/consul --set global.name=consul`
_That's it._ The Helm chart does everything to set up a recommended
Consul-on-Kubernetes deployment.
In a couple minutes, a Consul cluster will be formed and a leader

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

@ -16,8 +16,6 @@ up some resources that Helm does not delete.
release "hashicorp" uninstalled
```
-> If using Helm 2, run `helm delete --purge hashicorp`
1. 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).
To delete, run: