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.

Sign up for GitHub

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

Jump to bottom

Add initialization phase to Kubernetes router #384

Merged
merged 1 commit into from
Dec 1, 2019
Merged

Add initialization phase to Kubernetes router #384

merged 1 commit into from
Dec 1, 2019

Conversation

stefanprodan
Copy link
Member

This PR makes Flagger take over a running deployment without disruption:

  • create Kubernetes services before deployments
  • ensure Envoy's readiness by creating the canary and primary ClusterIP services
  • take over main service after primary becomes availability
  • create mesh routes after primary becomes availability

Fix: #374
Fix: #308

@stefanprodan
Add initialization phase to Kubernetes router
8766523 
Create Kubernetes services before deployments because Envoy's readiness depends on existing ClusterIPs
@stefanprodan stefanprodan merged commit 295f5d7 into master Dec 1, 2019
@stefanprodan stefanprodan mentioned this pull request Dec 3, 2019
Merged
@stefanprodan stefanprodan deleted the svc-init branch December 19, 2019 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@stefanprodan