-
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
v1beta2 APIs #3720
v1beta2 APIs #3720
Conversation
Co-authored-by: Ankita Swamy <swamyan@vmware.com> Co-authored-by: Sedef Savas <ssavas@vmware.com>
Co-authored-by: Ankita Swamy <swamyan@vmware.com> Co-authored-by: Sedef Savas <ssavas@vmware.com>
6e1ec93
to
7b18c94
Compare
/test? |
@Ankitasw: 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/test-infra repository. |
/test pull-cluster-api-provider-aws-e2e-blocking |
This looks okay to me compared to previous ways of promoting a new version. But since this is a significant change, I would suggest not just taking my word for it. :D I'll wait until tests pass for lgtm. :) |
Ahh and it just happened, will fix E2E tests. |
Bwuhahahaha. :D Yeah, it's quite massive. :D |
Running E2E tests locally, and would commit the fix together, mostly failing because of some of the kubeadm APIs are still v1beta1, and we mistakenly changed it to v1beta2. Update: |
ed4f201
to
8451d6e
Compare
/test pull-cluster-api-provider-aws-e2e-blocking |
1 similar comment
/test pull-cluster-api-provider-aws-e2e-blocking |
/test pull-cluster-api-provider-aws-e2e |
/test pull-cluster-api-provider-aws-e2e-clusterclass |
/test pull-cluster-api-provider-aws-e2e-conformance |
/test pull-cluster-api-provider-aws-e2e |
de4204b
to
14109e7
Compare
/test pull-cluster-api-provider-aws-e2e |
@richardcase @Skarlso This is ready for final review. |
/lgtm |
🚀 |
14109e7
to
610bfd5
Compare
83a793d
to
a430b09
Compare
/test pull-cluster-api-provider-aws-e2e |
a430b09
to
5f8e106
Compare
/test pull-cluster-api-provider-aws-e2e |
/assign |
Based on review, discussions and e2e passing: /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 |
/lgtm |
What this PR does / why we need it:
This PR adds new v1beta2 API version and it is the exact copy of v1beta1.
After this PR is merged, v1beta2 changes will come as follow up PRs.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist: