-
Notifications
You must be signed in to change notification settings - Fork 580
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
✨ SubnetSchema support #4971
✨ SubnetSchema support #4971
Conversation
|
Welcome @krasoffski! |
Hi @krasoffski. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
2320b77
to
4c74e82
Compare
Hi, @dlipovetsky and @richardcase |
Hi, @dlipovetsky and @richardcase |
4c74e82
to
6b75e83
Compare
Hi, @dlipovetsky and @richardcase |
Hi, @dlipovetsky and @richardcase |
Thank you for your patience @krasoffski. It's taken be a while to get back into things after a 6 week break away. /ok-to-test |
/test ? |
@richardcase: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-cluster-api-provider-aws-e2e |
Thank you, @richardcase I will take a look for test problems and come back. |
6b75e83
to
2450236
Compare
/retest |
2450236
to
9534ec4
Compare
Hi, @richardcase |
/test pull-cluster-api-provider-aws-e2e |
/test pull-cluster-api-provider-aws-e2e |
@richardcase Do these jobs have timeouts or how long it usually takes to finish? I am asking because I see that one of them running more than an hour. Updated. But it usually took about 2-3h in case everything is OK. |
Once the actual job starts running, there is a timeout (I forget what it is off the top of my head). And there are various timeouts in the tests (configured in the e2e config). There can be a delay from the Prow side before the tests are actually executed, this doesn't feed into the test timeout, though. |
Thank you, @richardcase |
/milestone v2.6.0 |
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.
thanks, the change looks good
/lgtm
The e2e tests have passed. This change looks good to me, thanks for this @krasoffski . /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardcase 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 |
Thank you, Guys. |
What type of PR is this?
This PR adds functionality related to Subnet schema type, more details can be found in original issue #4784.
Add one of the following kinds:
/kind feature
What this PR does / why we need it:
As I mentioned above, this PR adds ability to configure preferred way for subnets division with priority to private as original behavior by default or public via
PreferPublic
.For existing users nothing is changed because original behavior is not changed and set as default. But new parameter
PreferPublic
allows to use provider in more specific cases like with Google Agones where subnet division to with public subnets priority fits better.Which issue(s) this PR fixes
Fixes #4784
Special notes for your reviewer:
My first PR to AWS provider =)
Checklist:
Release note: