-
Notifications
You must be signed in to change notification settings - Fork 1
chore: migrate from k8s.gcr.io to registry.k8s.io #142
chore: migrate from k8s.gcr.io to registry.k8s.io #142
Conversation
@ahmedwaleedmalik: GitHub didn't allow me to assign the following users: your_reviewer. Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In 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. |
Welcome @ahmedwaleedmalik! It looks like this is your first PR to openyurtio/yurt-app-manager 🎉 |
Codecov Report
@@ Coverage Diff @@
## master #142 +/- ##
==========================================
+ Coverage 45.14% 45.21% +0.06%
==========================================
Files 42 42
Lines 4782 4782
==========================================
+ Hits 2159 2162 +3
+ Misses 2320 2318 -2
+ Partials 303 302 -1
Flags with carried forward coverage won't be shown. Click here to find out more. see 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, rambohe-ch 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 |
/lgtm |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Kubernetes is migrating its image registry from k8s.gcr.io to registry.k8s.io.
Part of kubernetes/k8s.io#4780.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
other Note