feat: add prod-v2 ALB override for the dedicated hub-utils cluster - #48
Merged
Conversation
Also widens the CI deploy path to a glob so both Argo apps get updated while they run in parallel during the migration.
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.
Wave 4 of the hub-utils migration (same parallel-deploy pattern as social-thumbnails / cloudimg / widgets-cors-proxy): minimal override layered on top of env/prod.yaml by the new Argo app — the ingress joins the existing shared hub-utils-int-prod-cloudfront ALB. Inert until the companion infra-deployments PR lands. Cutover is CloudFront-only (behavior target switch), no DNS handover.