Deploy Big Bang Prod Gitlab-runners on CI EKS cluster (Phase 3)
Description
The new CI EKS cluster on the AWS production account will need to have new gitlab-runners created with existing TAGS used in current pipelines for Big Bang developers.
Resources
Criteria
- Use automation to register the gitlab-runners to repo1.dso.mil (gitlab)
- Pause existing RKE2 gitlab-runners one by one to ensure functionality is the same on EKS
- Minimize downtime as much as possible
- get prior approval from value stream, anchors and mission team leads before cutover to EKS gitlab-runners.
- Validate and test
- Document in README.md and merge requests
Definition of Done
- code review and merge requests approvals
- RKE2 gitlab-runners are paused or destroyed and EKS runners are funcional
Gitlab-runners TAGs List
| Region | AWS Account ID | RKE2 Clusters | Runner Name | TAGS |
|---|---|---|---|---|
| us-gov-west-1 | 141025336883 | .ci.bigbang.mil | bigbang-runner | "bb-prod-ci, bigbang-runner, privileged" |
| us-gov-west-1 | 141025336883 | .ci.bigbang.mil | graduated-runner | "bb-prod-ci, graduated-runner, privileged" |
| us-gov-west-1 | 141025336883 | .ci.bigbang.mil | incubating-runner | "bb-prod-ci, incubating-runner, privileged" |
| us-gov-west-1 | 141025336883 | .ci.bigbang.mil | sandbox-runner | "bb-prod-ci, sandbox-runner, privileged" |
| us-gov-west-1 | 141025336883 | .ci.bigbang.mil | release-runner | "bb-prod-ci, release-runner, release" |
| us-gov-west-1 | 141025336883 | .ci.bigbang.mil | edge-runner | "edge-runner, privileged" |
Edited by Daniel Stocum