-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Use k8s.gcr.io for kubernetes related images #5764
Use k8s.gcr.io for kubernetes related images #5764
Conversation
/assign @LuckySB |
Pipeline passed but GitHub didn't get the completion feedback apparently. |
#5646 is updating and fixing metrics-server for 1.16, I'll remove it from my PR |
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.
Looks good
3565868
to
8c7ae26
Compare
169c120
to
ce82825
Compare
Looks good, let's see what CI says /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EppO, Miouge1 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 |
* Use k8s.gcr.io for kubernetes related images * Use k8s.gcr.io in inventory sample
* Use k8s.gcr.io for kubernetes related images (#5764) * Use k8s.gcr.io for kubernetes related images * Use k8s.gcr.io in inventory sample * [2.12] Update hashes and set default version to 1.16.14 * [2.12] Update hashes and set default version to 1.16.15 Co-authored-by: Florent Monbillard <f.monbillard@gmail.com>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
gcr.io/google-containers
will be replaced bygcr.io/k8s-artifacts-prod
soon (early April). Using k8s.gcr.io should be safe until the cutoff is done and even after.Which issue(s) this PR fixes:
Fixes #5711
Special notes for your reviewer:
I didn't address the dashboard image as they moved it to dockerhub for the latest releases. Current version is actually not compatible with 1.16.x. It should be addressed in a separate PR.
Does this PR introduce a user-facing change?: