The argocd-apps setup is finalized
- Deploy runner in dev with the new config
- Deploy runner in prod with the new config
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| In Progress | RThomas-WMF | T358575 Kubernetes(k8s) platform for Enterprise Applications | |||
| Open | None | T384574 [APP: Objective 3 Term 3.3. - WME OKR TBD- Q1-Q2 FY 25-26]- Gitlab on k8s | |||
| Resolved | This.chris.corriere | T410901 Finalize the dev and prod k8s gitlab runners configuration |
Event Timeline
Comment Actions
Notes from chat:
- Finalize gitlab runner configuration to handle the concurrency required by the existing pipeline builds happening on ECS fargate.
A few other checks such as failed task cleanup and garbage dump of the pods should work as expected. Memory spec should be pipeline specific instead of changing runner configuration.
- Deploy the runner for production
- Start migrating pipelines for existing services first, APIs later
dags
content-integrity
commons
Comment Actions
working to get an EKS gitlab runner deployed to production.
Remaining steps to deploy the runner to prod:
- the existing eks runner Argocd app is not templated completely, It should read configurable values from values-wme-eks-<env>.yaml
- we have to rename the runner tags appropriately for dev
- For production, a separate runner registration token is required
The upcoming wikidata deployment will use the existing ECS runners instead of the EKS runners.
This comment was removed by This.chris.corriere.
Comment Actions
I was able to run a dags-check on both dv and pr eks runners in the pipeline-test project