Use podinfo v1.7

fluxcd · Jul 25, 2019 · e3b03de · e3b03de
1 parent 163f529
commit e3b03de
Show file tree

Hide file tree

Showing 19 changed files with 32 additions and 22 deletions.
diff --git a/artifacts/ab-testing/deployment.yaml b/artifacts/ab-testing/deployment.yaml
@@ -25,7 +25,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.0
+ image: quay.io/stefanprodan/podinfo:1.7.0
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/artifacts/appmesh/deployment.yaml b/artifacts/appmesh/deployment.yaml
@@ -25,7 +25,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.0
+ image: quay.io/stefanprodan/podinfo:1.7.0
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/artifacts/canaries/deployment.yaml b/artifacts/canaries/deployment.yaml
@@ -25,7 +25,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.0
+ image: quay.io/stefanprodan/podinfo:1.7.0
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/artifacts/gloo/deployment.yaml b/artifacts/gloo/deployment.yaml
@@ -25,7 +25,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.0
+ image: quay.io/stefanprodan/podinfo:1.7.0
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/artifacts/nginx/deployment.yaml b/artifacts/nginx/deployment.yaml
@@ -23,7 +23,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.0
+ image: quay.io/stefanprodan/podinfo:1.7.0
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/artifacts/workloads/canary-deployment.yaml b/artifacts/workloads/canary-deployment.yaml
@@ -23,7 +23,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.0
+ image: quay.io/stefanprodan/podinfo:1.7.0
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/artifacts/workloads/primary-deployment.yaml b/artifacts/workloads/primary-deployment.yaml
@@ -23,7 +23,7 @@ spec:
  spec:
  containers:
  - name: podinfod
- image: quay.io/stefanprodan/podinfo:1.4.1
+ image: quay.io/stefanprodan/podinfo:1.7.1
  imagePullPolicy: IfNotPresent
  ports:
  - containerPort: 9898

diff --git a/charts/podinfo/Chart.yaml b/charts/podinfo/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v1
-version: 2.2.0
-appVersion: 1.4.0
+version: 2.3.0
+appVersion: 1.7.0
 name: podinfo
 engine: gotpl
 description: Flagger canary deployment demo chart

diff --git a/charts/podinfo/values.yaml b/charts/podinfo/values.yaml
@@ -1,7 +1,7 @@
 # Default values for podinfo.
 image:
  repository: quay.io/stefanprodan/podinfo
- tag: 1.4.0
+ tag: 1.7.0
  pullPolicy: IfNotPresent
 
 service:

diff --git a/docs/gitbook/how-it-works.md b/docs/gitbook/how-it-works.md
@@ -902,6 +902,7 @@ Manual gating with Flagger's tester:
 ```
 
 The `/gate/halt` returns HTTP 403 thus blocking the rollout. 
+
 If you have notifications enabled, Flagger will post a message to Slack or MS Teams if a canary rollout is waiting for approval.
 
 Change the URL to `/gate/approve` to start the canary analysis:
@@ -937,3 +938,12 @@ You can pause the rollout at any time with:
 ```bash
 curl -d '{"name": "podinfo","namespace":"test"}' http://localhost:8080/gate/close 
 ```
+
+If a canary analysis is paused the status will change to waiting:
+
+```bash
+kubectl get canary/podinfo
+
+NAME STATUS WEIGHT
+podinfo Waiting 0
+```
diff --git a/docs/gitbook/tutorials/canary-helm-gitops.md b/docs/gitbook/tutorials/canary-helm-gitops.md
@@ -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

diff --git a/docs/gitbook/tutorials/flagger-smi-istio.md b/docs/gitbook/tutorials/flagger-smi-istio.md
@@ -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:

diff --git a/docs/gitbook/usage/ab-testing.md b/docs/gitbook/usage/ab-testing.md
@@ -131,7 +131,7 @@ Trigger a canary deployment by updating the container image:
 
 ```bash
 kubectl -n test set image deployment/abtest \
-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:

diff --git a/docs/gitbook/usage/appmesh-progressive-delivery.md b/docs/gitbook/usage/appmesh-progressive-delivery.md
@@ -176,7 +176,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:

diff --git a/docs/gitbook/usage/blue-green.md b/docs/gitbook/usage/blue-green.md
@@ -59,8 +59,8 @@ Create a deployment and a horizontal pod autoscaler:
 ```bash
 export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master
 
-kubectl apply -f ${REPO}/artifacts/canary/deployment.yaml
-kubectl apply -f ${REPO}/artifacts/canary/hpa.yaml
+kubectl apply -f ${REPO}/artifacts/canaries/deployment.yaml
+kubectl apply -f ${REPO}/artifacts/canaries/hpa.yaml
 ```
 
 Deploy the load testing service to generate traffic during the analysis:
@@ -172,7 +172,7 @@ Trigger a 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:
@@ -297,7 +297,7 @@ Trigger a deployment by updating the container image:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-podinfod=quay.io/stefanprodan/podinfo:1.4.3
+podinfod=quay.io/stefanprodan/podinfo:1.7.3
 ```
 
 Generate 404s:

diff --git a/docs/gitbook/usage/gloo-progressive-delivery.md b/docs/gitbook/usage/gloo-progressive-delivery.md
@@ -197,7 +197,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:

diff --git a/docs/gitbook/usage/linkerd-progressive-delivery.md b/docs/gitbook/usage/linkerd-progressive-delivery.md
@@ -165,7 +165,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:

diff --git a/docs/gitbook/usage/nginx-progressive-delivery.md b/docs/gitbook/usage/nginx-progressive-delivery.md
@@ -189,7 +189,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:

diff --git a/docs/gitbook/usage/progressive-delivery.md b/docs/gitbook/usage/progressive-delivery.md
@@ -119,7 +119,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: