Use registry.k8s.io for deployment#372
Conversation
|
Welcome @AdityaC45! |
|
Hi @AdityaC45. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
| containers: | ||
| - name: csi-attacher | ||
| image: gcr.io/k8s-staging-sig-storage/csi-attacher:canary | ||
| image: registry.k8s.io/k8s-staging-sig-storage/csi-attacher:canary |
There was a problem hiding this comment.
Use registry.k8s.io/sig-storage/csi-attacher:v3.5.0. I don't see :canary builds in registry.k8s.io.
There was a problem hiding this comment.
Ok, I didn't check that, will update this PR
|
/ok-to-test |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AdityaC45, jsafrane The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/release-note-none |
|
@humblec: you can not set the release note label to "release-note-none" because the PR has the label "kind/deprecation". DetailsIn response to this:
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. |
|
@AdityaC45 can you correct the release note section in the PR description ? |
|
@AdityaC45: you can not set the release note label to "release-note-none" because the PR has the label "kind/deprecation". DetailsIn response to this:
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. |
|
/kind cleanup |
|
@AdityaC45: you can not set the release note label to "release-note-none" because the PR has the label "kind/deprecation". DetailsIn response to this:
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. |
|
/remove-kind deprecation |
|
@AdityaC45: you can not set the release note label to "release-note-none" because the PR has the label "kind/deprecation". DetailsIn response to this:
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. |
|
/release-note-none |
What type of PR is this?
/kind feature
/label release-note-none
What this PR does / why we need it:
Related to:
kubernetes-csi/external-snapshotter#687
Switch to the new endpoint for container images. See: https://github.com/kubernetes/k8s.io/wiki/New-Registry-url-for-Kubernetes-(registry.k8s.io)
Special notes for your reviewer:
registry.k8s.io is currently a redirect to k8s.gcr.io. The change should be transparent to any pulling from k8s.gcr.io.
Does this PR introduce a user-facing change?:
NONE