RFE: Document the kubeadm roadmap

[fabriziopandini]

Kubeadm was created in 2016 and then graduated GA in 2018, and, In order to continue to provide the best user experience to our users, we should start drafting a new roadmap for defining.

This issues should act as a focal point for collecting items to be included in this roadmap; each item should be discussed in a separated issue, and linked here for visibility

-- note from kubeadm office hours 09-30-2020
This list does not express a commitment to implement a feature nor implementation priorities.
As stated above, item are linked here for visibility, but each issue should be discussed separately.

As soon as we will be ready, we will create a roadmapa.md document, documenting maintainers' agreement on the relevance of a selected list of issues/topics for the future of kubeadm.

Implementation priorities will be discussed as usual in the planning session/office hours meetings according to the availability of people willing to work on each issue/topic.

Implementation details will be defined in KEPs, if required, on directly on each issue.

[fabriziopandini]

Create the kubeadm library #2316

[fabriziopandini]

Improve kubeadm support for declarative approaches/git-ops #2317

[fabriziopandini]

Improve kubeadm support for pluggable addons / operator driven addons #2318

[fabriziopandini]

Support node-specific configurations #2367

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fabriziopandini]

/remove-lifecycle stale

[neolit123]

We have seen user requests for kubeadm to allow node-role labels. There was a k/k issue too but i cannot find it. This is something the operator can support:
#2509

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[TBBle]

/lifecycle frozen

This is an issue for tracking other issues, I'm not sure "activity" is the right metric for closing this.