-
Notifications
You must be signed in to change notification settings - Fork 578
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
Bump CAPI to v1.5.0 #4398
Bump CAPI to v1.5.0 #4398
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3647679
to
e91485d
Compare
7ec1565
to
27943ba
Compare
@furkatgofurov7 - maybe a |
2deef07
to
27943ba
Compare
f818126
to
49ad729
Compare
3b452be
to
639abcf
Compare
/retitle Bump CAPI to v1.5.0-rc.1 This should be ready for review! |
@richardcase it has been already updated to v1.5.0 but forgot to update the title. Anyways it needs a rebase, pushing it.. |
Signed-off-by: Furkat Gofurov <[email protected]>
Signed-off-by: Furkat Gofurov <[email protected]>
The tests where failing after upgrading controller-runtime due to changes in the fake client. Signed-off-by: Richard Case <[email protected]>
Signed-off-by: Furkat Gofurov <[email protected]>
Signed-off-by: Furkat Gofurov <[email protected]>
48f7107
to
e758b8f
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
Re-running it case it was a flake: /test pull-cluster-api-provider-aws-e2e |
GH rate limit was hit with this run, rerunning it again /test pull-cluster-api-provider-aws-e2e |
same /test pull-cluster-api-provider-aws-e2e |
/test pull-cluster-api-provider-aws-e2e |
1 similar comment
/test pull-cluster-api-provider-aws-e2e |
@furkatgofurov7 do you need any help here? |
@richardcase would you be able to spend some time here? |
Adding label 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. |
@furkatgofurov7 @richardcase I dont have permission to edit the PR so couldn't push the changes, could any of you resolve the conflicts, then we can merge this on priority |
@furkatgofurov7: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
I ll cherry pick the changes from this PR and raise a new one for fixing the tests and rebasing. |
PR needs rebase. 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. |
/close in favor of #4510 |
@Ankitasw: Closed this PR. 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. |
What type of PR is this?
/kind support
What this PR does / why we need it:
Bumps CAPI to v1.5.0-rc.1 based on https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/book/src/developer/providers/migrations/v1.4-to-v1.5.md
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 #4375, #4390
Special notes for your reviewer:
Checklist:
Release note: