Kubernetes Installation( kubeadm =Non Production)

-


Kubernetes installation(Kubeadm for non production)

AWS (t2.micro) pricing details:

low-cost-burstable-ec2-instances

 https://aws.amazon.com/blogs/aws/low-cost-burstable-ec2-instances/
  1. Ensure you have more than one linux with following flavors
  2. Ensure following ports are open
  3. Install docker runtime on master & all nodes by following here
  4. Install kubeadm components on master & all nodes by following here
5. Create the kubernetes cluster
  • Login into master, become a root user (sudo -i)
  • execute kubeadm init
  • root@ip-172-31-7-224:~# kubeadm init
    [init] Using Kubernetes version: v1.13.3
    [preflight] Running pre-flight checks
    [preflight] Pulling images required for setting up a Kubernetes cluster
    [preflight] This might take a minute or two, depending on the speed of your internet connection
  •  
  • To start using your cluster, you need to run the following as a regular user:

      mkdir -p $HOME/.kube
      sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
      sudo chown $(id -u):$(id -g) $HOME/.kube/config

    You should now deploy a pod network to the cluster.
    Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
      https://kubernetes.io/docs/concepts/cluster-administration/addons/

    You can now join any number of machines by running the following on each node
    as root:

      kubeadm join 172.31.7.224:6443 --token 1fz0wn.t0um5nfzqkpmkbc2 --discovery-token-ca-cert-hash sha256:cca66babbd28dd63d3cabc4312d85266db0b061dd6c877e52cfb206a6a435a6f


     
  • make the note of kubeadm join command
  • now become the non root user (exit) and create kubeconfig
ubuntu@ip-172-31-7-224:~$ mkdir -p $HOME/.kube
ubuntu@ip-172-31-7-224:~$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
ubuntu@ip-172-31-7-224:~$ sudo chown $(id -u):$(id -g) $HOME/.kube/config

  • install pod network on master
ubuntu@ip-172-31-7-224:~$ kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"
serviceaccount/weave-net created
clusterrole.rbac.authorization.k8s.io/weave-net created
clusterrolebinding.rbac.authorization.k8s.io/weave-net created
role.rbac.authorization.k8s.io/weave-net created
rolebinding.rbac.authorization.k8s.io/weave-net created
daemonset.extensions/weave-net created

=> Then check the nodes status before n/w join and after:(Status will become ready after pods network)

Before:

ubuntu@ip-172-31-7-224:~$ kubectl get nodes
NAME              STATUS     ROLES    AGE   VERSION
ip-172-31-4-210   NotReady   <none>   46s   v1.13.3
ip-172-31-7-224   NotReady   master   21m   v1.13.3

After:

 ubuntu@ip-172-31-7-224:~$ kubectl get nodes
NAME              STATUS   ROLES    AGE    VERSION
ip-172-31-4-210   Ready    <none>   100s   v1.13.3
ip-172-31-7-224   Ready    master   22m    v1.13.3

  • log in to the nodes become root user & execute kubeadm join command which you have copied
 root@ip-172-31-4-210:~# kubeadm join 172.31.7.224:6443 --token 1fz0wn.t0um5nfzqkpmkbc2 --discovery-token-ca-cert-hash sha256:cca66babbd28dd63d3cabc4312d85266db0b061dd6c877e52cfb206a6a435a6f
[preflight] Running pre-flight checks
[discovery] Trying to connect to API Server "172.31.7.224:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://172.31.7.224:6443"
[discovery] Requesting info from "https://172.31.7.224:6443" again to validate TLS against the pinned public key
[discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server "172.31.7.224:6443"
[discovery] Successfully established connection with API Server "172.31.7.224:6443"
[join] Reading configuration from the cluster...
[join] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.13" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...
[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "ip-172-31-4-210" as an annotation

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the master to see this node join the cluster.

root@ip-172-31-4-210:~#


Comments

Post a Comment

Popular posts from this blog

How to run Jenkins on Docker container | How to create Jenkins Volumes on Docker

-
1. How to start Jenkins on Docker Container  2. Start and Stop Jenkins Container  3. How to set Jenkins home on Docker Volume and Host Machine How to remove died container: ubuntu@ip-172-31-39-216:~$ docker ps -a CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                       PORTS               NAMES efdab4e0a237        jenkins             "/bin/tini -- /usr/l…"   5 minutes ago  ...
Read more

POWERSHELL

-
 get-help about_operator    get-help where-object    get-service | where-object {$_.status -eq "running"}    get-service | where-object {$_.name -eq "winrm"}   get-eventlog -logname application -Newest 50 | where-object {$_.EntryType -eq "error"} get-hotfix | where-object {$_.Description -eq "update"} Not equal:  get-hotfix | where-object {$_.Description -ne "update"}    get-help about_comparison_operators   Greater than: get-process | where-object {$_.Handles -gt "1500"} Less than: get-process | where-object {$_.Handles -lt "100"} greater than date:  get-hotfix | where-object {$_.InstalledOn -gt "01/01/2020"}    get-hotfix | where-object {$_.InstalledOn -gt "01/01/2019"}    get-hotfix | where-object {$_.InstalledOn -gt "01-01-2019"}    Like:    get-service | where-object {$_.displayname -like "Application*"}    get-process | where-object {$_.ProcessName -like "*host*...
Read more

Building game of life container

-
Building game of life container -----------------------------------------     Manual Steps:         install java8 (openjdk8)         install tomcat 7         tomcat directory/webapps/         (re)start tocmat         works on port 8080 Game-of-life war file has been uploaded into S3 bucket: ======================================== Game-of-life   How to pull tomcat from git:(Now here we r downloading tomcat8) -------------------------------------- ubuntu@ip-172-31-2-125:~$ docker image pull tomcat:8 8: Pulling from library/tomcat ab1fc7e4bf91: Pull complete 35fba333ff52: Pull complete f0cb1fa13079: Pull complete 3d79c18d1bc0: Pull complete ff1d0ae4641b: Pull complete 8883e662573f: Pull complete adab760d76bd: Pull complete 86323b680e93: Pull complete 14a2c1cdce1c: Pull c...
Read more