🌱 Update RKE2 provider URL

[yiannistri]

What this PR does / why we need it:

The CAPRKE2 repository was recently moved from https://github.com/rancher-sandbox/cluster-api-provider-rke2 to https://github.com/rancher/cluster-api-provider-rke2 so GitHub redirects any requests to the old repo URL, to the new repo URL. This change simply updates the CAPRKE2 provider URL to point to the new repo .

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 #

/area clusterctl

[linux-foundation-easycla]

• ✅login: yiannistri / (21f58aa)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @yiannistri!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. 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 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 @yiannistri. 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.

[furkatgofurov7]

Thanks @yiannistri, great catch, LGTM.

/lgtm

cc @sbueringer

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 06d55e70519ab6addbe7fec19598a1b15202d55c

[furkatgofurov7]

/ok-to-test

[sbueringer]

Thx!

/lgtm
/approve

@furkatgofurov7 Feel free to cherry-pick to supported releases if you want

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

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

[furkatgofurov7]

/cherry-pick release-1.8
/cherry-pick release-1.7

[k8s-infra-cherrypick-robot]

@furkatgofurov7: new pull request created: #11225

In response to this:

/cherry-pick release-1.8
/cherry-pick release-1.7

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.

[furkatgofurov7]

/cherry-pick release-1.7

[k8s-infra-cherrypick-robot]

@furkatgofurov7: new pull request created: #11226

In response to this:

/cherry-pick release-1.7

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.