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 -n=sumit
NAME READY UP-TO-DATE AVAILABLE AGE
rajesh 3/3 3 3 4m43s

Delete deployment:

kubectl delete deploy rajesh -n=sumit
deployment.apps “rajesh” deleted

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 maintains all information about cluster in etcd form.

It maintains record of health and actions of all nodes.

c) Controller Manager:

It is a script that is always running to monitor all activities in a cluster.

d) Kube-scheduler:

It watches API server for all incoming tasks and schedule nodes based on affinity, constraint and resource requirement.

Each node contains

a) Kubelet:

It is the main Kubernetes agent, as long as it is running, the node can be said to be a part of the cluster.

It registers itself with the master.

It instantiates a pod.

— Pod is a logical entity to group containers.

b) Container Engine:

It pulls images, start & stops containers. It runs the containers

c) Kube proxy

It assigns IP addresses to pods, this allows access to load balancer.

Typical execution of launching a container:

1. Request goes to API server

2. API server checks availability in etcd as sent by control manager

3. API server asks scheduler to communicate with node.

4. Scheduler asks kubelet to instantiate pod

5. Contaainer Engine launches containers and Kube proxy updates IP table

6. IP can be used to access services

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