K8s Help

Introduction to Kubernetes Activities: Objectives: In this lab, you will: Use the kubectl CLI Create a Kubernetes Pod Create a Kubernetes Deployment Create a ReplicaSet that maintains a set number of replicas Witness Kubernetes load balancing in action 1. Verify that kubectl CLI is installed: theia@theiadocker-mohiindia:/home/project$ kubectl version Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.14+IKS", GitCommit:"35f1768b1292e15e3e5ca2e31658ecf675c4d5a6", GitTreeState:"clean", BuildDate:"2020-11-12T18:37:40Z", GoVersion:"go1.13.15", Compiler:"gc", Platfor

Container runtime: Remember, Kubernetes is a container orchestration tool. Hence it requires some container runtime software for running the containers. Kubernetes supports several container runtimes: Docker, containerd, CRI-O, and any implementation of the Kubernetes CRI (Container Runtime Interface). Kubernetes Architecture vs Kubernetes Cluster: When you deploy Kubernetes, you get a cluster. Yes We can also say it as Kubernetes Architecture since it contains entire block of Kubernetes Architecture. A Kubernetes cluster consists of a set of worker machines, also called nodes, that run containerized applications. Every cluster has at least one worker node. The worker node(s) host the Pods that are the components of the application workload. The control plane manages the worker nodes and the Pods in the cluster.  In production environments, the control plane usually runs across multiple computers and a cluster usually runs multiple nodes, providing fault-tolerance and high availability