0) Verify the status of kubernetes cluster kubectl get nodes # kubectl get pods --all-namespaces # kubectl cluster-info # kubectl config get-contexts
1) download the script from Helm's GitHub repository:
$ cd /tmp $ curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > install-helm.sh
2) Make the script executable $ chmod u+x install-helm.sh
3) #Install helm $ ./install-helm.sh
4) Installing Tiller Tiller is a companion to the helm command that runs on your cluster, receiving commands from helm and communicating directly with the Kubernetes API to do the actual work of creating and deleting resources. To give Tiller the permissions it needs to run on the cluster, we are going to make a Kubernetes serviceaccount resource.
#install the parts we need for Kubernetes
$ sudo apt-get install -y kubelet kubectl kubernetes-cni
Kubernetes requires a Pod Network for the pods to communicate. For this guide we will use Flannel although there are several other Pod Networks availabl
#We can now initialize Kubernetes by running the initialization command and passing --pod-network-cidr which is required for Flannel to work correctly
$ sudo kubeadm init --pod-network-cidr=22.214.171.124/24
Once Kubernetes has been initialized we then install the Flannel Pod Network by running.
Let’s deploy the pod network, Pod network is the network through which our cluster nodes will communicate with each other. We will deploy Flannel as our pod network, Flannel will provide the overlay network between cluster nodes.
First we need to set /proc/sys/net/bridge/bridge-nf-call-iptables to 1 to pass bridged IPv4 traffic to iptables` chains which is required by certain CNI networks (in this case Flannel). Do this by issueing
#We can check that the pod is up by running
$ kubectl get pods --all-namespaces
$ sudo kubectl get nodes
Because we are running only a single Kubernetes node we want to be able
to run Pods on the master node. To do this we need to untaint the master
node so it can run regular pods. To do so run
$ kubectl taint nodes --all node-role.kubernetes.io/master-