Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate and Implement Istio Based Canary Deployments #40

Closed
dthomson25 opened this issue Mar 15, 2019 · 2 comments
Closed

Investigate and Implement Istio Based Canary Deployments #40

dthomson25 opened this issue Mar 15, 2019 · 2 comments
Labels
canary Canary related issue enhancement New feature or request L

Comments

@dthomson25
Copy link
Member

Currently, Canary deployments are limited to traffic shaping using the round-robin behavior of the Kubernetes Service. This strategy works with applications with at least 10 replicas running because they can limit the scope of their change to a smaller percentage of the traffic. However, smaller applications cannot limit the percentage to the same degree. With a service mesh solution, the small applications achieve the same percentages as the larger applications.

This issue will be updated after an initial investigation to determine the work required to add an Istio based canary deployment.

@dthomson25 dthomson25 added this to the v0.4.0 milestone Mar 15, 2019
@jessesuen jessesuen removed this from the v0.4.0 milestone May 31, 2019
@jessesuen jessesuen added this to the v0.7 milestone Jul 30, 2019
@jessesuen jessesuen added canary Canary related issue enhancement New feature or request labels Aug 2, 2019
@malinafong malinafong added the L label Sep 12, 2019
@dthomson25
Copy link
Member Author

Remaining work for this ticket includes:

  • Enqueue rollout on any virtual service change
  • Validation of the virtual services

@dthomson25
Copy link
Member Author

The Alpha version has been merged in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
canary Canary related issue enhancement New feature or request L
Projects
None yet
Development

No branches or pull requests

3 participants