🌱 Bump CAPI to v1.11.1

[changjjjjjjj]

What this PR does / why we need it:
Bumps the Cluster API dependency to release v1.11.1. Also bumps go version to fix CVEs

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 #413

[k8s-ci-robot]

Welcome @changjjjjjjj!

It looks like this is your first PR to kubernetes-sigs/cluster-api-addon-provider-helm 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-addon-provider-helm has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @changjjjjjjj. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[mboersma]

/ok-to-test

[changjjjjjjj]

Hi @jackfrancis @Jont828 @mboersma , this PR removes deprecated status clusterv1.conditions from the status field. As you can check from e2e test results, I think the changes do not affect controller behavior. I will appreciate if you give an opinion about ignoring apidiff test failure.

[jackfrancis]

@changjjjjjjj I'll let @mboersma do an audit of the v1beta2 changes, in the meantime you could rebase this PR to overcome that blocker

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: changjjjjjjj
Once this PR has been reviewed and has the lgtm label, please assign jackfrancis for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: changjjjjjjj
Once this PR has been reviewed and has the lgtm label, please assign jackfrancis for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[Jont828]

Ty for the contribution! Looks like you need a rebase btw. I'll take a look as well but if tests pass I think we should be in good shape.

[Jont828]

Can you add a newline at the end here? And same for the other files.

[changjjjjjjj]

I rebased and added newlines as you mentioned. It would be grateful if you give opinions about apidiff test.

[scrothers]

What do we need to do in order to get this merged? The author @changjjjjjjj appears to have abandoned this.

[jackfrancis]

@scrothers you could submit a PR of these changes yourself

[k8s-ci-robot]

@changjjjjjjj: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-addon-provider-helm-apidiff-main	e4d3ace	link	false	/test pull-cluster-api-addon-provider-helm-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.