Removed references to helm 2

juice-shop · Apr 23, 2021 · 829da45 · 829da45
1 parent f8ff186
commit 829da45
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 20 deletions.
diff --git a/guides/aws/aws.md b/guides/aws/aws.md
@@ -35,10 +35,6 @@ kubectl config current-context
 # You'll need to add the multi-juicer helm repo to your helm repos
 helm repo add multi-juicer https://iteratec.github.io/multi-juicer/
 
-# for helm <= 2
-helm install multi-juicer/multi-juicer --name multi-juicer
-
-# for helm >= 3
 helm install multi-juicer multi-juicer/multi-juicer
 
 # kubernetes will now spin up the pods
@@ -110,6 +106,7 @@ kubectl apply -f https://raw.githubusercontent.com/iteratec/multi-juicer/master/
 ```
 
 You can get the LoadBalancer's DNS record either from the AWS console, or by running:
+
 ```sh
 kubectl get ingress
 # Should print something like:
@@ -118,6 +115,7 @@ kubectl get ingress
 ```
 
 Use `kubectl get pods`to see the pods you have successfully running, which should be similar to
+
 ```sh
 kubectl get pods
 # NAME                                 READY   STATUS      RESTARTS   AGE
@@ -149,6 +147,7 @@ kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingr
 # Delete the kubernetes cluster
 eksctl delete cluster multi-juicer
 ```
+
 ## Errors you might see
 
 ```
@@ -157,6 +156,6 @@ AWS::IAM::Role/Role1: CREATE_FAILED – "1 validation error detected: Value '' a
 
 This error may occur when you don't update `cluster-iam.yaml` with your Region and Policy ARN.
 
-  - Update `cluster-iam.yaml`
-  - Run `eksctl delete iamserviceaccount --cluster=multi-juicer --name=alb-ingress-controller --namespace=kube-system` to delete the old account if it exists
-  - Run `eksctl create iamserviceaccount --config-file=cluster-iam.yaml --approve --override-existing-serviceaccounts`
+- Update `cluster-iam.yaml`
+- Run `eksctl delete iamserviceaccount --cluster=multi-juicer --name=alb-ingress-controller --namespace=kube-system` to delete the old account if it exists
+- Run `eksctl create iamserviceaccount --config-file=cluster-iam.yaml --approve --override-existing-serviceaccounts`
diff --git a/guides/azure/azure.md b/guides/azure/azure.md
@@ -29,10 +29,6 @@ kubectl config current-context
 # You'll need to add the multi-juicer helm repo to your helm repos
 helm repo add multi-juicer https://iteratec.github.io/multi-juicer/
 
-# for helm <= 2
-helm install multi-juicer/multi-juicer --name multi-juicer
-
-# for helm >= 3
 helm install multi-juicer multi-juicer/multi-juicer
 
 # kubernetes will now spin up the pods

diff --git a/guides/digital-ocean/digital-ocean.md b/guides/digital-ocean/digital-ocean.md
@@ -29,10 +29,6 @@ kubectl config current-context
 # You'll need to add the multi-juicer helm repo to your helm repos
 helm repo add multi-juicer https://iteratec.github.io/multi-juicer/
 
-# for helm <= 2
-helm install multi-juicer/multi-juicer --name multi-juicer
-
-# for helm >= 3
 helm install multi-juicer multi-juicer/multi-juicer
 
 # kubernetes will now spin up the pods

diff --git a/guides/k8s/k8s.md b/guides/k8s/k8s.md
@@ -23,7 +23,6 @@ kubectl cluster-info
 # You'll need to add the multi-juicer helm repo to your helm repos
 helm repo add multi-juicer https://iteratec.github.io/multi-juicer/
 
-# for helm >= 3
 helm install multi-juicer multi-juicer/multi-juicer
 
 # kubernetes will now spin up the pods

diff --git a/guides/openshift/openshift.md b/guides/openshift/openshift.md
@@ -27,10 +27,6 @@ oc new-project multi-juicer
 # You'll need to add the multi-juicer helm repo to your helm repos
 helm repo add multi-juicer https://iteratec.github.io/multi-juicer/
 
-# for helm <= 2
-helm install multi-juicer/multi-juicer --name multi-juicer ./multi-juicer/helm/multi-juicer/
-
-# for helm >= 3
 helm install multi-juicer multi-juicer/multi-juicer ./multi-juicer/helm/multi-juicer/
 ```