.nh .TH KUBERNETES(1) kubernetes User Manuals Eric Paris Jan 2015 .SH NAME kubeadm - kubeadm: easily bootstrap a secure Kubernetes cluster .SH SYNOPSIS \fBkubeadm\fP [OPTIONS] .SH DESCRIPTION .EX ┌──────────────────────────────────────────────────────────┐ │ KUBEADM │ │ Easily bootstrap a secure Kubernetes cluster │ │ │ │ Please give us feedback at: │ │ https://github.com/kubernetes/kubeadm/issues │ └──────────────────────────────────────────────────────────┘ .EE .PP Example usage: .EX Create a two-machine cluster with one control-plane node (which controls the cluster), and one worker node (where your workloads, like Pods and Deployments run). ┌──────────────────────────────────────────────────────────┐ │ On the first machine: │ ├──────────────────────────────────────────────────────────┤ │ control-plane# kubeadm init │ └──────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────┐ │ On the second machine: │ ├──────────────────────────────────────────────────────────┤ │ worker# kubeadm join │ └──────────────────────────────────────────────────────────┘ You can then repeat the second step on as many other machines as you like. .EE .SH OPTIONS \fB--rootfs\fP="" The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. .PP \fB--version\fP=false --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version .SH SEE ALSO \fBkubeadm-alpha(1)\fP, \fBkubeadm-certs(1)\fP, \fBkubeadm-completion(1)\fP, \fBkubeadm-config(1)\fP, \fBkubeadm-init(1)\fP, \fBkubeadm-join(1)\fP, \fBkubeadm-kubeconfig(1)\fP, \fBkubeadm-reset(1)\fP, \fBkubeadm-token(1)\fP, \fBkubeadm-upgrade(1)\fP, \fBkubeadm-version(1)\fP, .SH HISTORY January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!