kubeadm: make a control-plane's kubelet talk to the local API Server on kubeadm join.

[chrischdi]

Enhancement Description

• One-line enhancement description (can be used as a release note): Make the control-plane's kubelet talk to the local API Server on kubeadm join.
• Kubernetes Enhancement Proposal: KEP-4471: kubeadm: make a control-plane's kubelet talk to the local API Server on kubeadm join. #4496
• Discussion Link: make components on control-plane nodes point to the local API server endpoint kubeadm#2271
• Primary contact (assignee): @chrischdi
• Responsible SIGs: Cluster Lifecycle
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

• make components on control-plane nodes point to the local API server endpoint kubeadm#2271 (comment)
• Kubeadm office hours from 31st January 2024

cc @neolit123 : we discussed that this may not get tracked by enhancement tracking.

[neolit123]

we discussed that this may not get tracked by enhancement tracking.

yes, we are not going to opt-in for enhancement tracking for this feature.

[neolit123]

@chrischdi FYI, there is a PR that has been in review for a long time but it may merge in 1.30:
kubernetes/kubernetes#119598

we are thinking of adding a new dedicated join phase behind a feature gate, that waits for all k8s CP components (not etcd) to be ready.
basically ALA wait-control-plane for join.
note that it might conflict / mix things a little with this KEP.

[chrischdi]

@chrischdi FYI, there is a PR that has been in review for a long time but it may merge in 1.30: kubernetes/kubernetes#119598

we are thinking of adding a new dedicated join phase behind a feature gate, that waits for all k8s CP components (not etcd) to be ready. basically ALA wait-control-plane for join. note that it might conflict / mix things a little with this KEP.

Thanks for the heads up: it does not conflict with this proposal :-) it introduces stuff which happens after the parts this touches.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[neolit123]

/remove-lifecycle stale