Add legacy cluster deploy jobs to release pipeline#1579
Open
andersondario-er wants to merge 6 commits into
Open
Add legacy cluster deploy jobs to release pipeline#1579andersondario-er wants to merge 6 commits into
andersondario-er wants to merge 6 commits into
Conversation
Adds dev-legacy and prod-legacy Helm deployment jobs (identical pattern to report-form-builder) that deploy via SSH bastion tunnel to the legacy GKE clusters after stage succeeds.
…acy deploy Pass explicit image_repository, deployment_name, and container_name to the in-repo _deploy_legacy_kubectl.yml workflow (kept in-repo because das-web-react is a public repo and cannot call the private serca-pipelines).
Sync in-repo copy with serca-pipelines fix: enumerate specific GCP domains in NO_PROXY instead of *.googleapis.com (wildcard not honoured by Go's HTTP client), and add per-attempt failure message to tunnel loop.
Adds service_account input to the in-repo legacy deploy workflow (falls back to vars.SERVICE_ACCOUNT) and wires LEGACY_DEPLOY_SERVICE_ACCOUNT into all four legacy jobs so they impersonate the dedicated deploy SA. Also fixes the ((SUCCESS_COUNT++)) bash gotcha that aborts under set -e after the first successful tenant.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds legacy cluster deployment jobs to the
das-web-reactrelease pipeline, mirroring the pattern already used in the report-form-builder (EFB) repo. On each release branch run, after stage sync succeeds, the pipeline deploys to the legacy dev cluster and then to the legacy prod cluster (split across 3 parallel jobs).Changes
Added
.github/workflows/_deploy_legacy.yml— reusable Helm workflow that authenticates via WIF, sets up an SSH tunnel through the bastion host, and runshelm upgrade --install das-web-reactper tenant with stuck-release recovery and a deployment summary.github/workflows/helm/legacy-dev-values.yml— placeholder Helm values for the legacy dev environment (image repository pre-configured).github/workflows/helm/legacy-prod-values.yml— placeholder Helm values for the legacy prod environment (image repository pre-configured)deploy-dev-legacy,deploy-prod-legacy-1/2/3jobs inrelease.yml, chained aftersync-stageTechnical Details
das-web-reactHelm chart (oci://europe-west3-docker.pkg.dev/padas-app/er-mt-helm/das-web-react, version1.0.2)das-dev(us-west1-a) for dev-legacy,das-prod1(europe-west3-a) for prod-legacykubernetes-bastion-2inearthranger-78ca55ca, tunneling tolocalhost:8888LEGACY_TENANTS_DEV,LEGACY_TENANTS_1/2/3(must be set before first run)Files Changed
4 files changed, 297 insertions(+)