{"id":2409,"date":"2022-07-26T06:25:46","date_gmt":"2022-07-26T06:25:46","guid":{"rendered":"https:\/\/www.checkmateq.com\/blog\/?p=2409"},"modified":"2023-08-06T14:29:49","modified_gmt":"2023-08-06T14:29:49","slug":"deploying-kubernetes-cluster","status":"publish","type":"post","link":"https:\/\/www.checkmateq.com\/blog\/deploying-kubernetes-cluster","title":{"rendered":"How to Deploy Containers on a Kubernetes Cluster?"},"content":{"rendered":"

What is a pod?<\/h3>\n

A pod is smallest unit of deployment in Kubernetes<\/a>,\u00a0 the containers you deploy on Kubernetes are wrapped in pods ,each pod may have more than one container , so when you want to run an application in Kubernetes you will write a yaml file typically called as a manifest <\/strong> file<\/strong>\u00a0and deploy your application on the Kubernetes cluster using kubectl<\/strong> commands which will deploy your containerized application wrapped in pod(called as a deployment<\/strong>) and you can create multiple replicas of this pod by just mentioning the count in the deployment file .<\/p>\n

A D<\/strong>eployment<\/strong> is responsible for keeping a set of pods running, pods are ephemeral by nature, even an if a pod fails Kubernetes can automatically create a new replica of that pod to continue operations.<\/span><\/span><\/p>\n

\n
\n
\n
\n
\n
\u00a0After creating a deployment to access it you have to create\u00a0a Service, <\/b>service is responsible for enabling network access <\/span><\/span>to a set of pods, there are four types of Kubernetes services Cluster IP, NodePort, Load Balancer, External Name<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
<\/div>\n
\n

Cluster IP<\/b> is most common service type used, Kubernetes will assign a cluster-internal IP address to Cluster IP service, this makes the service only available within the cluster, you cannot connect to service (pods) from outside the Kubernetes cluster.<\/p>\n

Node Port<\/strong> is an open port on every node of your cluster, Kubernetes transparently routes incoming traffic on the NodePort to your service, this is an extension of Cluster IP service. A Cluster IP Service, to which the NodePort Service routes, is automatically created, you can contact the NodePort Service, from outside the cluster, by requesting <NodeIP>:<NodePort>.<\/p>\n

LoadBalancer<\/strong> service is an extension of NodePort service, NodePort and Cluster IP Services are automatically created when you request for a load balancer to which the external load balancer routes traffic to, it exposes the Service externally using a cloud provider\u2019s (AWS, GCP, Azure) load balancer.<\/p>\n<\/div>\n

In this blog we will create a deployment (deploying nginx webserver) and a service (Node port) for that deployment using yaml configuration files, below is the deployment.yaml file which deploys 2 replicas of\u00a0 ngins web server, and service.yaml file to allow traffic from outside to access the webserver at port 32000 on the node.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Lets understand these configuration files line by line<\/h3>\n
apiVersion: v1\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0      apiVersion: v1\r\nkind: Deployment\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0kind: Service<\/pre>\n
the first two lines is declaring what you want to create, here we are creating deployment\u00a0 and a service , for each component there is a\u00a0 different api version .<\/p>\n
 <\/p>\n
metadata:                                       metadata:\r\n  name: nginx-deployment                          name: nginx-service\r\n<\/pre>\n
Every configuration file in Kubernetes has 2 parts, first part is meta data of components, here the meta data is name of the component itself<\/p>\n
 <\/p>\n
\"\"<\/p>\n
Specification<\/strong><\/p>\n
the second part in configuration file is specification<\/strong> where you basically put every kind of configuration that you want to apply for that component of deployment, and you will give the attributes that are specific to the kind of a component that you are creating service\/deployment.<\/p>\n
 <\/p>\n
\n
\n
\"\"<\/p>\n
as you can see in the specification part of deployment.yaml, it has a block named\u00a0 template<\/strong> and this template also has its own meta data and specification, this part of configuration under template is applied to a pod , a pod should have its own configuration in a deployment configuration file , this will be the blueprint for a pod like which image<\/strong> it should be based on which port<\/strong> it should open what will be name of the container and all other details.<\/p>\n
First let’s create a deployment and a service and then understand the specification part of service configuration file.<\/p>\n
Deploying pods on Kubernetes Cluster<\/strong><\/h3>\n
As we have understand how to write deployment file and a service file and how they are connected using labels and selectors, let’s deploy nginx webserver on the Kubernetes cluster, use below given commands to get the status of your cluster and nodes.<\/p>\n
kubectl cluster-info\r\nkubectl get nodes<\/pre>\n
\"\"<\/p>\n
 <\/p>\n
Copy below syntax on your master node terminal and click enter or create a yaml file (nginx.yaml\/deployment.yaml) copy the highlighted part of below syntax in the yaml file and save it , use “kubectl apply -f\u00a0 \u00a0xxxx.yaml<\/strong>”\u00a0 \u00a0xxxx.yaml should be replaced by your yaml file name .<\/p>\n
cat <<EOF | kubectl apply -f -\r\napiVersion: apps\/v1\r\nkind: Deployment\r\nmetadata:\r\n  name: nginx-deployment\r\nspec:\r\n  replicas: 2 \r\n  template:\r\n    metadata:\r\n      labels:\r\n        app: nginx\r\n    spec:\r\n      containers:\r\n      - name: nginx\r\n        image: nginx:latest\r\n        ports:\r\n        - containerPort: 80<\/strong>      \r\nEOF\r\n<\/pre>\n
And use command “kubectl get pods<\/strong>” to check the status of the deployment\/pods.<\/p>\n
\"\"<\/p>\n
Creating a Service<\/h3>\n
Now let’s create a service of type NodePort, create file named service.yaml<\/strong> (you can use any name for your file need not be “service”) copy below given syntax and save it.<\/p>\n
apiVersion: v1\r\nkind: Service\r\nmetadata:\r\n  name: nginx-service\r\nspec:\r\n  selector: \r\n    app: nginx\r\n  type: NodePort  \r\n  ports:\r\n    - port: 80\r\n      targetPort: 80\r\n      nodePort: 32000\r\n<\/pre>\n
Now use below given command to apply the configuration and\u00a0 create a NodePort\/expose deployed application for external traffic,\u00a0 for the pods you deployed in previous step.<\/p>\n
kubectl apply -f service.yaml<\/pre>\n
replace service.yaml with your file name<\/p>\n
\"\"<\/p>\n
Now go on to the browser and give <IP-address>:32000 (IP address of the worker node on which pods are deployed)<\/p>\n
\"\"<\/h3>\n
How service routes traffic to deployment?<\/h3>\n
In previous step we have created a deployment and a service, and we are able to access our deployment from the browser, but how these both are connected?<\/p>\n
it’s simply done using labels and selectors.<\/p>\n
Labels\u00a0are key<\/b>\/value pairs attached to objects you can label each and every object in Kubernetes<\/p>\n
Selectors are<\/b> nothing but selecting objects using the labels i.e., selecting objects with same label to make a group, you cannot have a selector without a label, so if you want to group a particular set of objects all those set of objects should have the same labels, for example if you want to select a set of pods as a backend to an application all of them should have same label.<\/p>\n<\/div>\n
\"\"<\/p>\n
In deployment.yaml we are labeling our pods with a key\/value pair app:nginx\u00a0<\/strong>and in the service.yaml\u00a0 a selector\u00a0 is being used and the same label is given to it as in the deployment.yaml file ( app:nginx<\/strong>) , so whenever someone access this service it will check the labels and routes the traffic to the pods with the same label.<\/p>\n<\/div>\n
How to declare ports in service configuration file?<\/h3>\n
\n
\"\"<\/p>\n
\"\"<\/p>\n
As show in the above image we are exposing our application(nginx) at\u00a0 port :80\u00a0 by declaring\u00a0 \u00a0– containerPort<\/strong> as 80<\/strong> under ports:\u00a0<\/strong>in deployment.yaml file, and in service.yaml file\u00a0 \u00a0targetPort: 80<\/strong> is the container port number on which we have exposed our application on, and – port: 80 <\/strong> is the external port , as mention initially in this blog we created a service of type NodePort<\/strong> and using port:32000 for this , even if you do not mention any port number ,Kubernetes will choose any random port from node-port IP range( 30,000 t0 32,767)<\/p>\n
 <\/p>\n
Please contact our software engineering team for any Cloud DevOps<\/a> infrastructure management services website<\/a>, LinkedIn<\/a><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
What is a pod? A pod is smallest unit of deployment in Kubernetes,\u00a0 the containers you deploy on Kubernetes are wrapped in pods ,each pod may have more than one container , so when you want to run an application in Kubernetes you will write a yaml file typically called as a manifest file\u00a0and deploy … Continue reading “How to Deploy Containers on a Kubernetes Cluster?”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":2604,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[3,79,2,71,70,69,68,59,11,78,63,23,16,24,80,8],"_links":{"self":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/2409"}],"collection":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/comments?post=2409"}],"version-history":[{"count":46,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/2409\/revisions"}],"predecessor-version":[{"id":4267,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/2409\/revisions\/4267"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media\/2604"}],"wp:attachment":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media?parent=2409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/categories?post=2409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/tags?post=2409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}