The flowchart describe the stages in a canary deployment controlled by Flagger. This tool makes it possible to control the rollout in a number of different ways (canary, A/B testing, manually gated, etc). I the chart green text indicates types of webhooks that can be used for manually controlled rollout (this is not default behaviour). Below the chart there is a stepwise description of the canary deployment used in this project is describedset in ehealth-service.
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Start deployment of canary
Set traffic to 10% (
stepWeight) if pod health is okAfter 1 min (
interval) check pod health . After x min (?there is 3 interval settings?) and check threshold for request-success-rate and request-duration.If the threshold test is ok increase traffic limitation with 10% (
stepWeight)If threshold still is ok after 1 min, increase traffic again. This step will repeat until 50% (
maxWeight) traffic is reached.If tests are stille still ok after 1 min, complete rollout.
Minimum time for full rollout = interval * iterations= 1m * 50/10 = 5 min
Minimum time for rollback = interval * threshold = 1m * 5 = 5 min