[Umbrella Issue] Update the mentions of testgrid dashboard URL from k8s-testgrid.appspot.com to testgrid.k8s.io
letmerecall opened this issue · 18 comments
What happened:
Somewhere down the line, 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'. There're numerous links to the old testgrid dashboard's domain which across many projects now stands broken.
Related slack conversation: https://kubernetes.slack.com/archives/C09QZ4DQB/p1689609631562029?thread_ts=1689589511.968429&cid=C09QZ4DQB
What you expected to happen:
This issue aims to track the update of the testgrid dashboard's URL across different projects. Once updated we expect to have no broken links to the testgrid dashboard.
How to reproduce it (as minimally and precisely as possible):
Visit: https://k8s-testgrid.appspot.com
Projects:
Repos/projects where the link to the old testgrid dashboard domain (k8s-testgrid.appspot.com) was found by doing a cs.k8s.io search.
- kubernetes/enhancements | search result | kubernetes/enhancements#4154
- kubernetes/sig-release | search result | kubernetes/sig-release#2305
- kubernetes/community | search result | kubernetes/community#7472
- kubernetes/test-infra | search result | #30371
- kubernetes/website | search result | kubernetes/website#42538 (Maintaining old blogs are discouraged)
- kubernetes-sigs/lwkd | search result | kubernetes-sigs/lwkd#216
- kubernetes/kubeadm | search result | kubernetes/kubeadm#2918
- kubernetes/kubernetes | search result | kubernetes/kubernetes#119934
- kubernetes/release | search result | kubernetes/release#3211
- kubernetes-csi/csi-driver-nfs | search result | kubernetes-csi/csi-driver-nfs#500
- kubernetes-csi/csi-driver-smb | search result | kubernetes-csi/csi-driver-smb#654
- kubernetes-csi/csi-test | search result | kubernetes-csi/csi-test#477
- kubernetes/autoscaler | search result | kubernetes/autoscaler#6036
- kubernetes/ingress-gce | search result | kubernetes/ingress-gce#2237
- kubernetes-csi/csi-driver-host-path | search result | (subtree)
- kubernetes-csi/csi-driver-iscsi | search result | (subtree)
- kubernetes-csi/csi-driver-nvmf | search result | (subtree)
- kubernetes-csi/csi-lib-utils | search result | (subtree)
- kubernetes-csi/csi-proxy | search result | (subtree)
- kubernetes-csi/csi-release-tools | search result | kubernetes-csi/csi-release-tools#234
- kubernetes-csi/external-attacher | search result |
- kubernetes-csi/external-health-monitor | search result | (subtree)
- kubernetes-csi/external-provisioner | search result |
- kubernetes-csi/external-resizer | search result |
- kubernetes-csi/external-snapshotter | search result |
- kubernetes-csi/lib-volume-populator | search result |
- kubernetes-csi/livenessprobe | search result |
- kubernetes-csi/node-driver-registrar | search result |
- kubernetes-csi/volume-data-source-validator | search result | (subtree)
- kubernetes-sigs/gluster-block-external-provisioner | search result | (subtree)
- kubernetes-sigs/gluster-file-external-provisioner | search result | (sidecar)
- kubernetes-sigs/nfs-ganesha-server-and-external-provisioner | search result | (subtree)
- kubernetes-sigs/nfs-subdir-external-provisioner | search result | kubernetes-sigs/nfs-subdir-external-provisioner#302 (subtree)
- kubernetes/dns | search result | kubernetes/dns#595
- kubernetes/kubectl | search result | kubernetes/kubectl#1476 (subtree)
- kubernetes/node-problem-detector | search result | kubernetes/node-problem-detector#794
- kubernetes/perf-tests | search result | kubernetes/perf-tests#2307
- kubernetes-sigs/gcp-compute-persistent-disk-csi-driver | search result | kubernetes-sigs/gcp-compute-persistent-disk-csi-driver#1407
- kubernetes-sigs/hierarchical-namespaces | search result | kubernetes-sigs/hierarchical-namespaces#333
- kubernetes/design-proposals-archive | search result | (repository archived)
How can the assignee reach out for help?
You can have a look at this similar PR: kubernetes/sig-release#2305
Or
Ask your questions in the comment.
NOTE: Please mention this issue in your PR so that it can be tracked and duplicate work can be minimised.
/sig testing
/kind cleanup
Hi @neolit123 , I have done the changes in the kubeadm repository. I have also opened the pr for the same.
/good-first-issue
@letmerecall:
This request has been marked as suitable for new contributors.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.
In response to this:
/good-first-issue
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.
I'll be working on the kuberenetes/community related changes as it doesn't seem anyone has started work on it.
I'll be working on the kuberenetes/community related changes as it doesn't seem anyone has started work on it.
Thanks @Ritikaa96! Feel free to reference this issue in your PR :)
I've created PR for k/release repo @letmerecall feel free to review/update in this issue
kubernetes/release#3211
/assign
Hey, can I make a PR for this issue?
Hey, can I make a PR for this issue?
Sure @AdityaVardhanSingh, feel free to make a PR in any of the affect repositoriy.
This Issue isnt closed yet
/reopen
@Ritikaa96: Reopened this issue.
In response to this:
This Issue isnt closed yet
/reopen
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.
Not closed yet.
/reopen
@letmerecall: Reopened this issue.
In response to this:
Not closed yet.
/reopen
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.
This issue isnt closed yet
/reopen
@Ritikaa96: Reopened this issue.
In response to this:
This issue isnt closed yet
/reopen
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.
Hello. I would like to work on this issue, may I?
Hello. I would like to work on this issue, may I?
Thanks for the help @maclo2012, but I think we have all the tasks either completed or in review for this issue :)