Bump to Cluster API v1.7

[sbueringer]

Just an umbrella issue to collect follow-up tasks once we bumped to Cluster API v1.7 (to be released in April 2024):

• Ensure we don't add "component", "remote/clustercachetracker" twice. Since 🐛 Improve log k/v pairs and a improve/drop a few log lines cluster-api#9813 it is added by the CCT automatically
  • PR: 🌱 Drop duplicate ClusterCacheTracker log name #2863
• Bump to Go 1.21
  • PR 🌱 Bump go 1.21 #2741
  • Cherry-pick into release-1.9, release-1.8, release-1.7
    • [release-1.9] 🌱 Bump to Go 1.21 #2744
    • [release-1.8] 🌱 Bump to Go 1.21 #2743
    • [release-1.7] 🌱 Bump to Go 1.21 #2745
• Drop test/infrastructure/tmp added in ✨ Add vcsim server provider #2613
  • Done. Didn't lookup which PR but it's not important
• Adapt to 🌱 Improve patch helper error handling #2865 @zhanggbj
• Start using release markers in our e2e config: 🌱 Use release markers in e2e config to fetch lastest releases #2895 @zhanggbj

[zhanggbj]

Hey @sbueringer,
I would like to work on this one if it is still available

• Adapt to 🌱 Improve patch helper error handling cluster-api#9946

[sbueringer]

@zhanggbj sounds good. Thank you!

[zhanggbj]

Hey @sbueringer ,

I just want to double-check the target of this item.

• Start using release markers in our e2e config: ✨ Resolve release markers cluster-api#9265

The intention is to replace the current hard-coded providers' versions with release markers, so that e2e test could fetch the latest and stable releases?

And if yes, I would like to pick up this one :-)

[sbueringer]

The intention is to replace the current hard-coded providers' versions with release markers, so that e2e test could fetch the latest and stable releases?

Yup. The idea is that we basically configure a release series (e.g. v1.6.x) via markers and the tests always use the latest patch version.

Assigned you. Thx!

[sbueringer]

Closing this issue. The mandatory parts of the CAPI bump are done. I see #2895 more as an async follow-up (that we'll complete in the next 1-2 weeks)

[sbueringer]

/close

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

/close

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.