Skip to content

ci(DASOPS-2057): fix deploy_prod_legacy — use direct GKE credentials [release-20260508]#422

Merged
andersondario-er merged 1 commit into
release-20260508from
fix-DASOPS-2057-legacy-v12-release
May 13, 2026
Merged

ci(DASOPS-2057): fix deploy_prod_legacy — use direct GKE credentials [release-20260508]#422
andersondario-er merged 1 commit into
release-20260508from
fix-DASOPS-2057-legacy-v12-release

Conversation

@andersondario-er
Copy link
Copy Markdown
Contributor

Summary

Fixes deploy_prod_legacy on the release branch — same fix as #421 targeting main.

Changes

  • Bump deploy_prod_legacy from update_k8s_image.yml@v7@v12

Technical Details

v12 replaces gcloud container fleet memberships get-credentials --project=serca-tools with gcloud container clusters get-credentials --location --project, reading from the prod-legacy environment vars (already updated: GKE_CLUTER_NAME=sintegrate-4bb07e9c, LOCATION=us-central1, PROJECT_ID=cdip-prod1-78ca).

Files Changed

1 file changed, 1 insertion(+), 1 deletion(-)


Jira: https://allenai.atlassian.net/browse/DASOPS-2057

v12 uses direct gcloud container clusters get-credentials instead of
Fleet Connect Gateway, fixing the deploy_prod_legacy failure caused by
cdip-prod01 not being registered in the serca-tools Fleet.
@andersondario-er andersondario-er self-assigned this May 13, 2026
@andersondario-er andersondario-er merged commit 6cfa5c0 into release-20260508 May 13, 2026
1 check passed
@andersondario-er andersondario-er deleted the fix-DASOPS-2057-legacy-v12-release branch May 13, 2026 18:08
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.

1 participant