{"id":39950,"date":"2016-08-31T23:57:34","date_gmt":"2016-08-31T18:27:34","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=39950"},"modified":"2016-09-01T11:07:04","modified_gmt":"2016-09-01T05:37:04","slug":"understanding-kubernetes-architecture-and-setting-up-a-cluster-on-ubuntu","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/understanding-kubernetes-architecture-and-setting-up-a-cluster-on-ubuntu\/","title":{"rendered":"Understanding Kubernetes Architecture and Setting up a Cluster on Ubuntu"},"content":{"rendered":"

As we discussed previously “what is Kubernetes” and “what are the benefits of this orchestration tool”.\u00a0So, if you are wondering\u00a0what Kubernetes\u00a0is, for a better understanding, see getting started with kubernetes.<\/a> Now, in this blog we are here to discuss about running Kubernetes cluster\u00a0on bare-metal.<\/p>\n

\"joining-forces\"<\/p>\n

In order to have better understanding of the architecture we decided to deploy Kubernetes<\/a> on bare-metal. Before setting up Kubernetes on bare-metal, we will discuss the architecture of Kubernetes. In the previous blog, we have discussed the basic term that what is master node,pods, kubectl, etc. and some generally used commands, so let’s have a deep dive on the architecture.
\n <\/p>\n

Kubernetes Architecture<\/span><\/h1>\n

\"kube7-arch\"<\/p>\n

 <\/p>\n

Master Node Architecture<\/span><\/h2>\n

Etcd<\/strong>: It is an open source key-value store developed by CoreOs team. Kubernetes uses ‘Etcd’ to store the configuration data accessed by all nodes (minions and master) in the cluster.<\/p>\n

Kube-ApiServer:<\/strong> \u00a0The Kubernetes api-server generally validates the configuration data store in ‘Etcd’ and the details of the deployed container that are in agreement. It also provides a RESTful interface to make communication easy.<\/p>\n

Kube-Schedule Server<\/strong>: It is responsible for assigning task to minions in the cluster.<\/p>\n

Kube-Controller-Manager:<\/strong> It is generally responsible for handling the cluster level function such as replication controller. Whenever the desired state of the cluster changes it is written to Etcd and then the controller manager tries to bring up the cluster in the desired state.<\/p>\n

Minion Node Architecture<\/span><\/h2>\n

Docker:<\/strong> One of \u00a0the basic requirement of nodes is Docker. Docker is responsible for pulling down and running container from Docker images. Read here for more information on docker<\/a>\u00a0.<\/p>\n

Kube-Proxy:<\/strong> Every node in the cluster runs a simple network proxy. Using proxy node in cluster routes request to the correct container in a node.<\/p>\n

Kubelet<\/strong>: It is an agent process that runs on each node. It is responsible for managing pods and their containers. It deal with pods specifications which are defined in YAML or JSON format. Kubelet takes the pod specifications and checks whether the pods are running healthy or not.<\/p>\n

Flannel<\/strong>: It is an overlay network that works on assigning \u00a0a range of subnet address. It is used to assign IPs to each pods running in the cluster and to make the \u00a0pod-to-pod \u00a0and pod-to-services communications.
\n <\/p>\n

Setup Kubernetes on Ubuntu (Bare-metal)\u00a0<\/span><\/h1>\n

Prerequisites for each server:<\/b><\/span><\/h3>\n
    \n
  • Linux Bridge utils Package [To install : sudo apt-get install bridge-utils ]<\/li>\n
  • Docker<\/span><\/li>\n
  • ssh-agent configured\u00a0properly<\/span><\/strong><\/li>\n
  • All server have ssh-logged in using key authentication<\/li>\n
  • All nodes private-key identity must be added in master node for SSH communication.<\/li>\n<\/ul>\n

    Steps:<\/span><\/h3>\n
      \n
    1. git clone –depth 1 <\/span>https:\/\/github.com\/kubernetes\/kubernetes.git<\/span><\/li>\n
    2. Configure the cluster information in kubernetes\/cluster\/ubuntu\/conf-default.sh file:<\/span><\/strong><\/strong><\/strong>\n

      [js]export nodes="root@ip root@ip root@ip"
      \nexport role="a i i"
      \nexport NUM_NODES=${NUM_NODES:-2}
      \nexport SERVICE_CLUSTER_IP_RANGE=192.168.3.0\/24
      \nexport FLANNEL_NET=172.16.0.0\/16[\/js]<\/p>\n

      Change these variables ,the variable “node” defines all the cluster nodes, “roles” defines what role should assign to each node and “num_nodes” define the number of minions.
      \nNote:<\/i><\/b>
      \nRole \u201ca\u201d for master and \u201ci\u201d for node (minion)<\/span><\/i>
      \nFlannel_net ip should not be the same as cluster CIDR address.<\/span><\/i><\/strong><\/strong><\/li>\n

    3. After all the variables are configured\u00a0correctly, run config-default.sh:\n

      [js] cd\u00a0kubernetes\/cluster\/ubuntu
      \n\u00a0.\/config-default.sh[\/js]<\/p>\n

      Now, all variables are now set for\u00a0that particular session.<\/li>\n

    4. The following command will bring online the whole cluster:\n

      [js]cd\u00a0kubernetes\/cluster\/
      \nKUBERNETES_PROVIDER=ubuntu .\/kube-up.sh[\/js]<\/p>\n

      The script automatically copies all config and binaries files using scp and starts Kubernetes services on each node.<\/li>\n

    5. Now, that the cluster has been setup, we can check by running kubectl on master node. Firstly, export all binaries into bashrc:\n

      [js]export PATH=$PATH:\/homedirectory\/kubernetes\/cluster\/ubuntu\/binaries
      \nsource .bashrc
      \nkubectl get nodes[\/js]<\/p>\n

      \"nodes\"<\/li>\n

    6. Now, Deploy Addons like DNS and UI to manage Kubernetes through UI:\n

      [js]cd\u00a0kubernetes\/cluster\/ubuntu
      \nKUBERNETES_PROVIDER=ubuntu .\/deployAddons.sh[\/js]<\/p>\n<\/li>\n

    7. Access UI:<\/strong> http:\/\/master_node_ip:8080\/UI
      \n\"ui\"
      \n<\/em><\/em><\/li>\n<\/ol>\n

      I hope this will help in understanding the architecture and how to\u00a0setup Kubernetes on Ubuntu. In my next blog, we will setup auto-scaling in pods using external load-balancer.<\/p>\n","protected":false},"excerpt":{"rendered":"

      As we discussed previously “what is Kubernetes” and “what are the benefits of this orchestration tool”.\u00a0So, if you are wondering\u00a0what Kubernetes\u00a0is, for a better understanding, see getting started with kubernetes. Now, in this blog we are here to discuss about running Kubernetes cluster\u00a0on bare-metal. In order to have better understanding of the architecture we decided […]<\/p>\n","protected":false},"author":917,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"link","meta":{"iawp_total_views":11},"categories":[2348,1],"tags":[248,2366,1892,1883,3965,3977,3979,3978,3970],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/39950"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/917"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=39950"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/39950\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=39950"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=39950"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=39950"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}