Once the commands run, Kubernetes will action the. ReplicaSets are not very smart and do not redeploy pods when the container specification has been edited. To create a replica said execute the following command. ReplicaSets guarantee that there will be a specific number of identical Pods running at any given time. kubectl logs -l app=myapp -c myapp --tail 100kubectl get pods <pod-name> -o yaml kubectl get pods my-helloworld-rs-c8rrj -o yaml Step-03: Expose ReplicaSet as a Service ; Expose ReplicaSet with a service (NodePort Service) to access the application externally (from internet) 3 Answers. Deploy Commands: rollout Manage the rollout of a resource scale Set a new size for a deployment, replica set, or. revisionHistoryLimit' 2 $ kubectl get rs NAME DESIRED CURRENT READY AGE nginx-696171888 2 2 2 59s $ kubectl set image. By using the command kubectl delete rs <rs name>, where rs name is the name of your ReplicaSet, you can destroy ReplicaSets. 3. Find the object that "old" rs is controlled by: kubectl describe <rs-name>. Connect and share knowledge within a single location that is structured and easy to search. $ kubectl set image deployment/newsconsumer-deployment. In this case (the example above), we’re. Create replica set. List the available StatefulSets. We manufacture concrete panels to build themed environments, custom. mongodb-2 – Read-only replica. You can use kubectl get pods again to see the unneeded pods being removed. $ kubectl get deploy pet2cattle-o 'jsonpath={. Enter the pod using kubectl exec: kubectl exec -it mongodb-replica-0 -n default -- mongo. Run this command to view: kubectl get pods Output:We can run kubectl get rs to see that the Deployment updated the Pods by creating a new Replica Set and scaling it up to 3 replicas, as well as scaling down the old Replica Set to 0 replicas. After deploying the replica set or replication controller, if you need to edit the file, you can use the command kubectl edit to edit. Deployment creates it in the background and manage it. Maka dari itu, ReplicaSet seringkali digunakan untuk menjamin ketersediaan dari beberapa Pod identik dalam jumlah tertentu. in. kubectl describe deployment awesome-app-deployment. kubectl get pods --all-namespaces. kubectl apply -f creates Replica Sets using a config file: kubectl apply -f replicaset-definition-file. This should create the node api deployment. the old replica sets are not removed they are retained for the versioning. Define container ports with --port. I am not able to find a better description than kubectl describe deploy. Certificate Management with kubeadm; Configuring a cgroup driver; Reconfiguring a. name=my-service metadata. Get details of a replica set: kubectl describe replicaset webapp. Also, take a look here13. To set up pod replication: 1. 0. mourya ~ % kubectl get statefulset NAME READY AGE web 3/3 68sKubectl rolling update updates Pods and ReplicationControllers in a similar fashion. Output: NAME DESIRED CURRENT READY AGE nodeapp-deployment-56865dcdf6 5 5 5 52s. Replica Sets Deployments Other Kinds of Resource Conclusion Kubernetes is not known for being approachable. spec. For example, you define how many replicas ( pods) of your app you want to run in the. Therefore, we have implemented a small handling charge of $1. with the -A option it gives you all your hpa from all namespaces if you want to specify a namespace, you can use -n option. You can use: kubectl get hpa -A -w. After being updated, the Deployment kills all pods at once, and starts new version of pods with the same amount of replicas. Step-02: Create ReplicaSet. Using kubectl, we can apply this definition like: kubectl apply -f orphan. selector: This specifies a label selector to identify the pods managed by this ReplicaSet. $ kubectl delete all --selector=<key>=<value> -n <namespace> or $ kubectl delete all -l <key>=<value> -n. yaml -- OR -- . g. When using ReplicaSets, you get to enforce a minimum number of Pods for your application. Deleting a ReplicaSet. Advantage – . Possible Solution 2: set minAvailable to quorum-size (e. 2 image is utilized. The controller creates two new pod definitions because we have configured replica value as. The same can be achieved with kubectl create -f ( -f is a flag for specifying file. yaml kubectl delete rs new-replica-set kunectl create -f rs. mongodb-replica-set-key}" | base64 --decode Step 3: Restore the MongoDB deployment on the destination cluster You can now restore the persistent volumes and integrate them with a new MongoDB deployment on the destination cluster. Daemon Set; Scaling Commands. Deployments are essentially a nicer way to perform rolling update server side, but there's a little more to it. kubectl apply -f creates Replica Sets using a config file: kubectl apply -f replicaset-definition-file. StatefulSet is the workload API object used to manage stateful applications. 4. kubectl get pods. Declarative way, edit this line in your Yaml file: replicas: 2. The . // demonstrate to change the number of Pod replicas. apps -n <namespace> (or --all-namespaces) – Noam Manos. One exception is the rolling-update command. 1. 168. How a ReplicaSet works? ReplicaSet is a next generation of replicationcontroller both replicaset and replicationcontroller ensure that pods that are. ReplicaSet immediately creates the pod. Stateful SetsThis is a reference where you can get most kubectl codes and their definitions easily acts as a reference. Change the number of replicas of your StatefulSet: kubectl scale statefulsets <stateful-set-name> --replicas=<new-replicas>. Deployments encapsulate replica sets and pods in the Kubernetes’ resource hierarchy and provide a declarative method of updating the state of both. This page contains a list of commonly used kubectl commands and flags. 概述. Now copy your deployment file to a master node and apply it. Delete the ReplicaSet Let's clean up before we move on. Pods run in node and node is the worker in kubernetes. After scaling the ReplicaSet, you can verify the changes by examining its status and the associated pods: 1. If Metrics Server is already running, you’ll see details on the running pods, as in the response below: kube-system metrics-server-v0. extensions/sample-rs scaled でちゃんとpodの数が6個になっているか確認してみる。In this manner, a ReplicaSet can own a non-homogenous set of Pods. 79. kubectl apply -f <name> to recreate the StatefulSet. logs: Prints the stdout and stderr for a container running in a Pod. Edit a replica set: kubectl edit replicaset webapp. So i need to used version in . phase field is. We can also verify the running service: kubectl get svc. Scaling apps to zero to help save resources. kubectl get pods <pod-name> -o yaml kubectl get pods my-helloworld-rs-c8rrj -o yaml Step-03: Expose ReplicaSet as a Service ; Expose ReplicaSet with a service (Load Balancer Service) to access the application externally (from internet) Step 2: Check All the ReplicaSets in Kubernetes. Create ReplicaSet with 3 Replicas. yaml deployment "mywebservice-deployment" create $ kubectl get deployments NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE. Now run the below kubectl get command to verify the list of namespaces on your Kubernetes cluster. Toye Idowu. $ kubectl create -f deploy. Changes to label selectors make existing pods fall out of ReplicaSet's scope, so if you change labels and label selector the pods are no longer "controlled" by ReplicaSet. By manually modifying the replica set that was created for you, you are fighting with the system controller. kubectl get replicasets -w. yaml. kubectl create -f my-replica-set. elastic. yaml. A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. First pods with your new revision will be created, but replicas of your old ReplicaSet will only be scaled down when you have. phase=Pending This kubectl command selects all Pods for which the value of the status. yaml, apply it and when I run 'kubectl get . This procedure allows you to set different settings for the replica set resource, such as overrides for statefulSet configuration. A "rolling deployment" will be performed. Delete the ReplicaSet Let's clean up before we move on. 492suser 0m0. If no pods are returned, you can deploy the latest version of the Metrics Server by running the following command. In Kubernetes 1. 1k 1. And they both say. Add a comment. Certificate Management with kubeadm; Configuring a cgroup driver;. Pro tip! To save time you can use kubectl to generate the YAML file boilerplate by running; kubectl create deployment --image=awesome-app-image awesome-app-deployment --dry-run -o yaml. When to use - DaemonSet and/or ReplicaSet?. Run Command $ sudo kubectl create -f service. Replica-Sets replicate and manage pods, as well. In addition, there is a special kubectl autoscale command for creating a HorizontalPodAutoscaler object. How to create it. The easiest way to scale an existing ReplicaSets on a Kubernetes cluster is to use the Kubectl command-line and quickly scale up or down the number of pods. In a real-life Postgres example, you’d use your init containers to set up database replication from the primary Pod to the replicas. If you list the Pods, you will notice that five Pods are running: $ Kubectl get Pods NAME READY STATUS RESTARTS AGE my-replicaset-89dkw 1/1 Running 0 4m15s You can see that the number of Replica and the running instance of a Pod are the same as the number specified in the manifest file replicas field. Apr 8, 2022 at 21:57. Note: if you run the command too. You should get just 1 deployment. $ kubectl apply -f my-pod. It uses a template that describes what each Pod must contain. 188ssys. Show that it runs in 3 pods mongodb-replicaset-0, mongodb-replicaset-1, mongodb-replicaset-2. Try kubectl get deployment --namespace=kube-system to see if you have a deployment in the kube-system namespace. Even though the new replica set is created. Display information about the ReplicaSet in the current namespace $ kubectl get replicaset. This command can be used to view logs from a single pod, but you can also use it to view logs from multiple simulataneously. Only when I cleaned up all replica sets with kubectl delete $(kubectl -o name get rs), new replica set was created, and then everything worked again. Verwaltung mit kubeadm. The differences in this manifest are: Using kind: Deployment to state the resource type. However if you change labels and run the same. kubectl delete -f nginx-rs. Open your terminal, and run the kubectl create command below to create a new namespace ( ns ) called mongodb on your Kubernetes cluster. This output shows that the ReplicaSet frontend along with the number of replicas currently running. kubectl get replicaset. it will reset it back to 3. Make sure that the kubectl client version is skewed no more than one version from the Kubernetes master version running on your Azure Stack Edge Pro device. This procedure allows you to set different settings for the replica set resource, such as overrides for statefulSet configuration. 8. Here the replicas field is set to 3, but you can set it to whatever fits your application. We have now logged into the MySQL database. replicas}{" "}' 2 $ kubectl get rs pet2cattle-5479f4b6cb NAME DESIRED CURRENT READY AGE pet2cattle-5479f4b6cb 2 2 2 5d5hA service is basically a load balancer over a deployment (and a deployment is a replica set of multiple pods). Now run the command $ sudo kubectl. kubectl delete sts --cascade=orphan <name> to delete the StatefulSet and leave its pods. The differences in this manifest are: Using kind: Deployment to state the resource type. It looks a lot like the other pods, but it is using Apache (instead of Nginx for an image. Whenever you deploy new version of deployment, the replica set preserves the previous configuration of the deployment. The following imperative command helped me remove all the pods in a ReplicaSet without deleting the ReplicaSet. yml kubectl get pods Code language: CSS (css) As you can see from my screenshot, we now have two pods running as we were expecting. yaml Check the status of the autoscaler using the kubectl get hpa command. Ask Question Asked 5 years, 3 months ago. Use kubectl directly. 3. Then they are in your desired number of replicas. Kubectl Scale use cases. getenv ("MY_REPLICASET")) and have a result like: [frontend-b2zdv,frontend-vcmts,frontend-wtsmm] that is the pod names of all the container's replicas (also the current container of course) and eventually compare the current name in the name list to get my index in the. I assume that you want the default 'rolling upgrade' behavior of Deployments: they create a new replica set and start it before the old one is drained (rolling upgrade). $ kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES sample-pod3-rzmhb 2/2 Running 0 38s 192. 13. kubectl expose pod rabbitmq-0 --port=15672 --target-port=15672 --type=NodePort. Old Replica set are removed. The API version apps/v1beta2 is deprecated. Install and Set Up kubectl on Linux; Install and Set Up kubectl on macOS; Install and Set Up kubectl on Windows; Administer a Cluster. 1 <none> 443/TCP 9d NAME READY UP-TO-DATE AVAILABLE AGE deployment. vi d. kubectl get storageclass NAME PROVISIONER standard (default). The pods must have labels that match the specified labels here. yaml. If the mode is blank or iptables, the traffic is distributed round-robin. extensions/frontend scaled master $ kubectl get pods NAME READY STATUS RESTARTS AGE frontend-4jb2x 1/1 Terminating 0 38s frontend-98xkj 0/1. 7k 2 38 55. First find the pvs: kubectl get pv -n {namespace} Then delete the pv in order set status to Terminating. Step 2: Edit the pod labels which no longer match the replicaset selectors. The kubectl get command allows a user to inspect cluster resources. When using a Deployment, the actual pods are created and managed by the Deployment’s ReplicaSets, not by the Deployment directly. Run kubectl get rs to see the deployed replicaset kubectl get rs. List all services and get the nodePort which can be used locally, e. 69. Scaling_and_replica gauravagnihotri$ kubectl get deployment NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE tomcat-deployment 1 1 1 1 3m13s. kubectl get deployments -w. yaml’, and we will be submitting this file to the Kubernetes cluster. // demonstrate to change the number of Pod replicas. spec section. And the -w argument is for watch so you have a refreshed interface that gives you infos on your hpa ressources. master $ kubectl scale rs frontend --replicas 2 replicaset. yaml # or another way of writing "kubectl scale --replica=10 replicaset <replicaset name as provided in metadata>" kubectl scale --replica=10 replicaset myapp-rs. 80 383 more pod1. ***> wrote: You don't need to run any script in order to cleanup old replica sets - just set . Scaling the replicaset can be done by using two methods. replicas and all old Replica Sets will be scaled to 0. I am creating a deployment using this yaml file. yaml 384 clear 385 kubectl get pods 386 kubectl delete deploy my-dep 387 clear 388 kubectl get pods 389 clear 390 kubectl get pods 391 kubectl apply -f pod1. 1 Answer. After executing the kubectl scale command to set the replicas to zero, running kubectl get pods will show that there are no Pods running in the default namespace since all the Pods were terminated. Running the kubectl get pods command shows the rollout of two new pods with the updated version 1. – P. Get Pods. In this article, we will look into how to connect Replicaset to a Pod in. kubectl get events -w. If you want the rolling update functionality please consider using Deployments instead. See moreIf you inspect how kubectl does it (by executing kubectl -n my-namespace describe deploy my-deployment --v=9) you will see that it dos the following: first gets. kubectl edit pod <Name of the Pod> Step 3: Apply the pod by using the following command. Also the command won't show the situation when DESIRED = 2 but RUNNING = 1. kubectl create -f my-replica. Tujuan dari ReplicaSet adalah untuk memelihara himpunan stabil dari replika Pod yang sedang berjalan pada satu waktu tertentu. kind: This is the type of Kubernetes object. 26 introduced a new, alpha-level feature for StatefulSets that controls the ordinal numbering of Pod replicas. Set an alias for kubectl in Bash. Deployments . get_my_replicaset_names ()) or. yaml Step 4: Set up Replication Host. In the Kubernetes API documentation it's mention that there is a PUT request to do the same. kubectl scale --replicas=3 statefulset/web. In order to remove the ReplicaSet from the Kubernetes system, you can rely on the subcommand delete. Installed kubectl on the client and saved the kubeconfig file with the user configuration to C:Users<username>. You can get help from kubectl logs -h and according the info, . name 是命名这些 Pod 的部分基础。. ReplicaSets. Replica Set is a next generation of replication controller. ReplicaSet 的名称必须是一个合法的 DNS. +1 to what blixt said. Use kubectl directly. name=rolling-nginx-74cf96d8bb-6f54x LAST SEEN TYPE REASON OBJECT MESSAGE 5m21s. replicas | contains(0)) | "kubectl delete rs --namespace=(. kubectl get endpoints Code language: JavaScript (javascript) Once the service and endpoint are deployed, we’ll deploy a quick container into our. In a few minutes, you will see that there are 5 MongoDB pods. Kubernetes client (kubectl) sent a request to the API server requesting the creation of a ReplicaSet defined in the replicaset-app. To get the list of available Kubernetes StatefulSets use: bash. To expose the external deployment as a NodePort service, you can specify the type as NodePort in kubectl expose: shell. Replica Sets, as the name implies, define how many replicas of each pod will be running. ReplicaSets guarantee that there will be a specific number of identical Pods running at any given time. It creates a selector that matches to matchLabels. metadata. The Horizontal Pod Autoscaler automatically scales the number of pods in a replication controller, deployment or replica set based on observed CPU utilization (or, with custom metrics support, on some other application. MySQL settings remain on insecure defaults to. Here we go. Follow. (Remember, a controller in Kubernetes is what takes care of tasks to make sure the desired state of the cluster matches the observed state. 🕸️Simple Difference Between ReplicaSet and Deployment. $ kubectl get hpa -w. Their purpose is to keep a set of identical pods running and upgrade them in a controlled way. To check the mode of the kube-proxy : (it should be either iptables or ipvs or blank) kubectl get cm -n kube-system kube-proxy -o jsonpath=' {. In the above screenshot, you can see the details of the ponds created after creating a replica set. (Allows more disruptions at once). Background. 1. Example-2: Create replica set using match expressions. kubectl describe replicaset replicaset-name. kubectl apply -f [manifest file] Code language: CSS (css) Let’s check the endpoint just to make sure it looks correct. Once the ReplicaSet is created, you can check its status using the kubectl get replicaset. Run the command kubectl get pods and count the number of pods. $ kubectl apply -f deployment. As with all other Kubernetes config, a DaemonSet needs apiVersion, kind, and metadata fields. 1. A caveat to note is that if you pass a deployment or a replica set, the logs command will get the logs for the first pod,. The kubectl run command can take a number of arguments to configure additional parameters of the deployments. yml file called ‘frontend. Time for scaling! 1st. Share. $ kubectl run my - nginx -- image = nginx. Check to see whether the kube-controller-manager is running or crashing or logging errors. The ReplicaSet. 2. deployment "my-nginx" created. If we want to check the status of the replica set, then run the below command. Ensure that you add s for each Kubernetes pod that hosts a member of your replica set to the certificate. Another way of scaling your controller is using kubectl scale --replicas=1 rc/expressapp-controller. The same can be achieved with kubectl create -f ( -f is a flag for specifying file. How Deployments Work. This will make the old replica set get drained before the new one is started. Get replicaset. 1. conf} {" "}' |grep mode. Use the following command to delete the Kibana object: $ kubectl delete Kibana quickstart-kb. We want to perform such a migration with no downtime and minimal. $ kubectl apply -f replicaset. When connecting to a replica set, the hostnames and IP addresses in the connection string are the seed list. Deploying. This will open the ReplicationController’s YAML definition in your default text editor: bash. name }') This should be more stable because it processes the replica count directly instead of trying to parse the output of kubectl which might. 14. Add a comment | 20. $ kubectl exec —namespace default MASTER_POD_NAME — mongo —eval=“printjson (db. Every replica is named in sequential order, beginning from ordinal number zero. g. Now , you will need to either delete the replica sets or delete the existing pods: kubectl delete rs new-replica-set kubectl delete pod pod_1 pod_2 pod_2 pod_4. spec. Install kubectl and minikube. Along with the Deployments came the Replica Sets (RS), a kind of more powerful RC (supporting set-based labels). For example, kubectl scale –replicas=2 rs/web. A link to the MyEd BC portal can be found on the Oak Bay website underReplica Rocks is a Victoria BC company that creates premium resort style outdoor living spaces. This way the deployment will be marked as paused and won't be reconciled by the controller. I am creating a new deployment, but when I apply my yaml file the replicas Pods Status are waiting instead of available. Cómo funciona un ReplicaSet Un ReplicaSet se define con campos, incluyendo un selector que indica cómo identificar a los Pods que puede adquirir, un número de. There can be multiple reasons – node maintenance, migration to another rack, datacenter, or newer hardware. You could also use the command: kubectl create -f rs. In case, these pods go down then this replicaset can use it’s template to replace these pods. In order to remove the ReplicaSet from the Kubernetes system, you can rely on the subcommand delete. Normal SuccessfulCreate Created pod: frontend-9si5l $ kubectl get pods NAME READY STATUS RESTARTS AGE frontend-9si5l 1/1 Running 0 1m frontend-dnjpy 1/1 Running 0 1m frontend-qhloh 1/1 Running 0 1m ReplicaSet as an Horizontal Pod Autoscaler target. kubectl get hpa constant-load-test -n hpa-constant-load. A pod doesn't "run" a replica set, and there is no such thing as a "primary set". kubectl create --help |awk '/Available Commands:/,/^$/' Available Commands: clusterrole Create a cluster role clusterrolebinding Create a cluster role binding for a particular cluster role configmap Create a config map. Wherever applicable, kubectl get all returns a list of pods, services, daemon sets, deployments, replica sets, jobs, cronjobs, and stateful sets. This should create the replica sets for MongoDb. It will show the number of desired Pods, Ready Pods, and Current Pods count. mourya ~ % kubectl get statefulset NAME READY AGE web 0/0 33s deepak. selector section so that new replicaset and deployment can. the service has its clusterIP set to “None” and hence will prevent the service from having an IP giving clients the ability to connect directly to what lies behind it. 9, la version de l'API apps/v1 pour le type ReplicaSet est la version actuelle et activée par défaut. To scale down the pods under we can use same scale command but here we have to reduce the number of replicas. We will explain: What RS is. 08 18:00:57 字数 2,721. $ kubectl get pod NAME READY STATUS RESTARTS AGE myapp-replicas-67rkp 1/1 Running 0 33s myapp-replicas-6kfd8 1/1 Running 0 33s myapp-replicas-s96sg. But when I edit this deployment using the command kubectl edit deployment my-dep2, only changing the version of busybox image to 1. Sorted by: 2. DaemonSets run only a single pod replica on each node, whereas ReplicaSets scatter them around the whole cluster randomly. yaml and repeate for deployment. $ kubectl apply -f my-nginx. To scale up set --replicas=1 (or any other required number) accordingly. # Create ReplicaSet kubectl apply -f 02-replicaset-definition. Most kubectl commands that support Replication Controllers also support ReplicaSets. kubectl get replicaset. Kubectl apply -f <name of the pod> Scaling a ReplicaSet . Manually by using the command. kubectl scale rs new-replica-set --replicas 0 kubectl scale rs new-replica-set -. Kubernetes Replication Controller vs DeploymentYou need to use -c flag to specify the Container name. -c, --container='': Print the logs of this container -f, --follow=false: Specify if. If we execute the commands: kubectl get sts mongodb and kubectl get pods -l app=mongodb , we see the cluster deployed. Anything else we need to know?: I realize that in my example, the HPA is unable to read the resource metric and that may be a contributing factor in the calculation of the desired replica count. You can get the list of configured node ports using the command below: echo "$. The following kubectl command sets the spec with progressDeadlineSeconds to make the controller report lack of progress of a rollout for a Deployment after 10 minutes: kubectl patch deployment/nginx-deployment -p ' {"spec": {"progressDeadlineSeconds":600}}'. apps/nginx 1/1 1 1 6m54s NAME DESIRED CURRENT READY AGE replicaset. The issue happen because the Replica Set configuration points to the other nodes using your internal cluster IPs, so you will see. Syntax: $ kubectl [command] [TYPE] [NAME] [flags] Command: This will include the operation mentioned below you want to perform regarding the specific resource. {target} is the name of the pod you want to view logs from;kubectl scale deployment my-deployment --replicas=0. Install and Set Up kubectl on macOS; Install and Set Up kubectl on Windows; Administer a Cluster. Cara kerja ReplicaSet Sebuah ReplicaSet didefinisikan dengan beberapa field. kubectl get pods. kubectl logs -l=app= {app-name} -c= {container-name} -n= {namespace} As you can see the options with the kubectl logs -h command. As with all other Kubernetes API objects, a ReplicaSet needs the apiVersion, kind, and metadata fields. print (os. kubectl get pods NAME READY. Log in to CEE CLI and confirm that no active alerts and system status must be at 100%. statefulset. When changing the image I found this to be the most straight forward way to update the . As such, it is often used to guarantee the availability of a specified number of identical Pods. 12. HPA is a form of autoscaling that increases or decreases the number of pods in a replication controller, deployment, replica set, or stateful set based on CPU utilization—the scaling is horizontal because it affects the number of instances rather than the resources allocated to a single container. g. kubectl get replicaset. Nice! With just a single line we launched a pod with two containers into the Kubernetes cluster. Use this procedure to create a new replica set in a member Kubernetes cluster in a multi-Kubernetes-cluster deployment. co/v1 kind: Kibana. metadata. To obtain them, follow the instructions below: MongoDB® nodes domain: you can reach MongoDB® nodes on any of the K8s nodes external IPs. Possible Solution 1: set maxUnavailable to 1 (works with varying scale of application). 5. In Kubernetes, if you will set replica value to 0, you will not have any running pod in this specific Deployment. You can insert a key into the primary instance of the MongoDB Replica Set by running the following: MASTER_POD_NAME must be replaced with the name of the master found in the previous step. This replica will further create a pod with name web-app-<replica-set->-<pod-id>.