Replicaset: A ReplicaSet is one of the Kubernetes controllers that makes sure we have a specified number of pod replicas running. A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time. As such, it is often used to guarantee the availability of a specified number of identical Pods.  You can define Deployments to create new ReplicaSets, or to remove existing Deployments and adopt all their resources with new Deployments. Example: creating replicaset: 2.scaling replicaset:

kubernetes replica sets instantiate the desired number of pods. kubectl create deployment name –image=imagename –replicas=noofreplicas -n=namespace kubectl apply -f filename kubectl get rs

[centos@ip-172-31-22-14 ~]$ kubectl scale –replicas=1 deploy/namrata -n=namtestdeployment.apps/namrata scaled[centos@ip-172-31-22-14 ~]$ kubectl scale –replicas=10 deploy/namrata -n=namtestdeployment.apps/namrata scaled[centos@ip-172-31-22-14 ~]$ kubectl get deploy -n=namrataNo resources found in namrata namespace.[centos@ip-172-31-22-14 ~]$ kubectl get deploy -n=namtestNAME READY UP-TO-DATE AVAILABLE AGEnamrata 10/10 10 10 8m54snamrata1 3/3 3 3 6m40s[centos@ip-172-31-22-14 ~]$ kubectl get pods -n=namtestNAME READY STATUS RESTARTS AGEnamrata 1/1 Running 0 116mnamrata-dfb987696-798c7 1/1 Running 0 2m5snamrata-dfb987696-8b6kz 1/1 Running 0 2m5snamrata-dfb987696-bzxsx 1/1 Running 0 2m5snamrata-dfb987696-d9qsq 1/1 Running 0 2m5snamrata-dfb987696-gdmwn 1/1 Running 0 2m5snamrata-dfb987696-gwgfr 1/1 Running 0 2m5snamrata-dfb987696-lxf69 1/1

A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time. As such, it is often used to guarantee the availability of a specified number of identical Pods There are many ways we can use replicasets such that always required number of pods running is guarangteed. While creating the deployment kubectl create deployment pradeepa–image=scmgalaxy/nginx-devopsschoolv1 –replicas=3 -n=pradeepa 2. While the deployment is running kubectl edit deploy pradeepa-n=pradeepa Replicas: 2 desired | 2 updated | 2

ReplicaSet: A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time. As such, it is often used to guarantee the availability of a specified number of identical Pods. There are many ways we can use replicasets such that always required number of pods running is guarangteed. While creating the deployment kubectl create deployment ramesh –image=scmgalaxy/nginx-devopsschoolv1 –replicas=3 -n=ramesh 2. While the deployment is running kubectl edit deploy ramesh -n=ramesh Replicas: 2 desired | 2

ReplicaSets Definition – It is a Kubernetes object that maintains the number of pods (i.e. replicas of a given pod) and checks if the current number of pods are matching the desired number specified for the figure given in replicasets. Advantage – 1.Its powerful – since at any point of time you can manage the scale of your app by this single configuration in the YAML. 2. Also – even if a pod gets killed/terminated – the ReplicaSet will always

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

1. What are Migrations and Migration table in Laravel? Laravel Migration is an essential feature in Laravel that allows you to “easily create a table in your database“. It allows you to create and modify the application’s database schema. You can modify the table by adding a new column or deleting an existing column. Migrations are like version control for your database. Migration tables are files that are created by an administrator. 2. Why do we use migrations? Another common reason for migration

Kubernetes cluster as two parts: the control plane and the compute machines, or nodes.Each node runs pods, which are made up of containersThe control plane is responsible for maintaining the desired state of the cluster, such as which applications are running and which container images they use. Compute machines actually run the applications and workloads.Kubernetes runs on top of an operating system and interacts with pods of containers running on the nodes. desired state of a Kubernetes cluster defines which

Kubernetes is an open-source platform for automated deployment, scaling, and management of containers and containerized applications. Features of Kubernetes:  Automating many processes of applications and services deployment that before were carried out manually  Kubernetes checks constantly the health of nodes and containers It takes care of scaling and failover for the application Kubernetes is able to load balance and distribute the network traffic so that the deployment is stable. Scale resources and applications in real time Orchestrate containers on multiple

