Skip to content

RFE: Document the kubeadm roadmap #2315

Open
@fabriziopandini

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/documentationCategorizes issue or PR as related to documentation.kind/tracking-issuelifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions