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
Manual-cherry-pick-for-1.23: kubeadm: apply registry.k8s.io changes #113393
Manual-cherry-pick-for-1.23: kubeadm: apply registry.k8s.io changes #113393
Conversation
28f3644
to
336d440
Compare
Update constants, API types, and unit tests to use the new registry location. Update dependencies.yaml as well.
336d440
to
d8f8c52
Compare
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.
/lgtm
/approve
6f16e72
to
6dddbb3
Compare
/lgtm |
….io" If the user runs "kubeadm upgrade apply", kubeadm can download a configuration from the cluster. If the configuration contains the legacy default imageRepository of "k8s.gcr.io", mutate it to the new default of "registry.k8s.io" and update the configuration in the config map. During "upgrade node/diff" download the configuration, mutate the image repository locally, but do not mutate the in-cluster value. That is done only on "apply". This ensures that users are migrated from the old default registry domain.
/retest |
2 similar comments
/retest |
/retest |
/lgtm |
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.
/lgtm
/approve
/assign @BenTheElder |
/approve |
@cpanato can we get this in as it's also keeping one of the kubeadm upgrade jobs broken? |
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.
/triage accepted
/priority important-soon
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, dims, neolit123, pacoxu, SataQiu 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 |
/test pull-kubernetes-e2e-kind-ipv6 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
manual, kubeadm scoped backport of:
#109938
#110343
Which issue(s) this PR fixes:
xref kubernetes/kubeadm#2671
Special notes for your reviewer:
it is essentially a feature backport, as discussed with k8s-infra and sig-release
https://kubernetes.slack.com/archives/C2C40FMNF/p1666723622759119
kubernetes/kubeadm#2671 (comment)
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: