OSASINFRA-3965: Bump cluster-api to v1.11.3

[stephenfin]

Pull in the most recent version which includes the v1beta2 API required by CAPO v0.13.x (and likely others in the future).

This can be treated as a pre-requisite for #10090.

[openshift-ci-robot]

@stephenfin: This pull request references OSASINFRA-3965 which is a valid jira issue.

In response to this:

Pull in the most recent version which includes the v1beta2 API required by CAPO v0.13.x (and likely others in the future).

This can be treated as a pre-requisite for #10090.

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 openshift-eng/jira-lifecycle-plugin repository.

[stephenfin]

/retest-required

[stephenfin]

/retest

[patrickdillon]

/test e2e-nutanix-ovn e2e-openstack-ovn e2e-powervs-ovn

[patrickdillon]

/test e2e-ibmcloud-ovn

[patrickdillon]

/test e2e-powervs-capi-ovn

[patrickdillon]

/approve
/lgtm

Let's wait to make sure we don't break any of these platforms before adding verified

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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 [patrickdillon]

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

[stephenfin]

e2e-azure-ovn-shared-vpc

This job appears to be permafailing currently.

e2e-nutanix-ovn

Also permafailing currently.

e2e-openstack-ovn

This is still running at time of comment, but sadly it's not in great shape either (we are working on it!)

e2e-ibmcloud-ovn

Also still running. This could be 50:50 (well, closer to 25:75). TBC.

e2e-powervs-capi-ovn

This job doesn't ever appear to have passed.

e2e-gcp-custom-dns

This should have passed and only two tests failed. I'll recheck on the assumption that they are flakes.

/test e2e-gcp-custom-dns

Overall, I think this should be good to go, but I'll hold of adding verified until you've seen this and agreed/disagreed, @patrickdillon

[patrickdillon]

/verified by multiple e2e-tests

I reviewed all the marginal test cases to ensure there are no regressions:
nutanix: infrastructure provisioned successfully
ibmcloud: install completed, e2es still in progress
powervs: seems the test is broken but ibmcloud uses the same provider
openstack: well, I defer to you!

Thanks for checking these so carefully

[openshift-ci-robot]

@patrickdillon: This PR has been marked as verified by multiple e2e-tests.

In response to this:

/verified by multiple e2e-tests

I reviewed all the marginal test cases to ensure there are no regressions:
nutanix: infrastructure provisioned successfully
ibmcloud: install completed, e2es still in progress
powervs: seems the test is broken but ibmcloud uses the same provider
openstack: well, I defer to you!

Thanks for checking these so carefully

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@stephenfin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-powervs-capi-ovn	f199ccb	link	false	/test e2e-powervs-capi-ovn
ci/prow/e2e-nutanix-ovn	f199ccb	link	false	/test e2e-nutanix-ovn
ci/prow/e2e-azure-ovn-shared-vpc	f199ccb	link	false	/test e2e-azure-ovn-shared-vpc
ci/prow/e2e-azurestack	f199ccb	link	false	/test e2e-azurestack

Full PR test history. Your PR dashboard.

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.