-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update registry k8s.gcr.io -> registry.k8s.io #172
Conversation
severity-ratings.md
Outdated
@@ -21,7 +21,7 @@ but you can specifically think of `kube-apiserver` and `kubelet` being the main | |||
|
|||
- Components built from source in the `kubernetes` github organization and | |||
[all current organizations in use](https://git.k8s.io/community/github-management/README.md#actively-used-github-organizations) | |||
- Container images under the `k8s.gcr.io` repository | |||
- Container images under the `registry.k8s.io` repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will support both registries in regards to vulnerabilities. Removing the reference to the old registry is not valid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @enj , so is it better I add it as a separate line? Or is it not needed at all?
@ArkaSaha30 please rebase and squash into one commit. |
6fc8754
to
449654d
Compare
Signed-off-by: ArkaSaha30 <[email protected]>
449654d
to
3bcd36d
Compare
Done @enj 👍 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ArkaSaha30, enj 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:
Approvers can indicate their approval by writing |
This PR will update the uses of deprecating
k8s.gcr.io
registry toregistry.k8s.io
prior to the planned April freeze.Tracking Issue: kubernetes/k8s.io#4738
Search results: https://cs.k8s.io/?q=k8s.gcr.io&i=nope&files=&excludeFiles=vendor%2F&repos=kubernetes/committee-security-response