Bump k8s to 1.29 versions

[Neo2308]

Description of the change:

• Bump k8s dependencies to 0.29.3
• Bump other operator-framework lib versions to support k8s 0.29.x
• Bump ginkgo/v2 to v2.17.2

TODO:

• Update operator-framework/ansible-operator-plugins after Update k8s dependencies ansible-operator-plugins#67 is merged
• Add changelog
• Regenerate testdata

Motivation for the change:

• Closes: Meta Issue for k8s 1.29 bump #6651
• Closes: Meta: Important Issues Needing Resolution Before New Release #6767
• Fixes: quickstart does not work #6681

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

[Neo2308]

@joelanford, @everettraven, @acornett21 could you review this PR?

[acornett21]

@Neo2308 This doesn't have the proper version of the ansilbe-plugin, I'll work on releasing today. Also, it doesn't have the proper version of the helm plugin, since we'll need to backfill that to have a matching version of kubebuilder.

[acornett21]

@Neo2308 ansible-operator-plugin v1.35.0` has been released for you to use.

[acornett21]

@Neo2308 Can you pull this version in for the java plugin?
https://github.com/operator-framework/java-operator-plugins/releases/tag/v0.10.0

[acornett21]

Hi @Neo2308 Sorry for the delay, but it took 11 PR's to get the helm-operator-plugin backfilled to the proper version of kubebuilder.

You can use this version in this PR
https://github.com/operator-framework/helm-operator-plugins/releases/tag/v0.2.2

I think after this all the deps are in proper shape, we'd just have to look to make sure all scaffolding/testing/etc passes CI.

[Neo2308]

@acornett21 any idea how to fix the failing docs sanity?

[acornett21]

@Neo2308 I'm unsure, I don't have access to the routes/etc for the website. I asked here in slack about this and for additional reviews.

I'll spend sometime tomorrow reviewing/testing this myself as well.

[chiragkyal]

Hey, if there isn't any problem with version compatibility, is it possible to bump Helm to v3.15.0, which can also help fix CVE-2019-25210?

[acornett21]

There is a problem with version compatibility, 3.15 is based off of k8s 1.30, so if helm was updated here it would also update k8s which is not what we want. That version will be part of the k8s 1.30 work.

[chiragkyal]

Makes sense. Thanks a lot, @acornett21.

[acornett21]

@Neo2308 Doing some testing today, and am updating the PR description as I find more issues this fixes/closes.

[acornett21]

I've tested all the things I care to test and everything looks good.

[acornett21]

Hi @Neo2308 Can you change the below?

https://github.com/operator-framework/operator-sdk/blob/master/website/config.toml#L202

to
https://github.com/operator-framework/operator-sdk/tree/v1.20.x/website/content/en/docs

It seems like there is a limit on the number of subdomains. Thanks.

[varshaprasad96]

Apart from the change made in website/config.toml, rest of it looks good! Changing that would end up triggering a change in netlify configuration (iirc), and that's something we don't want in this PR. Could you please revert it back?

@Neo2308 Thanks for the contribution! Rest of the changes look good!

/lgtm after its reverted.

[varshaprasad96]

I think this should be reverted back. This change is made only with the release PR.

[acornett21]

This is needed since v1-20-x is no longer a subdomain, without this change the docs GHA fails