istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

need to use replace vs create (#1397) 

to avoid failure as the app is already deployed
This commit is contained in:
Lin Sun 2018-05-31 19:26:50 -04:00 committed by GitHub
parent 53833abde9
commit 09d443a19d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/docs/setup/kubernetes/upgrading-istio.md
View File

@ -65,7 +65,7 @@ The applications already running istio will still using the sidecar from 0.7.1 a
sidecar manually by running the following command:
```command
$ kubectl apply -f <(istioctl kube-inject -f $ORIGINAL_DEPLOYMENT_YAML)
$ kubectl replace -f <(istioctl kube-inject -f $ORIGINAL_DEPLOYMENT_YAML)
```
If the sidecar was previously injected with some customized inject config
@ -73,7 +73,7 @@ The applications already running istio will still using the sidecar from 0.7.1 a
version and reinject the sidecar as follows:
```command
$ kubectl apply -f <(istioctl kube-inject \
$ kubectl replace -f <(istioctl kube-inject \
--injectConfigFile inject-config.yaml \
--filename $ORIGINAL_DEPLOYMENT_YAML)
```
@ -102,4 +102,4 @@ spec:
```
When all your applications have been migrated and tested, you can repeat the istio upgrade process, removing the `--set global.proxy.image=proxy` option.
When all your applications have been migrated and tested, you can repeat the istio upgrade process, removing the `--set global.proxy.image=proxy` option.