The purpose of this repo is to aggregate issues filed against the kubeadm component.
NOTE: This issue tracker is not designated for providing support for kubeadm users. Please see the Support section below.
Kubeadm is a tool built to provide best-practice "fast paths" for creating Kubernetes clusters. It performs the actions necessary to get a minimum viable, secure cluster up and running in a user-friendly way. Kubeadm's scope is limited to the local node filesystem and the Kubernetes API, and it is intended to be a composable building block of higher level tools.
- kubeadm init to bootstrap the initial Kubernetes control-plane node.
- kubeadm join to bootstrap a Kubernetes worker node or an additional control plane node, and join it to the cluster.
- kubeadm upgrade to upgrade a Kubernetes cluster to a newer version.
- kubeadm reset to revert any changes made to this host by kubeadm init or kubeadm join.
Only log issues here if you think there is an actual bug or if you have a feature request.
The Kubernetes and kubeadm troubleshooting guides can be found here:
Support requests should be sent to the community support channels or #kubeadm on the k8s Slack:
- Installing kubeadm
- Creating a cluster
- Command-line reference
- Customizing components
- Certificate management
- Configuration API reference
- Configuration API reference (godoc) (pick an API version from the list of packages)
Learn how to engage with the Kubernetes community on the community page.
You can reach the maintainers of this project at the Cluster Lifecycle SIG.
The full picture of which direction we're taking is described in this blog post.
Please also refer to the latest milestones in this repo.
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.