-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 KCP should update Kubeadm config map when setting imageRepository
#2807
🐛 KCP should update Kubeadm config map when setting imageRepository
#2807
Conversation
Signed-off-by: Naadir Jeewa <[email protected]>
/milestone v0.3.3 |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benmoss, vincepri 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 |
/retitle 🐛 KCP should update Kubeadm config map when setting |
imageRepository
imageRepository
imageRepository
@k8s-ci-robot hates emojis |
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
/hold
Feel free to unhold
a43711f
to
5213120
Compare
/hold cancel |
5213120
to
bedda68
Compare
/lgtm |
What this PR does / why we need it:
Fixes issues arising when a user specifies a global
imageRegistry
in theirclusterConfiguration
. We weren't updating the kubeadm configmap and so when we spun up new nodes kubeadm would still pull from the default registry.Which issue(s) this PR fixes
Fixes #2805