kubernetes consists of master/controlplane and worker Nodes. Control Plane Components : . apiserver The API server is a component of the Kubernetes controlplane that exposes the Kubernetes API. The API server is the front end for the Kubernetes control plane. . etcd Consistent and highly-available key value store used as Kubernetes’ backing store for all cluster data. . kube-scheduler schedules pods for a node .controller-manager It checks continuously whether the pods are running or not. Node Components : . kubelet An agent

Kubernetes works with Kubernetes cluster and a control plane. Kubernetes cluster is a combination of nodes with atleast one Master node and a worked node. Control plane components: Api Server: Provides Api to connect to worker nodes Cluster store (etcd): Persistant storage of cluster state and it stores data in key and value pair in etcd db. Controller Manager: It is a controller of controllers. Kube schedular: It will just schedule the pods and assigns the work Node components: Kubelet

What is Kubernetes and its feature? Kubernates is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Feature: Some of the features which Kubernates offers are:· Pod -collection contains· Replication Controller· Storage Management· Resource Monitoring· Health Checking· Horizontal Auto Scaling· Service Discovery· Networking· Services· ConfigMap and Secret· Rolling Deployment and Rollback· Logging How kubernetes works? Explain each components with Short Summary Kubernetes

Kubernetes is a container management system developed on the Google platform. Kubernetes helps to manage containerized applications in various types of physical, virtual, and cloud environments. Google Kubernetes is a highly flexible container tool to consistently deliver complex applications running on clusters of hundreds to thousands of individual servers.Kubernetes helps you to control the resource allocation and traffic managementFeatures :Automated SchedulingAuto-healing capabilitiesresource utilizationHorizontal Scaling & Load BalancingResource monitoring

Kubernetes is a open source tool that groups the containers into logical units to make up as application, which helps to manage the containers to achieve resource isolation, resource utilization, loosely/tightly coupled distributed workloads, distributions portability, CI & CD, high availability, scalability in lesser than few seconds Features Self-healing: without user intervention restarts the pods which is failed Networking: Pods can communicate within the node or outside the node also, each node/pod will have ip address Load balancing: Applications can be auto

Kubernetes Essential Components Kubernetes initially developed by Google and now an Open source project in CNCF. It has following major components Kubernetes Master Kubernetes Worker aka Minion aka Node Workstation usage – Kubectl Kubernetes Master It is the control plane of the cluster – it receives request for the desired state of the cluster and also the current state from the workers’ agent and is responsible to schedule workloads aka containers accordingly. Normally kept as replica of 3 to manage

Kubernetes has manily two components Master and Node/Minion. The master node controls the state of the cluster; for example, which applications are running and their corresponding container images. Master Components: API Server ETCD – for storing data in Key Velue Controller Scheduler Kubectl Kubelet Docker The Utlitites/Softwares (5,6,7) can be installed via kubeadmin init Node: Kubelet Docker Kubectl Kube proxy The utilites (1,2,3) can be installed via kubeadmin join Workstation Kubectl -> Package

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

Kubernetes is a open source tool that groups the containers into logical units to make up as application, which helps to manage the containers to achieve resource isolation, resource utilization, loosely/tightly coupled distributed workloads, distributions portability, CI & CD, high availability, scalability in lesser than few seconds Features Self-healing: without user intervention restarts the pods which is failed Networking: Pods can communicate within the node or outside the node also, each node/pod will have ip address Load balancing: Applications can

Kubernetes is an open-source platform for automated deployment, scaling, and management of containers and containerized applications. Features of Kubernetes:  Automating many processes of applications and services deployment that before were carried out manually  Kubernetes checks constantly the health of nodes and containers It takes care of scaling and failover for the application Kubernetes is able to load balance and distribute the network traffic so that the deployment is stable. Scale resources and applications in real time Orchestrate containers on multiple