🌱 Bump Cluster API to v1.5.2

[killianmuldoon]

Bump Cluster API to its latest patch release.

Release notes here: https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.5.2

[killianmuldoon]

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.8

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/test-infra repository.

[killianmuldoon]

Not sure what our feeling is on backporting these updates to older branches. It looks like we definitely backported v1.5.1 to 1.8, but release 1.7 and older aren't on latest patch releases.

I'm fine to keep that as the pattern for now, but maybe we should consider updating release-1.7 to CAPI v1.4.7?

@chrischdi @fabriziopandini WDYT?

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (ed46a47) 60.87% compared to head (3ef3ab7) 60.88%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2401      +/-   ##
==========================================
+ Coverage   60.87%   60.88%   +0.01%     
==========================================
  Files         164      164              
  Lines        9473     9473              
==========================================
+ Hits         5767     5768       +1     
+ Misses       3293     3292       -1     
  Partials      413      413              

see 7 files with indirect coverage changes

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

[zhanggbj]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d20bbfaa589bb0155b6ae11f4617c1068c3513ae

[chrischdi]

Not sure what our feeling is on backporting these updates to older branches. It looks like we definitely backported v1.5.1 to 1.8, but release 1.7 and older aren't on latest patch releases.

I'm fine to keep that as the pattern for now, but maybe we should consider updating release-1.7 to CAPI v1.4.7?

@chrischdi @fabriziopandini WDYT?

+1 to backporting:

• v1.5.2 to release-1.8
• v1.4.7 to release-1.7

[chrischdi]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi

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

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

[k8s-infra-cherrypick-robot]

@killianmuldoon: #2401 failed to apply on top of branch "release-1.8":

Applying: Bump Cluster API to v1.5.2
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump Cluster API to v1.5.2
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.8

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/test-infra repository.

[killianmuldoon]

Will do the backports manually