github/flagger
1
0
Fork 0
mirror of https://github.com/fluxcd/flagger.git synced 2026-04-15 06:57:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Use podinfo v1.7

Browse Source
This commit is contained in:
stefanprodan
2019-07-26 01:25:44 +03:00
parent 163f5292b0
commit e3b03debde
19 changed files with 32 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gitbook/tutorials/canary-helm-gitops.md
+1 -1
View File
@@ -344,7 +344,7 @@ launch the `frontend` and `backend` apps.
A CI/CD pipeline for the `frontend` release could look like this:
* cut a release from the master branch of the podinfo code repo with the git tag `1.4.1`
* CI builds the image and pushes the `podinfo:1.4.1` image to the container registry
* CI builds the image and pushes the `podinfo:1.7.1` image to the container registry
* Flux scans the registry and updates the Helm release `image.tag` to `1.4.1`
* Flux commits and push the change to the cluster repo
* Flux applies the updated Helm release on the cluster
docs/gitbook/tutorials/flagger-smi-istio.md
+1 -1
View File
@@ -236,7 +236,7 @@ Trigger a canary deployment by updating the container image:
```bash
kubectl -n test set image deployment/podinfo \
podinfod=quay.io/stefanprodan/podinfo:1.4.1
podinfod=quay.io/stefanprodan/podinfo:1.7.1
```
Flagger detects that the deployment revision changed and starts a new rollout: