docs: add helm v3 commands

doc/source/workflow/usage-reporting.md

@@ -9,7 +9,7 @@ We provide an option to use an anonymous metrics collection tool provided by the
 To help support the development of seldon-core, the voluntary reporting of usage data can be enabled whenever the "seldon-core-operator" helm chart is used  by setting the "--set usageMetrics.enabled=true" option.
 
 ```bash
-helm install seldon-core-operator --name seldon-core \
+helm install seldon-core seldon-core-operator \
         --repo https://storage.googleapis.com/seldon-charts --set usageMetrics.enabled=true
 ```
 
@@ -62,7 +62,7 @@ An example of what's reported:
 Reporting of usage data is disabled by default, just use "seldon-core-operator" as normal.
 
 ```bash
-helm install seldon-core-operator --name seldon-core \
+helm install seldon-core seldon-core-operator \
         --repo https://storage.googleapis.com/seldon-charts
 ```
 

examples/cicd/sig-mlops-jenkins-classic/README.md

@@ -507,7 +507,7 @@ In particular, you will need to run the following:
 ```bash
 %%bash
 helm install \
-    --name "jenkins" stable/jenkins \
+    jenkins stable/jenkins \
     --namespace "jenkins" \
     --set "rbac.create=true" \
     --set "master.adminUser=admin" \

examples/models/aws_eks_deep_mnist/README.md

@@ -385,7 +385,7 @@ We first start with the custom resource definitions (CRDs)
 
 
 ```python
-!helm install seldon-core-operator --name seldon-core-operator --repo https://storage.googleapis.com/seldon-charts --set usageMetrics.enabled=true --namespace seldon-system
+!helm install seldon-core-operator seldon-core-operator --repo https://storage.googleapis.com/seldon-charts --set usageMetrics.enabled=true --namespace seldon-system
 ```
 
     NAME:   seldon-core-operator
@@ -467,7 +467,7 @@ In EKS it automatically creates an Elastic Load Balancer, which you can configur
 
 
 ```python
-!helm install stable/ambassador --name ambassador --set crds.keep=false
+!helm install ambassador stable/ambassador --set crds.keep=false
 ```
 
     NAME:   ambassador

examples/models/azure_aks_deep_mnist/README.md

@@ -354,7 +354,7 @@ We first start with the custom resource definitions (CRDs)
 
 
 ```python
-!helm install seldon-core-operator --name seldon-core-operator --repo https://storage.googleapis.com/seldon-charts
+!helm install seldon-core-operator seldon-core-operator --repo https://storage.googleapis.com/seldon-charts
 ```
 
     NAME:   seldon-core-operator
@@ -415,7 +415,7 @@ In EKS it automatically creates an Elastic Load Balancer, which you can configur
 
 
 ```python
-!helm install stable/ambassador --name ambassador --set crds.keep=false
+!helm install ambassador stable/ambassador --set crds.keep=false
 ```
 
     Error: release ambassador failed: serviceaccounts "ambassador" already exists

examples/models/gpu_tensorflow_deep_mnist/README.md

@@ -430,7 +430,7 @@ We first start with the custom resource definitions (CRDs)
 
 
 ```python
-!helm install seldon-core-operator --name seldon-core-operator --repo https://storage.googleapis.com/seldon-charts
+!helm install seldon-core-operator seldon-core-operator --repo https://storage.googleapis.com/seldon-charts
 ```
 
     NAME:   seldon-core-operator

testing/profiling/engine/README.md

@@ -5,7 +5,7 @@
   1. Create debug image using Makefile. Ensure you use current version of engine.
   1. Launch Seldon Core with this image as the engine image using, e.g.
      ```
-     !helm install ../helm-charts/seldon-core --name seldon-core --namespace seldon  --set ambassador.enabled=true --set engine.image.name=seldonio/engine-debug:0.2.6-SNAPSHOT
+     !helm install seldon-core ../helm-charts/seldon-core --namespace seldon  --set ambassador.enabled=true --set engine.image.name=seldonio/engine-debug:0.2.6-SNAPSHOT
      ```
   1. Check logs of instance to get port and port forward to it, e.g.
      ```