Day3- architecture and components of Kubernetes and Pods

Kubernetes Architecture: When you deploy Kubernetes, we get a cluster. Every cluster has at least one Master node and Worker node Control Plane Components: kube-apiserver                 -> POD -> Container -> Docker image –> Google Registry etcd                                  -> POD -> Container -> Docker image –> Google Registry kube-scheduler                 -> POD -> Container -> Docker image –> Google Registry kube-controller-manager -> POD -> Container -> Docker image –> Google Registry The control plane’s components make global decisions

Read more

Docker Image:

is a layer of filesystem. like rootfs +userfs+ apps+ apps all layers are read only. layer wise we can create container. when we pull the image then in var/lib/docker folder images is downloaded when we create the container then in var/lib/docker folder merged layer is created with RW file system conflict in layers then top layer is given priority. when we stop the container then merged layer is removed image is assigned to a user then a container is created

Read more

docker update & docker wait commands with example

update : Update configuration of one or more containers [root@ip-172-31-14-110 centos]# docker update –cpu-shares 512 d28b65c987d8 ecstatic_shawd28b65c987d8ecstatic_shaw[root@ip-172-31-14-110 centos]# docker diff d28b65c987d8C /tmpA /tmp/jetty-0_0_0_0-8080-war-_-any-8581425030792705993A /tmp/winstone6787664488571520537.jarA /tmp/hsperfdata_jenkinsA /tmp/hsperfdata_jenkins/7 wait Block until one or more containers stop, then print their exit codes in 1st terminal [root@ip-172-31-14-110 centos]# docker wait 465d9c332e130[root@ip-172-31-14-110 centos]# [root@ip-172-31-14-110 centos] in 2nd terminal: [root@ip-172-31-14-110 centos]# docker stop 465d9c332e13465d9c332e13

Read more