-
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 1.8.6 #5249
base: main
Are you sure you want to change the base?
🌱 Bump CAPI to 1.8.6 #5249
Conversation
Skipping CI for Draft Pull Request. |
[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 |
/test pull-cluster-api-provider-aws-e2e |
Updates for CAPI v1.8.5 also need to be made to:
|
Will need a retitle to 1.8.6 |
Signed-off-by: Nolan Brubaker <[email protected]>
/test pull-cluster-api-provider-aws-e2e |
@nrb: The following test 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-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Brings CAPI to 1.8.6 specifically for PRs kubernetes-sigs/cluster-api#11303 and kubernetes-sigs/cluster-api#11478
This appears to address on-going failures we see in CAPA CI where the
capa-e2e.[It] [unmanaged] [Cluster API Framework] Self Hosted Spec Should pivot the bootstrap cluster to a self-hosted cluster
case has been failing on the Kubernetes 1.29.8 to 1.29.9 step continuously.
My investigations of the logs showed that the most obvious errors were with webhooks during this step, something mentioned in kubernetes-sigs/cluster-api#11133
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:
Fully fixing the periodic failures will probably need #5242 and #5239, but I think the failures addressed by the CAPI updates are the most common.
Checklist:
Release note: