Skip to content
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

Kubeadm Config versioning #2498

Closed
4 tasks
shekhar-rajak opened this issue Feb 12, 2021 · 3 comments
Closed
4 tasks

Kubeadm Config versioning #2498

shekhar-rajak opened this issue Feb 12, 2021 · 3 comments
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@shekhar-rajak
Copy link
Member

shekhar-rajak commented Feb 12, 2021

Enhancement Description

  • One-line enhancement description (can be used as a release note): Kubeadm Config versioning
  • Kubernetes Enhancement Proposal:

Kubeadm uses MasterConfiguraton for two distinct but similar operations: Initialising a new cluster and upgrading an existing cluster.
The former is typically created by hand by an administrator.
It is stored on disk and passed to kubeadm init via command line flag.
The latter is produced by kubeadm using supplied configuration files, command line options, and internal defaults.
It will be stored in a ConfigMap so upgrade operations can find.

Right now the configuration format is unversioned.
This means configuration file formats can change between kubeadm versions and there's no safe way to update the configuration format.

We propose a stable versioning of this configuration, v1alpha2 and eventually v1beta1.
Version information will be mandatory going forward, both for user-generated configuration files and machine-generated configuration maps.

There as an existing document describing current Kubernetes best practices around component configuration.

  • Discussion Link:
  • Primary contact (assignee): @liztio
  • Responsible SIGs: sig-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.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 12, 2021
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Feb 12, 2021

@shekhar-rajak: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@shekhar-rajak
Copy link
Member Author

shekhar-rajak commented Feb 12, 2021

Migrating all the old template keps to new template : #2499

@neolit123
Copy link
Member

neolit123 commented Feb 13, 2021

this proposal was only about how to versioning the config.
it was accepted and does not follow the alpha/beta/ga model.

so we can close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants