{"id":40547,"date":"2016-10-24T12:56:09","date_gmt":"2016-10-24T07:26:09","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=40547"},"modified":"2016-10-24T14:27:09","modified_gmt":"2016-10-24T08:57:09","slug":"working-with-kubernetes-deployment-pods-and-service-part1","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/working-with-kubernetes-deployment-pods-and-service-part1\/","title":{"rendered":"Working with Kubernetes deployment, pods and service Part1"},"content":{"rendered":"

In my previous blog, Getting Started with Kubernetes<\/a>,\u00a0I have explained the basics of kubernetes. In this blog, I will be explaining how to create deployment, pods, and service.<\/p>\n

Deployment and pods:<\/strong> Below command will create a deployment controller named a “my-nginx”, a pod with a single\u00a0 container of an image nginx (base image of nginx in docker hub) which listens on port 80. Replicas will define how many pods do\u00a0 you want to run, in this case, it is “1”, so deployment controller will ensure that there should always be one pod running.<\/p>\n

[shell]
\nkubectl run my-nginx –image=nginx –replicas=1 –port=80
\n[\/shell]<\/p>\n

Get the status of the deployment and pod with below commands:<\/p>\n

[shell]
\nkubectl get deployment -o wide
\n[\/shell]<\/p>\n

\"deployment\"
\n<\/code><\/p>\n

[shell]
\nkubectl get pods -o wide
\n[\/shell]<\/p>\n

\"pods\"
\n<\/code><\/p>\n

Service<\/strong>: Below command will create a service named “my-nginx” with type Loadbalancer, it will create ELB an endpoint. This service listens on the port 80 and redirects it to the target port 80 (the port on which containers listens).<\/p>\n

[shell]
\nkubectl expose deployment my-nginx –port=80 –type=LoadBalancer
\n[\/shell]<\/p>\n

\"svc\"<\/p>\n

Get the status of the service with the below command:<\/p>\n

[shell]
\nkubectl get service -o wide
\n[\/shell]<\/p>\n

\"svc1\"<\/p>\n

Curl the ELB endpoint and you should see the Welcome Nginx Page<\/strong> response back.<\/p>\n

Deployments, pods, and services can also be created using yaml\/json file. Please find below a sample yaml file nginx.yaml:<\/p>\n

[shell]<\/p>\n

apiVersion: extensions\/v1beta1
\nkind: Deployment
\nmetadata:
\nname: my-nginx
\nspec:
\nreplicas: 1
\ntemplate:
\nmetadata:
\nlabels:
\nrun: my-nginx
\nspec:
\ncontainers:
\n– name: my-nginx
\nimage: nginx
\nports:
\n– containerPort: 80
\n—
\napiVersion: v1
\nkind: Service
\nmetadata:
\nname: my-nginx
\nspec:
\nports:
\n– name: "www"
\nport: 80
\ntargetPort: 80
\nselector:
\nrun: my-nginx
\ntype: LoadBalancer<\/p>\n

[\/shell]<\/p>\n

Run the below command which uses the above yaml and creates deployment controller, a pod and service.<\/p>\n

[shell]
\nkubectl apply -f nginx.yaml
\n[\/shell]<\/p>\n

Assign pod to a specific node:<\/strong>\u00a0Suppose there has been an application which requires to run on the same machine i.e on the same IP. Steps to achieve the same:<\/p>\n