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

chrischdi commented 9 months ago

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: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/4471-cp-join-kubelet-local-apiserver/README.md
Discussion Link: https://github.com/kubernetes/kubeadm/issues/2271
Primary contact (assignee): @chrischdi
Responsible SIGs: Cluster Lifecycle
Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): 1.31
- Beta release target (x.y):
- Stable release target (x.y):
[x] Alpha
- [x] KEP (k/enhancements) update PR(s):
- https://github.com/kubernetes/enhancements/pull/4496
- https://github.com/kubernetes/enhancements/pull/4759
- [x] Code (k/k) update PR(s):
- https://github.com/kubernetes/kubernetes/pull/125582
- https://github.com/kubernetes/kubernetes/pull/125780
- [x] Docs (k/website) update PR(s): https://github.com/kubernetes/website/pull/46945
- [x] kuebadm (k/kubeadm) and Test-infra (k/test-infra): update PR(s):
- https://github.com/kubernetes/kubeadm/pull/3080
- https://github.com/kubernetes/test-infra/pull/32858

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

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

neolit123 commented 9 months ago

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 commented 8 months ago

@chrischdi FYI, there is a PR that has been in review for a long time but it may merge in 1.30: https://github.com/kubernetes/kubernetes/pull/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 commented 8 months ago

@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 commented 5 months ago

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 commented 5 months ago

/remove-lifecycle stale

k8s-triage-robot commented 2 weeks ago