**kubeadm** helps you bootstrap a minimum viable Kubernetes cluster that conforms to best practices. With kubeadm, your cluster should pass [Kubernetes Conformance tests](https://kubernetes.io/blog/2017/10/software-conformance-certification). Kubeadm also supports other cluster
+lifecycle functions, such as upgrades, downgrade, and managing [bootstrap tokens](/docs/reference/access-authn-authz/bootstrap-tokens/).
+
+Because you can install kubeadm on various types of machine (e.g. laptop, server,
+Raspberry Pi, etc.), it's well suited for integration with provisioning systems
+such as Terraform or Ansible.
+
+kubeadm's simplicity means it can serve a wide range of use cases:
+
+- New users can start with kubeadm to try Kubernetes out for the first time.
+- Users familiar with Kubernetes can spin up clusters with kubeadm and test their applications.
+- Larger projects can include kubeadm as a building block in a more complex system that can also include other installer tools.
+
+kubeadm is designed to be a simple way for new users to start trying
+Kubernetes out, possibly for the first time, a way for existing users to
+test their application on and stitch together a cluster easily, and also to be
+a building block in other ecosystem and/or installer tool with a larger
+scope.
+
+You can install _kubeadm_ very easily on operating systems that support
+installing deb or rpm packages. The responsible SIG for kubeadm,
+[SIG Cluster Lifecycle](https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle), provides these packages pre-built for you,
+but you may also on other OSes.
+
+
+### kubeadm Maturity
+
+| Area | Maturity Level |
+|---------------------------|--------------- |
+| Command line UX | beta |
+| Implementation | beta |
+| Config file API | alpha |
+| Self-hosting | alpha |
+| kubeadm alpha subcommands | alpha |
+| CoreDNS | GA |
+| DynamicKubeletConfig | alpha |
+
+
+kubeadm's overall feature state is **Beta** and will soon be graduated to
+**General Availability (GA)** during 2018. Some sub-features, like self-hosting
+or the configuration file API are still under active development. The
+implementation of creating the cluster may change slightly as the tool evolves,
+but the overall implementation should be pretty stable. Any commands under
+`kubeadm alpha` are by definition, supported on an alpha level.
+
+
+### Support timeframes
+
+Kubernetes releases are generally supported for nine months, and during that
+period a patch release may be issued from the release branch if a severe bug or
+security issue is found. Here are the latest Kubernetes releases and the support
+timeframe; which also applies to `kubeadm`.
+
+| Kubernetes version | Release month | End-of-life-month |
+|--------------------|----------------|-------------------|
+| v1.6.x | March 2017 | December 2017 |
+| v1.7.x | June 2017 | March 2018 |
+| v1.8.x | September 2017 | June 2018 |
+| v1.9.x | December 2017 | September 2018 |
+| v1.10.x | March 2018 | December 2018 |
+| v1.11.x | June 2018 | March 2019 |
+
+{{% /capture %}}
+
+{{% capture prerequisites %}}
+
+- One or more machines running a deb/rpm-compatible OS, for example Ubuntu or CentOS
+- 2 GB or more of RAM per machine. Any less leaves little room for your
+ apps.
+- 2 CPUs or more on the master
+- Full network connectivity among all machines in the cluster. A public or
+ private network is fine.
+
+{{% /capture %}}
+
+{{% capture steps %}}
+
+## Objectives
+
+* Install a single master Kubernetes cluster or [high availability cluster](https://kubernetes.io/docs/setup/independent/high-availability/)
+* Install a Pod network on the cluster so that your Pods can
+ talk to each other
+
+## Instructions
+
+### Installing kubeadm on your hosts
+
+See ["Installing kubeadm"](/docs/setup/independent/install-kubeadm/).
+
+{{< note >}}
+**Note:** If you have already installed kubeadm, run `apt-get update &&
+apt-get upgrade` or `yum update` to get the latest version of kubeadm.
+
+When you upgrade, the kubelet restarts every few seconds as it waits in a crashloop for
+kubeadm to tell it what to do. This crashloop is expected and normal.
+After you initialize your master, the kubelet runs normally.
+{{< /note >}}
+
+### Initializing your master
+
+The master is the machine where the control plane components run, including
+etcd (the cluster database) and the API server (which the kubectl CLI
+communicates with).
+
+1. Choose a pod network add-on, and verify whether it requires any arguments to
+be passed to kubeadm initialization. Depending on which
+third-party provider you choose, you might need to set the `--pod-network-cidr` to
+a provider-specific value. See [Installing a pod network add-on](#pod-network).
+1. (Optional) Unless otherwise specified, kubeadm uses the network interface associated
+with the default gateway to advertise the master's IP. To use a different
+network interface, specify the `--apiserver-advertise-address=Objectives
+-
+
- Learn what a Kubernetes cluster is. +
- Learn what Minikube is. +
- Start a Kubernetes cluster using an online terminal. +
Kubernetes Clusters
++ Kubernetes coordinates a highly available cluster of computers that are connected to work as a + single unit. The abstractions in Kubernetes allow you to deploy containerized applications + to a cluster without tying them specifically to individual machines. To make use of this new model + of deployment, applications need to be packaged in a way that decouples them from individual hosts: + they need to be containerized. Containerized applications are more flexible and available than in + past deployment models, where applications were installed directly onto specific machines as + packages deeply integrated into the host. Kubernetes automates the distribution and scheduling of + application containers across a cluster in a more efficient way. Kubernetes is an open-source platform and is + production-ready. +
+A Kubernetes cluster consists of two types of resources: +
-
+
- The Master coordinates the cluster +
- Nodes are the workers that run applications +
Summary:
+-
+
- Kubernetes cluster +
- Minikube +
+ Kubernetes is a production-grade, open-source platform that orchestrates the placement + (scheduling) and execution of application containers within and across computer clusters. +
++ +
Cluster Diagram
+
+ +
The Master is responsible for managing the cluster. The master coordinates all activities in + your cluster, such as scheduling applications, maintaining applications' desired state, scaling + applications, and rolling out new updates.
+A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster. + Each node has a Kubelet, which is an agent for managing the node and communicating with the + Kubernetes master. The node should also have tools for handling container operations, such as Docker or rkt. A + Kubernetes cluster that handles production traffic should have a minimum of three nodes.
+ +Masters manage the cluster and the nodes are used to host the running applications.
+When you deploy applications on Kubernetes, you tell the master to start the application containers. + The master schedules the containers to run on the cluster's nodes. The nodes communicate with the + master using the Kubernetes API, which the master exposes. End users can also use the + Kubernetes API directly to interact with the cluster.
+ +A Kubernetes cluster can be deployed on either physical or virtual machines. To get started with + Kubernetes development, you can use Minikube. + Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and + deploys a simple cluster containing only one node. Minikube is available for Linux, macOS, and + Windows systems. The Minikube CLI provides basic bootstrapping operations for working with your + cluster, including start, stop, status, and delete. For this tutorial, however, you'll use a + provided online terminal with Minikube pre-installed.
+ +Now that you know what Kubernetes is, let's go to the online tutorial and start our first + cluster!
+ ++ +
+ 
+ 
+ 
+ 
+ 
+