Learn about Kubernetes cluster and create a simple cluster using Minikube.

During kubeadm init, kubeadm uploads the ClusterConfiguration object to your cluster in a ConfigMap called kubeadm-config in the kube-system namespace. This configuration is then read during kubeadm join, kubeadm reset and kubeadm upgrade. You can use kubeadm config print to print the default static configuration that kubeadm uses for kubeadm init and kubeadm join. Note: The output of the command is meant to serve as an example. You must manually edit the output of this command to adapt to your setup.

Bootstrap tokens are used for establishing bidirectional trust between a node joining the cluster and a control-plane node, as described in authenticating with bootstrap tokens. kubeadm init creates an initial token with a 24-hour TTL. The following commands allow you to manage such a token and also to create and manage new ones. kubeadm token create Create bootstrap tokens on the server Synopsis This command will create a bootstrap token for you.

kubeadm kubeconfig provides utilities for managing kubeconfig files. For examples on how to use kubeadm kubeconfig user see Generating kubeconfig files for additional users. kubeadm kubeconfig overview Kubeconfig file utilities Synopsis Kubeconfig file utilities. Options -h, --help help for kubeconfig Options inherited from parent commands --rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem. kubeadm kubeconfig user This command can be used to output a kubeconfig file for an additional user.

kubectl reference kubectl kubectl annotate kubectl api-resources kubectl api-versions kubectl apply kubectl attach ku...

Synopsis Create a service account with the specified name. kubectl create serviceaccount NAME [--dry-run=server|client|none] Examples # Create a new service account named my-service-account kubectl create serviceaccount my-service-account Options --allow-missing-template-keys     Default: true If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. --dry-run string[="unchanged"]     Default: "none" Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it.

Synopsis Display the current-context. kubectl config current-context [flags] Examples # Display the current-context kubectl config current-context Options -h, --help help for current-context --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group strings Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string     Default: "

Synopsis Unset an individual value in a kubeconfig file. PROPERTY_NAME is a dot delimited name where each token represents either an attribute name or a map key. Map keys may not contain dots. kubectl config unset PROPERTY_NAME Examples # Unset the current-context kubectl config unset current-context # Unset namespace in foo context kubectl config unset contexts.foo.namespace Options -h, --help help for unset --as string Username to impersonate for the operation.

Synopsis Edit a resource from the default editor. The edit command allows you to directly edit any API resource you can retrieve via the command-line tools. It will open the editor defined by your KUBE_EDITOR, or EDITOR environment variables, or fall back to 'vi' for Linux or 'notepad' for Windows. When attempting to open the editor, it will first attempt to use the shell that has been defined in the 'SHELL' environment variable.

In v1.15.0, kubeadm introduced preliminary support for kubeadm upgrade node phases. Phases for other kubeadm upgrade sub-commands such as apply, could be added in the following releases. kubeadm upgrade node phase Using this phase you can choose to execute the separate steps of the upgrade of secondary control-plane or worker nodes. Please note that kubeadm upgrade apply still has to be called on a primary control-plane node. phase preflight control-plane kubelet-config Use this command to invoke single phase of the node workflow