🌱 Bump CAPI to 1.8.6

[nrb]

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:

• includes emojis

Release note:

Upgrade to CAPI 1.8.6

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[nrb]

/test pull-cluster-api-provider-aws-e2e

[richardcase]

Updates for CAPI v1.8.5 also need to be made to:

• unmanaged e2e config file: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/test/e2e/data/e2e_conf.yaml
• managed e2e config file: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/test/e2e/data/e2e_eks_conf.yaml
• Versions file: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/versions.mk

[damdo]

Will need a retitle to 1.8.6

[nrb]

/test pull-cluster-api-provider-aws-e2e

[damdo]

/test pull-cluster-api-provider-aws-e2e

[richardcase]

/test pull-cluster-api-provider-aws-e2e

[damdo]

/lgtm

/assign @richardcase @AndiDog

[richardcase]

/test ?

[k8s-ci-robot]

@richardcase: The following commands are available to trigger required jobs:

/test pull-cluster-api-provider-aws-build

/test pull-cluster-api-provider-aws-build-docker

/test pull-cluster-api-provider-aws-test

/test pull-cluster-api-provider-aws-verify

The following commands are available to trigger optional jobs:

/test pull-cluster-api-provider-aws-apidiff-main

/test pull-cluster-api-provider-aws-e2e

/test pull-cluster-api-provider-aws-e2e-blocking

/test pull-cluster-api-provider-aws-e2e-clusterclass

/test pull-cluster-api-provider-aws-e2e-conformance

/test pull-cluster-api-provider-aws-e2e-conformance-with-ci-artifacts

/test pull-cluster-api-provider-aws-e2e-eks

/test pull-cluster-api-provider-aws-e2e-eks-gc

/test pull-cluster-api-provider-aws-e2e-eks-testing

Use /test all to run the following jobs that were automatically triggered:

pull-cluster-api-provider-aws-apidiff-main

pull-cluster-api-provider-aws-build

pull-cluster-api-provider-aws-build-docker

pull-cluster-api-provider-aws-test

pull-cluster-api-provider-aws-verify

In response to this:

/test ?

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.

[richardcase]

/test pull-cluster-api-provider-aws-e2e-eks

[nrb]

/test pull-cluster-api-provider-aws-e2e-eks

last call sat on pending for 2 hours, can't see it on the prow dashboard at all.

[damdo]

It's pending probably because other eks jobs are running, only one is allowed at the same time IIUC.

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[richardcase]

Both the e2e tests passed.

/approve

[k8s-ci-robot]

[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:

• OWNERS [richardcase]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[damdo]

Do we want to back port to 2.7?

[nrb]

/cherry-pick release-2.7

[k8s-infra-cherrypick-robot]

@nrb: new pull request created: #5328

In response to this:

/cherry-pick release-2.7

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.