Eric Paris Jan 2015
kubeadm join phase control-plane-prepare all [Options]
Prepare the machine for serving a control plane
--apiserver-advertise-address="" If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
--apiserver-bind-port=6443 If the node should host a new control plane instance, the port for the API Server to bind to.
--certificate-key="" Use this key to decrypt the certificate secrets uploaded by init.
--config="" Path to kubeadm config file.
--control-plane=false Create a new control plane instance on this node
--discovery-file="" For file-based discovery, a file or URL from which to load cluster information.
--discovery-token="" For token-based discovery, the token used to validate cluster information fetched from the API server.
--discovery-token-ca-cert-hash= For token-based discovery, validate that the root CA public key matches this hash (format: ":").
--discovery-token-unsafe-skip-ca-verification=false For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
--experimental-patches="" Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.
--node-name="" Specify the node name.
--tls-bootstrap-token="" Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
--token="" Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
Options Inherited from Parent Commands
--azure-container-registry-config="" Path to the file containing Azure container registry configuration information.
--log-flush-frequency=5s Maximum number of seconds between log flushes
--rootfs="" [EXPERIMENTAL] The path to the 'real' host root filesystem.
--version=false Print version information and quit
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!