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

Document rollout halting

Browse Source
This commit is contained in:
Stefan Prodan
2018-09-23 12:45:29 +03:00
parent f756dc247c
commit 9d1b4ce4d4
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@@ -10,7 +10,7 @@ Create a test namespace:
kubectl apply -f ./artifacts/namespace/
```
Create GA and canary deployments, services and Istio virtual service:
Create GA and canary deployments, services, hpa and Istio virtual service:
```bash
kubectl apply -f ./artifacts/workloads/
@@ -24,15 +24,18 @@ Rollout flow:
* scan namespace for deployments marked for rollout
* scan namespace for a corresponding canary deployment (`-canary` prefix)
* check Istio virtual service routes are mapped to GA and canary ClusterIP services
* check GA and Canary deployments status (halt rollout if a rolling update is underway or if pods are in crash loop)
* check GA and canary deployments status (halt rollout if a rolling update is underway or if pods are unhealthy)
* increase canary traffic weight percentage by 10%
* check canary HTTP success rate (halt rollout if percentage is under the specified threshold)
* advance canary traffic wight by 10% till it reaches 100% (halt rollout if deployments are unhealthy or success rate is under the threshold)
* advance canary traffic wight by 10% till it reaches 100%
* halt rollout while canary success rate is under the threshold
* halt rollout if the GA or canary deployments becomes unhealthy
* halt rollout while canary deployment is being scaled up/down by HPA
* promote canary to GA (copy canary deployment spec template over GA)
* wait for GA rolling update to finish
* scale to zero the canary deployment
* mark rollout deployment as finished
* wait for canary deployment to be updated (revision bump) and start over
* wait for the canary deployment to be updated (revision bump) and start over
HTTP success rate query: