Skip to content

Retarget feature-branch deploy workflow at credreg-test#1028

Merged
arielr-lt merged 1 commit into
masterfrom
hotfix/deploy-feature-to-credreg-test
Apr 24, 2026
Merged

Retarget feature-branch deploy workflow at credreg-test#1028
arielr-lt merged 1 commit into
masterfrom
hotfix/deploy-feature-to-credreg-test

Conversation

@arielr-lt

Copy link
Copy Markdown
Collaborator

Summary

  • The staging env was renamed to credreg-test and moved to the cer-api-prod EKS cluster. deploy-feature-to-staging.yaml was still targeting ce-registry-eks / credreg-staging, so the DB-migration step timed out (run 24905871968).
  • Point the workflow at cer-api-prod / credreg-test, switch the Slack ENVIRONMENT label to test.
  • Add terraform/environments/eks/k8s-manifests-test/db-migrate-job.yaml (copy of the version in the ce-registry repo) so the migration job schedules on the test node group (nodeSelector env=test, toleration, priorityClassName: test-normal).

Test plan

  • Trigger Deploy feature branch to staging environment via workflow_dispatch on a test branch
  • Verify set image + rollout status succeed against deploy/main-app and deploy/worker-app in credreg-test
  • Verify the db-migrate-* Job in credreg-test schedules on a test node, runs rake db:create db:migrate, and reaches Complete
  • Confirm Slack notification shows env: test

Notes

  • Assumes the github-oidc-widget IAM role already has an EKS access entry on cer-api-prod. If the aws eks update-kubeconfig / first kubectl call fails with an auth error, add the access entry.
  • The migration manifest now lives in both repos (CredentialRegistry and ce-registry/infra). Worth consolidating later.

The staging environment was renamed to credreg-test and moved to the
cer-api-prod EKS cluster. Update deploy-feature-to-staging.yaml to point
at the new cluster/namespace and add the matching db-migrate-job manifest
(with test node selector, toleration, and priority class) so the
migration step actually schedules.
@edgarf edgarf self-requested a review April 24, 2026 21:48
@arielr-lt arielr-lt merged commit 77f7acf into master Apr 24, 2026
12 of 14 checks passed
@arielr-lt arielr-lt deleted the hotfix/deploy-feature-to-credreg-test branch April 24, 2026 21:50
excelsior pushed a commit that referenced this pull request May 18, 2026
## Summary
- The staging env was renamed to `credreg-test` and moved to the
`cer-api-prod` EKS cluster. `deploy-feature-to-staging.yaml` was still
targeting `ce-registry-eks` / `credreg-staging`, so the DB-migration
step timed out (run
[24905871968](https://github.com/CredentialEngine/CredentialRegistry/actions/runs/24905871968)).
- Point the workflow at `cer-api-prod` / `credreg-test`, switch the
Slack `ENVIRONMENT` label to `test`.
- Add
`terraform/environments/eks/k8s-manifests-test/db-migrate-job.yaml`
(copy of the version in the `ce-registry` repo) so the migration job
schedules on the test node group (`nodeSelector env=test`, toleration,
`priorityClassName: test-normal`).

## Test plan
- [ ] Trigger `Deploy feature branch to staging environment` via
workflow_dispatch on a test branch
- [ ] Verify `set image` + `rollout status` succeed against
`deploy/main-app` and `deploy/worker-app` in `credreg-test`
- [ ] Verify the `db-migrate-*` Job in `credreg-test` schedules on a
test node, runs `rake db:create db:migrate`, and reaches `Complete`
- [ ] Confirm Slack notification shows `env: test`

## Notes
- Assumes the `github-oidc-widget` IAM role already has an EKS access
entry on `cer-api-prod`. If the `aws eks update-kubeconfig` / first
kubectl call fails with an auth error, add the access entry.
- The migration manifest now lives in both repos (`CredentialRegistry`
and `ce-registry/infra`). Worth consolidating later.

Co-authored-by: Ariel Rolfo <arielr-lt+username@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants