remove invalid caBundle from CRDs

[nojnhuh]

What type of PR is this?
/kind bug

What this PR does / why we need it:

This change removes invalid caBundles from our CRDs to enable running CAPZ in a Kubernetes 1.31 management cluster per the CAPI migration guide to 1.8: https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.7-to-v1.8

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:

• cherry-pick candidate

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

NONE

[nojnhuh]

/cherry-pick release-1.17

[k8s-infra-cherrypick-robot]

@nojnhuh: once the present PR merges, I will cherry-pick it on top of release-1.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.17

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.

[jackfrancis]

Can we cherry-pick this into v1.16 as well?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.35%. Comparing base (da6ca56) to head (b4ca0dc).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5172   +/-   ##
=======================================
  Coverage   51.35%   51.35%           
=======================================
  Files         273      273           
  Lines       24670    24670           
=======================================
  Hits        12670    12670           
  Misses      11211    11211           
  Partials      789      789           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nojnhuh]

Yeah that should be fine. I was naively associating this only with CAPI 1.8 (which we don't import on our 1.16 branch) but I don't see where that would actually matter assuming this doesn't break any tests.

/cherry-pick release-1.16

[k8s-infra-cherrypick-robot]

@nojnhuh: once the present PR merges, I will cherry-pick it on top of release-1.16 in a new PR and assign it to you.

In response to this:

Yeah that should be fine. I was naively associating this only with CAPI 1.8 (which we don't import on our 1.16 branch) but I don't see where that would actually matter assuming this doesn't break any tests.

/cherry-pick release-1.16

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.

[willie-yao]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: willie-yao

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 [willie-yao]

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

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 966371fa550364b5a0330028d2de20f102209927

[nojnhuh]

/retest

[nojnhuh]

/retest

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #5174

In response to this:

/cherry-pick release-1.17

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.

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #5175

In response to this:

Yeah that should be fine. I was naively associating this only with CAPI 1.8 (which we don't import on our 1.16 branch) but I don't see where that would actually matter assuming this doesn't break any tests.

/cherry-pick release-1.16

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.