Fix broken links to testgrid dashboard

[AdityaVardhanSingh]

release-note
What type of PR is this?
/kind cleanup

What this PR does / why we need it:
The domain name of the testgrid dashboard was updated from k8s-testgrid.appspot.com to testgrid.k8s.io. After the update old domain now throws a 'page not found error'. So fixes the broken links of the testgrid dashboard.

Which issue(s) this PR fixes:
This is related to an umbrella issue and fixes a task of the same: kubernetes/test-infra#30370

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: AdityaVardhanSingh / name: Aditya Singh (3aa2f01)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AdityaVardhanSingh
Once this PR has been reviewed and has the lgtm label, please assign xing-yang for approval. For more information see the Kubernetes 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:

• release-tools/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]

Welcome @AdityaVardhanSingh!

It looks like this is your first PR to kubernetes-csi/csi-lib-utils 🎉. 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-csi/csi-lib-utils 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 @AdityaVardhanSingh. Thanks for your PR.

I'm waiting for a kubernetes-csi 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/test-infra repository.

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[AdityaVardhanSingh]

Hey, can you guys review this?

[pohly]

Don't modify release-tools in downstream repos like this one.

First csi-release-tools needs to be fixed (done in kubernetes-csi/csi-release-tools@1f7e605), then an automatic sync will copy that to the other repos.

[AdityaVardhanSingh]

@pohly which repo needs to be fixed next?

[pohly]

Please don't fix any further repos which have a "release-tools" directory.

[AdityaVardhanSingh]

Ok, thanks for clarifying @pohly , actually I am new to open source and didn't know much about upstream and downstream repos but thanks to you, your mention made me aware of it.