zalando-incubator / zalando-incubator/stackset-controller

Support dark release deployment

Open
#114 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
183
Forks
29
Avg merge
3d 18h
Merged PRs (30d)
5

Description

An interesting feature instead of starting with canary, and directly shifting traffic to your new stack, it would be nice to first push some shadow traffic to the new stack, and then decide to switch real traffic.

https://www.functionize.com/blog/what-is-canary-testing-and-dark-launching/

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the StackSet controller's existing canary, blue-green, and traffic-switching behavior, then determine how dark release deployment should be represented and verified in Kubernetes before defining the completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.