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
test/e2e: Allow zones to be passed to e2e cloud provider #98787
Conversation
/hold (verifying there are no issues with this) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
47d6350
to
6e7e55c
Compare
Instead of allowing the cloud provider to guess at the zones that should be applied for a cluster under test, allow the explicit list of zones to consider to be passed as a new test context flag -gce-zones. Only the GCE test cloud provider recognizes this value because only the GCE test cloud provider makes assumptions about zones for verifying values, and the default assumptions for GKE do not always match non-GKE providers.
6e7e55c
to
9830cc9
Compare
/lgtm please feel free to remove hold when you are ready |
/hold cancel thanks for the review |
/triage accepted |
Instead of allowing the cloud provider to guess at the zones that should be applied for a cluster under test, allow the explicit list
of zones to consider to be passed as a new test context flag -gce-zones.
For distributions that want to run e2e tests against the GCE cloud but restrict zones based on rules relevant to how they install, allowing explicit zone restrictions to be passed to the tests.
Only the GCE test cloud provider recognizes this value because only the GCE test cloud provider makes assumptions about zones for verifying values, and the default assumptions for GKE do not always match non-GKE providers.
/kind cleanup