-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select random region in health check #1911
Conversation
|
if [ -z "${{ inputs.aws_region }}" ]; then | ||
regions=("us-west-2" "us-east-1" "ca-central-1" "eu-central-1") | ||
rand=$[$RANDOM % ${#regions[@]}] | ||
selected_aws_region=${regions[$rand]} | ||
else | ||
selected_aws_region="${{ inputs.aws_region }}" | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I chose bash for this, because it doesn't involve any JSON parsing like we do in case of account selection.
And is rather simple at this point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL about composite actions, LGTM
Problem
We could spread health_checks traffic across regions we also use for canaries (since they're bootstrapped anyway).
This is a follow up on this #1902 (comment) .
Changes
Validation
I looked at jobs to see if canaries keep their stickyness and if health checks select random regions.
Checklist
run-e2e
label set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.