Use apply rather than create for rolling upgrades (#2307)

content/docs/setup/kubernetes/helm-install/index.md

@@ -65,7 +65,7 @@ via `kubectl apply`, and wait a few seconds for the CRDs to be committed in the
 
     {{< text bash >}}
     $ kubectl create namespace istio-system
-    $ kubectl create -f $HOME/istio.yaml
+    $ kubectl apply -f $HOME/istio.yaml
     {{< /text >}}
 
 ### Option 2: Install with Helm and Tiller via `helm install`
@@ -77,7 +77,7 @@ to manage the lifecycle of Istio.
 1. If a service account has not already been installed for Tiller, install one:
 
     {{< text bash >}}
-    $ kubectl create -f install/kubernetes/helm/helm-service-account.yaml
+    $ kubectl apply -f install/kubernetes/helm/helm-service-account.yaml
     {{< /text >}}
 
 1. Install Tiller on your cluster with the service account:

content/docs/setup/kubernetes/multicluster-install/index.md

@@ -103,7 +103,7 @@ Proceed to one of the options for connecting the remote cluster to the local clu
 1.  Instantiate the remote cluster's connection to the Istio control plane:
 
     {{< text bash >}}
-    $ kubectl create -f $HOME/istio-remote.yaml
+    $ kubectl apply -f $HOME/istio-remote.yaml
     {{< /text >}}
 
 1.  Label all the remote cluster's namespaces requiring auto-sidecar injection.  The following example labels the `default` namespace.
@@ -120,7 +120,7 @@ Proceed to one of the options for connecting the remote cluster to the local clu
 install one:
 
     {{< text bash >}}
-    $ kubectl create -f install/kubernetes/helm/helm-service-account.yaml
+    $ kubectl apply -f install/kubernetes/helm/helm-service-account.yaml
     {{< /text >}}
 
 1.  Initialize Helm:
@@ -299,7 +299,7 @@ The following procedure is to be performed against the remote cluster.
 1.  Instantiate the remote cluster's connection to the Istio control plane:
 
     {{< text bash >}}
-    $ kubectl create -f $HOME/istio-remote_noautoinj.yaml
+    $ kubectl apply -f $HOME/istio-remote_noautoinj.yaml
     {{< /text >}}
 
 1.  [Generate kubeconfig for remote clusters](#generate-kubeconfigs-for-remote-clusters)
@@ -434,7 +434,7 @@ allow the remote sidecars to resolve the `istio-pilot.istio-system` hostname via
           --set security.selfSigned=false \
           --set global.controlPlaneSecurityEnabled=true \
           install/kubernetes/helm/istio > ${HOME}/istio-auth.yaml
-        $ kubectl create -f ${HOME}/istio-auth.yaml
+        $ kubectl apply -f ${HOME}/istio-auth.yaml
         {{< /text >}}
 
 1.  *Remote Cluster.*  Deployment of remote cluster's istio components
@@ -463,7 +463,7 @@ allow the remote sidecars to resolve the `istio-pilot.istio-system` hostname via
           --set global.remoteTelemetryAddress=${TELEMETRY_POD_IP} \
           --set global.proxy.envoyStatsd.enabled=true \
           --set global.proxy.envoyStatsd.host=${STATSD_POD_IP} > ${HOME}/istio-remote-auth.yaml
-        $ kubectl create -f ${HOME}/istio-remote-auth.yaml
+        $ kubectl apply -f ${HOME}/istio-remote-auth.yaml
         {{< /text >}}
 
     1.  [Generate kubeconfig for remote cluster](#generate-kubeconfigs-for-remote-clusters)