Migrate Web traffic to Kubernetes
Migrate Web traffic to Kubernetes
Overview
This epic contains all of the issues to migration the web frontend to the GitLab.com Kubernetes cluster.
The result of completing this will be to decommission the following VM fleets:
- web-*
- web-cny-*
DRI
Board
Blocking Issues
- Issues listed in this epic
- Graceful shut down of workhorse: gitlab-org/gitlab#325114 (closed)
- Some config can only be set by env var: gitlab-org&6060
- All blocking issues https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=kubernetes-migration-blocker
Milestones
- Potential Nginx blocker investigated and resolved
- Preprod rollout the Web fleet to Kubernetes
- Staging rollout the Web fleet to Kubernetes
- Canary rollout the Web fleet to Kubernetes
- Production rollout the Web fleet to Kubernetes
-
Cleanup
- Resource tuning
- Documentation updated
- VMs removed
- Resolve migration-related bugs
Issue Template
For any new issues that need to be created and linked to this epic, utilize the following:
/epic &272
/label ~"workflow-infra::Triage" ~"team::Delivery" ~"Service::Web" ~kubernetes ~"Delivery::P2"
Status 2021-09-23
The web fleet continues to run well following the migration to Kubernetes. Both known bugs resulting from the migration have been fixed: 1. /admin/sidekiq not loading - https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/14150 1. missing ssh fingerprints - delivery#2018 (closed) All issues are closed and this migration is considered complete.
- Show closed items
Link items together to show that they're related or that one is blocking others.