Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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. 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 the canary deployment used in this project is described.

Gliffy
imageAttachmentIdatt308281358
baseUrlhttps://ehealth-dk.atlassian.net/wiki
macroId52c5a78e-3495-441f-aeb3-5d4ff0714dc2
nameFlagger
diagramAttachmentIdatt308150293
containerId308183041
timestamp1570618186453

If canary is enabled for a service in the helmsman file the default configuration will make a rollout in these steps.

  1. Start deployment of canary

  2. Set traffic to 10% (stepWeight) if pod health is ok

  3. After 1 min (interval) check pod health.

  4. After x min (?there is 3 interval settings?) check threshold for request-success-rate and request-duration.

  5. If the threshold test is ok increase traffic limitation with 10% (stepWeight)

  6. If threshold still is ok after 1 min, increase traffic again. This step will repeat until 50% (maxWeight) traffic is reached.

  7. If tests are stille ok after 1 min, complete rollout