Kubernetes has a feature of deploying multiple replicas of a pod and managing them from workstation. Each of these sets of replicas of a pod are called replicasets. Replicasets can be created, deleted, updated in a single time. These are shown as deployments in the kubectl cli Creating deployment: kubectl create deployment rajesh –image=scmgalaxy/nginx-devopsschoolv1 –replicas=3 -n=sumit Getting list of replicas deployed in namespace: kubectl get deploy -n=sumit Scale deployment: kubectl scale –replicas=3 deploy/rajesh -n=sumit O/p:deployment.apps/rajesh scaled[centos@ip-172-31-22-14 ~]$ kubectl get deploy

Kubernetes is a container orchestrator tool. It solves the problem of manually launching, monitoring and maintaining container applications. A Kubernetes cluster is a set of Nodes and a control plane (aka master) Master controls all the nodes, it does so by using following components: a) API server: All incoming and outgoing communication with the cluster is done through API server. It communicates using JSON files and communication can be established through a set of REST API b) Cluster Store: It

Runs multiple containers from a single file and allows common access a) docker-compose run: run file b) docker-compose create: create services c) docker-compose stop: stop services d) docker-compose up: create and run e) docker-compose down: stop f) docker-compose rm g) docker-compose ps h) docker-compose push i) docker-compose pull

Containerization is motivated by need of dynamic scaling and resource allocation. Docker allows us to work in different environments and share with different involved stakeholders with ease.