🌱 Bump CAPI to v1.9.0-beta.1

[EmilienM]

What this PR does / why we need it:

Bump to the latest CAPI:

• Updates go.mod with the new tag.
• Run make modules in root and orc/.
• Run make generate.
• Add new API violations from what has been generated.
• Add schemes into predicates (see ⚠️ Fix object logging in predicates cluster-api#11239)
• Import deprecated errors that are used in CAPO and make it explicit that they are deprecated and will be replaced by Conditions when time permits.

Issue #2259

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	fa6367c
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/673e48130cd2a200089a27e2
😎 Deploy Preview	https://deploy-preview-2251--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[EmilienM]

/hold
it's still in beta, but at least we have it ready and we can see how it works in our CI.

[EmilienM]

The tests fail because kubernetes-sigs/cluster-api#11317 which deprecates Failure* fields:
https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-openstack/2251/pull-cluster-api-provider-openstack-test/1856337619219124224/build-log.txt

@lentzi90 @mdbooth we should get rid of the FailureReason and FailureMessage. Do we want a transition step where we carry this interface in CAPO or switch to conditions to surface errors, outside of this PR in preparation of a bump to this version of CAPI?

[lentzi90]

I think it depends on how much work it would be to switch. If we can do that pretty easily, let's just get it done. Otherwise, let's ignore the deprecation warning and give ourselves more time to work on it in the mean time.

[EmilienM]

/hold cancel

[EmilienM]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilienM

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

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

[lentzi90]

Great job!

Do we want to take this in already or wait for the final release?
One thing I am wondering about is also how the FailureMessage will now work. Previously, CAPI would propagate them up to the CAPI objects, but I'm guessing that would no longer happen in v1.9. That would mean that it is harder for users to detect when something is wrong.
If that it the case, should we rather hold off on this until we can transition to conditions instead?

[EmilienM]

Great job!

Do we want to take this in already or wait for the final release? One thing I am wondering about is also how the FailureMessage will now work. Previously, CAPI would propagate them up to the CAPI objects, but I'm guessing that would no longer happen in v1.9. That would mean that it is harder for users to detect when something is wrong. If that it the case, should we rather hold off on this until we can transition to conditions instead?

Yeah, that's a good point. I'm personally convinced that we will not release 0.12 until we get these conditions addressed, so we can probably live without the CAPO failures propagated to the CAPI objects.
Some platforms have bumped already (VSphere) but I suspect they already got rid of the conditions.
I'll let you and @mdbooth decide, but I'm in favour of bumping sooner rather than later.

[lentzi90]

Yeah I agree it is good to bump early and test it out properly. Shouldn't be a big deal to switch to conditions either.