They don’t cost much just sitting there in Kubernetes’ etcd store, but if you run monitoring or continuous validation tools, they may be slowing you down. $ kubectl config set PROPERTY_NAME PROPERTY_VALUE kubectl config unset − It unsets a specific. 26 introduced a new, alpha-level feature for StatefulSets that controls the ordinal numbering of Pod replicas. On the detail checking of replica set shown that the pod recreated when it’s deleted. Imperative config management with commands. </li> </ul> <div class="snippet-clipboard-content notranslate position-relative overflow-auto" data. apps/nginx 1/1 1 1 6m54s NAME DESIRED CURRENT READY AGE replicaset. kubectl describe replicaset replicaset-name. print (os. Wherever applicable, kubectl get all returns a list of pods, services, daemon sets, deployments, replica sets, jobs, cronjobs, and stateful sets. You can also use "watch" flag to refresh view each 30 seconds. Cómo funciona un ReplicaSet Un ReplicaSet se define con campos, incluyendo un selector que indica. kubectl apply-f my-manifest. g. Learn more about Teamskubectl get pods -l 'env in (development, testing)' kubectl get pods -l 'env notin (development, testing). imagkubectl 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) $ kubectl version . Normally, the old (previous). Also you can read in the documentation Horizontal Pod Autoscaler. 1 <none> 443/TCP 9d NAME READY UP-TO-DATE AVAILABLE AGE deployment. It makes sure that a stable set of replica pods is running at any given time, which guarantees an available specified number of identical pods. kubectl -n NAMESPACE get deploy/DEPLOYMENT_NAME Then scale it up. For example, if the variable is set to seattle, kubectl get pods would return pods in the seattle namespace. For ReplicaSets, the kind is always a ReplicaSet. Add a comment. Accessible as localhost:15672. Example-2: Create replica set using match expressions. Deleting a ReplicaSet. yaml file. 1-57c75779f-8sm9r 2/2 Running 0 16h. 3. Thanks this one worked. kubectl delete deployment nginx --namespace=kube-system. kubectl delete rc hello-rc --cascade=false this means the pods are no longer managed . First pods with your new revision will be created, but replicas of your old ReplicaSet will only be scaled down when you have. I tested this on kubernetes 1. What is a Mongo Replica Set. If you have used the kubectl rollout history command you might have noticed that it displays only the last 10. Certificate. kubectl scale --replicas=3 statefulset/web. How to delete all the resources Including service, deployment , pods, replica-set for particular deployment excluding specific one in kubernetes. DaemonSets create Pods on every node in the cluster by default, unless node selectors constrain them. Verwaltung mit kubeadm. (Remember, a controller in Kubernetes is what takes care of tasks to make sure the desired state of the cluster matches the observed state. yaml. If we want to check the status of the replica set, then run the below command. yaml Give it a few moments for the image to get pulled and the container is spawned then run kubectl get pods. A replica set is a group of MongoDB deployments that maintain the same data set. The next part in the manifest is the selector field. test. # List Pods kubectl get pods # Delete Pod kubectl delete pod <Pod-Name>. To learn more about this issue, see Kubernetes Issue 67250. kubectl scale deployment. StatefulSets (since Kubernetes 1. /cluster/kubectl. So i need to used version in . Kubectl apply -f <name of the pod> Scaling a ReplicaSet . This can help your applications scale out to meet increased demand or scale in when resources are not needed, thus freeing up your nodes for other applications. The API version apps/v1beta2 is deprecated. Now delete a pod, while watching pods: kubectl delete pod rs-quarkus-demo-mlnng. In case if you are working in a specific kubernetes namespace then I would recommend using the -n flag. 08. In the Kubernetes API documentation it's mention that there is a PUT request to do the same. In stateful applications, it’s important that a given replica keeps the initially assigned PV even if pods get rescheduled. batch/busy-job-completion created $ kubectl get po NAME READY STATUS RESTARTS AGE busy-job-2wg9f 0/1 Completed 0 19m busy-job-completion-bfh49 0/1. 1. [root@localhost ~]# kubectl get rs NAME DESIRED CURRENT READY AGE web-app 2 2 2 70s To verify the replicas created by the ReplicaSet YAML file you can use kubectl get. The output will look similar to this, with the frontend ReplicaSet’s info set in the metadata’s. Install and Set Up kubectl on macOS; Install and Set Up kubectl on Windows; Administer a Cluster. To check the version, use the kubectl version command. Create a folder called /kubernetes_experiments and in that folder run. Install and Set Up kubectl on Windows; Installieren und konfigurieren von kubectl; Kubectl installieren und konfigurieren auf Linux; Kubectl installieren und konfigurieren auf macOS; Installation von Minikube; Einen Cluster verwalten. spec. Run the command kubectl edit replicaset new-replica-set, modify the replicas and then save the file. PjoterS PjoterS. Scaling the replicaset can be done by using two methods. Sep 16, 2022 at 21:35. spec section is similar to the ReplicaSet’s, defining the pod template for each replica. Post a CommentYou can exit the pod using Ctrl+D, or by running exit in the console. Ensure that you add s for each Kubernetes pod that hosts a member of your replica set to the certificate. name=rolling-nginx-74cf96d8bb-6f54x LAST SEEN TYPE REASON OBJECT MESSAGE 5m21s. 概述. kubectl get storageclass NAME PROVISIONER standard (default). kubectl get rs new-replica-set -o yaml > rs. kubectl apply -f [manifest file]. 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. See also the documentation for more options on deployments. yaml # or another way of writing "kubectl scale --replica=10 replicaset <replicaset name as provided in metadata>" kubectl scale --replica=10 replicaset myapp-rs. To master Kubernetes, you need to understand how. 3. A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time. answered Dec 26. After deploying the replica set or replication controller, if you need to edit the file, you can use the command kubectl edit to edit. As an alternative to using this procedure, you can use the Multi-Kubernetes-Cluster Quick Start. This command will create a new replica set with updated pods and will gradually scale down the old replica set while scaling up. because what you are doing is not deleting the deployment but setting the desired replica count to 0. El objeto de un ReplicaSet es el de mantener un conjunto estable de réplicas de Pods ejecutándose en todo momento. yaml in which a deployment, whose strategy is RollingUpdate, is defined. StatefulSets are designed to run stateful applications in Kubernetes with dedicated persistent storage. Modified 5 years, 3 months ago. mongodb-2 – Read-only replica. selectorbut whose template does not match . 3. Use this procedure to create a new replica set in a member Kubernetes cluster in a multi-Kubernetes-cluster deployment. How can I get all the logs from a specific container (s) that are running in a replica set. The --cascade option set to "orphan" tells the command to only delete the replicaSet without deleting the pods. Damith June 10, 2020, 8:57am #10. 1 2022. Use get -h to see a list of options. 🕸️Simple Difference Between ReplicaSet and Deployment. yaml and re-apply it to update the deployment. The key to the replica set is the commands on runtime in the arg key field. I would like to get all ReplicaSets that have any problems using kubectl only without external monitoring systems. Pour ReplicaSets, l'attribut kind est toujours ReplicaSet. These correspond to the three nodes in your MongoDB replica set. Follow answered Jun 10, 2020 at 14:30. Step 2: Edit the pod labels which no longer match the replicaset selectors. For a single pod you can use the following command: kubectl logs {target} -f. Although ReplicaSet's main purpose is to maintain a stable set of replica Pods, it's not a kubernetes object that is commonly created,. Administration with kubeadm. items [*]. First, check the existing replica set using the following command. This procedure allows you to set different settings for the replica set resource, such as overrides for statefulSet configuration. Kubernetes Replica Sets - Replica Set ensures how many replica of pod should be running. For example, deploying the same. Deleting Replica Set. 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. phase field is. Replication controller is kinda imperative, but replica sets try to be as declarative as possible. kubectl delete rs {NAME_REPLICA_SET} kubernetes. yml from 3 to 6. Now copy your deployment file to a master node and apply it. $ kubectl get all NAME READY STATUS RESTARTS AGE pod/nginx-854998f596-6jtth 1/1 Running 0 52s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10. If we need to update the application to a new version, we can create a new replica set with the updated configuration and scale down the old replica set. Scale down the sts kubectl scale --replicas=0 sts <sts name>. kubectl scale rs/new-replica-set --replicas=0. 492suser 0m0. A ReplicaSet is used to ensure that a specific number of replicas (copies) of a pod are running at any given time, while a Deployment manages updates to a ReplicaSet by creating a new ReplicaSet with the updated pod template and gradually scaling it up while scaling down the old ReplicaSet. Replica Sets (usually written as . kubectl run now creates a deployemtn+replica-set. 2 ReplicaSet的伸缩A Deployment is a Kubernete’s object which is used to create, update and delete a set of Identical Pods. kubectl scale rs new-replica-set --replicas 0 kubectl scale rs new-replica-set -. If you need to get events related to specific objects, this can be achieved by describing an object using the command kubectl describe object/object_name. Log in to CEE CLI and confirm that no active alerts and system status must be at 100%. kubectl delete sts --cascade=orphan <name> to delete the StatefulSet and leave its pods. Installed kubectl on the client and saved the kubeconfig file with the user configuration to C:Users<username>. thank you3- If yes and you update the image name for that deployment. Scaling your Deployment down to 0 will remove all your existing Pods. name)"'. Get the replica sets list. When we fire delete to remove the resource, it removes the target objects forcefully: $ time kubectl delete rs my-first-replicaset && kubectl get podreplicaset. Great explanation. Normally, you can't delete ReplicaSet easily because it is controlled by another entity. I have enabled external access with SVC type LoadBalancer. Delete the CRD object itself, to delete the deployment and other objects (if any) that were created with it. Step 2: Edit the pod labels which no longer match the replicaset selectors. To ensure that, pods must be managed as stateful sets. Instead we use Deployment to manage a ReplicaSet. user@pc:/# kubectl delete pod sql1-0 -n arc pod "sql1. Display information about the ReplicaSet in the current namespace $. There can be multiple reasons – node maintenance, migration to another rack, datacenter, or newer hardware. kubectl delete pod <podname> ReplicaSets. selector section so that new replicaset and deployment can. Replica set, also termed as rs in short, is almost same as the replication controller is, only with a single difference. A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time. I have deployment and a replica set in Kubernetes that are failing to create a pod. name=backend. service "nginx" created. $ kubectl apply -f busy-job-completion. $ kubectl get pods,replicasets --show-labels NAME READY STATUS RESTARTS AGE LABELS pod/kuard-fm8fd 1/1 Running 0 11m app=kuard pod/kuard-j6fcf 1/1 Running 0 11m app=kuard pod/kuard-jmqjv 1/1. A ReplicaSet is defined with fields, including a selector that specifies how to identify Pods it can acquire, a number of replicas indicating how many Pods it should be maintaining, and a pod template specifying the data of new Pods it should create to meet the number of replicas criteria. 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}}'. We often don’t need to create a ReplicaSet directly. 使用kubectl delete命令会删除此RS以及它管理的Pod。在Kubernetes删除RS前，会将RS的replica调整为0，等待所有的Pod被删除后，在执行RS对象的删除。 如果希望仅仅删除RS对象（保留Pod），请使用kubectl delete命令时添加--cascade=false选项。 3. 1. yaml After some time, we modify d. kubectl apply -f aks-store-quickstart-hpa. ReplicaSets. data. Stateful sets perform the same role for stateful pods. Declarative config management. Apply the YAML with kubectl. 4. kubectl get deployments --all-namespace. We will explain: What RS is. Conditions: Type Status Reason ---- ----- ----- ReplicaFailure True FailedCreate Events: <none>You can use the kubectl expose command to create a NodePort Service for a ReplicaSet. $ kubectl get hpa -w. Enter the pod using kubectl exec: kubectl exec -it mongodb-replica-0 -n default -- mongo. Use --record while creating the deployment so that it will start recroding the deployment into the ReplicaSet. As with all other Kubernetes API objects, a ReplicaSet needs the apiVersion, kind, and metadata fields. kubectl is a command-line tool for interacting with a Kubernetes cluster. kubectl describe replicaset {NAME. ReplicaSetのreplica数を増減させる. Look out for stateful sets as well . Code: kubectl get replicasets. To further ensure that pods only get scheduled on that set of tainted nodes, you can also add a label to those nodes, e. extensions/sample-rs scaled でちゃんとpodの数が6個になっているか確認してみる。In this manner, a ReplicaSet can own a non-homogenous set of Pods. They are handy when it comes to rolling out changes to a set of pods via a ReplicaSet. While we won’t be providing a tutorial for managing Deployments via kubectl, we will be using. This is something you have to bear in mind. $ kubectl get hpa. kubectl get replicaset. If so, deleting it should also delete the replica set and the pods that you created. Options: --all-containers=false: Get all containers's logs in the pod (s). To expose the external deployment as a NodePort service, you can specify the type as NodePort in kubectl expose: shell. However if you change labels and run the same. This is because pods are a namespaced resource, and no namespace was provided in the command. Most kubectl commands that support Replication Controllers also support ReplicaSets. 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. root@cyberithub:~# kubectl get pods -l tier=nginx NAME READY STATUS RESTARTS AGE replicaset-1-nhvlq 1/1 Running 0 16m replicaset-1-mrj7v 1/1 Running 0 16m. To create a replica said execute the following command. 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. Share. Each replica will be created in order from 0-N and deleted in reverse order from N-0. Imperative way: (this will then diverge from what you have in your yaml-file) kubectl scale deployment mage-di --replicas=2. Get details of a replica set: kubectl describe replicaset webapp. For any queries, feel free to contact me at yatharth. However we also want to delete the replicasets and pods that below to 'our-deployment-name'. $ kubectl create -f <replicaSet_file_name>. You can observe how the autoscaler kicks in when load increases, and increments the quote server deployment replica set to a higher value. $ kubectl exec —namespace default MASTER_POD_NAME — mongo —eval=“printjson (db. Lets now delete the pod created independent of replica set. Try kind: Deployment. yaml Check the status of the autoscaler using the kubectl get hpa command. One exception is the rolling-update command. If you created HPA you can check current status using command. yaml After that remove unnecessary fields. Scale a replica set: kubectl scale --replicas=5 rs. So, we will be using the following command: kubectl exec -it mongodb-0 --. clusterIP}} Check the nginx welcome page is there via a browser or downloading it with curl:Then the docker. To start, run this little command: kubectl get rs --all-namespaces | wc -l. The selector and matchingLabels is used by the replicaset to monitor other pods as well who have the matching labels. In this blog post we are going to discuss the ReplicaSet concept in Kubernetes. name of the ReplicaSet is part of the basis for naming those Pods. How can I changeg them to running status. -69946b945f-txvvr 2m24s Normal ScalingReplicaSet deployment/dummy-deployment Scaled up replica set dummy-deployment-69946b945f to 1 kubectl -n default get pods | grep. 7k 2 38 55. You’ll find all the object-specific events in the. spec. How Deployments Work. Use kubectl version to check the version of kubectl. madhusudancs title: Replica Sets; TOC {:toc}. 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. apps -n <namespace> (or --all-namespaces) – Noam Manos. After it's paused you can make necessary changes to your configuration and then resume it by using kubectl rollout resume. yaml replicaset. If we need to update the application to a new version, we can create a new replica set with the updated configuration and scale down the old replica set. You cannot create replicaset using the command line. They behave in a similar way, but they have more expressive pod selectors. Restart will appear and number will increase incrementally in RESTARTS column of kubectl get pods -n <namespace> command output. List the available daemon sets: [root@controller ~]# kubectl get ds NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR. info 2019-04-01T14:03:33Z. $ kubectl scale deploy nginx --replicas=0 deployment. 0. kubectl get pods. Login to the MySQL pod and Verify: kubectl exec -it mysql-0 -- mysql -u root -p. 当控制平面为 ReplicaSet 创建新的 Pod 时，ReplicaSet 的 . Create a stateful set. Using kubectl, we can apply this definition like: kubectl apply -f orphan. Output. First, check the existing replica set using the following command. kubectl get deployments -w. kubectl create -f replicaset. kubectl get pods frontend-b2zdv -o yaml. analogy: Head chef instructs the team of line cooks to prepare a certain dish. 168. Replica sets ensure that the desired (minimum) number of replicas of a stateless pod for a given application are running. Now let’s inspect the ownerReferences of the ReplicaSet. yaml job. Then use NodeSelector in the deployment/pod. A ReplicaSet ensures that a specified number of pod replicas are running at any given time. print (k8s. They manage the deployment of Replica Sets (also a newer concept, but pretty much equivalent to Replication Controllers), and allow for easy updating of a Replica Set as well as the ability to roll back to a previous deployment. namespace) (. Get replicaset. kubectl apply -f stateful-set. Manages the deployment and scaling of a set of Pods, and provides guarantees about the ordering and uniqueness of these Pods. Así, se usa en numerosas ocasiones para garantizar la disponibilidad de un número específico de Pods idénticos. g. Deployments . When you. yaml kubectl delete rs new-replica-set kunectl create -f rs. This should create the replica sets for MongoDb. 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. spec. You should see an output that looks like the following:When we then look at the Replica set we can see that it was actually deployed a new Replica set with pods running the new image. yml # List Replicasets kubectl get rs. A ReplicaSet is a Kubernetes resource used to maintain a specified number of identical pod replicas within a cluster. 4. A pod doesn't "run" a replica set, and there is no such thing as a "primary set". kubectl get rs. 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. Once the ReplicaSet is created, you can check its status using the kubectl get replicaset. Once the Mongodb replicaSet is up, cd into the user-service and execute kubectl create -f . kind: This is the type of Kubernetes object. The Deployment controller will automatically create a new pod. Then, create, scale, and update a deployment with the following commands: kubectl run deployment web --image=nginx kubectl scale deployment web --replicas=10 kubectl set image deployment web nginx=that-image-does-not-exist. yaml. extensions. $ kubectl create -f replica. kube. yml # Verify if new pods got created kubectl get pods -o wide. Kubectl autocomplete BASH source <(kubectl completion bash) # set up autocomplete in bash into the current shell, bash-completion package should be. You can see them with this command: kubectl get pods NAME READY STATUS RESTARTS AGE mongo-0 2/2 Running 0 3m mongo-1 2/2 Running 0 3m mongo-2 2/2 Running 0 3m. kubectl get replicaset. By default, Kubernetes keep 10 replica sets for each deployment, which means you can go back 9 versions prior. $ kubectl set image deployment/newsconsumer-deployment. a number of replicas indicating how many Pods it should be maintaining. yml service/nginx unchanged The StatefulSet. Get a idea from yaml file. Set an alias for kubectl in Bash. Spring Boot Maven Multi Modules on Visual Studio Code 20. If you run kubectl get pods <pod_name> -o yaml where <pod_name> is a pod created by ReplicaSet, you will see owner reference. In the replica sets, we used the selector. apps/nginx 1/1 1 1 6m54s. A more complex use case is to run several identical replicas of a replicated service, such as web servers. yaml. Toye Idowu. Also, the rolling-update command is imperative whereas Deployments are declarative, so we. yaml Step 4: Set up Replication Host. 1. If the mode is blank or iptables, the traffic is distributed round-robin. test. A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. Install Docker. I've tried. The $ kubectl get all command will list all the resources from all of your workspace, so that you will have a very good idea of how many PODS, Deployments, Services, and Replica Sets are running inside your Kubernetes cluster. Step-02: Create ReplicaSet. kubectl delete pod <name of managed instance>-0 -n <namespace of data controller> For example. yml Verifying the replica set deployment and accessing the replica set. For example, you can do the following: Set environment variables with --env. kubectl get events -w. kubectl get pods. Sorted by: 2. kubectl get replicaset new-replica-set -oyaml >> replica. In order to remove the ReplicaSet from the Kubernetes system, you can rely on the subcommand delete. For now I'm able to increase the replicas from CLI using the command: kubectl scale --replicas=3 deployment my-deployment. mourya ~ % kubectl get statefulset NAME READY AGE web 0/0 33s deepak. yaml Step 4: Set up Replication Host. Run kubectl get rs (ReplicaSet) to see ReplicaSets created by the deployment. extensions "my-first-replicaset" deletedreal 0m2. 9, la version de l'API apps/v1 pour le type ReplicaSet est la version actuelle et activée par défaut. yaml pod/my-pod created Method 2: Rolling Restart of a Deployment. January 9, 2019. To update a Kubernetes deployment we can simply update its config file using 2. The output is similar to this:$ kubectl get deployment -o wide # check the deployment $ kubectl get rs -o wide # When you create a deployment resource,. kubectl scale command is used to change the number of running replicas inside Kubernetes deployment, , replication controller, and stateful set objects. Scaling the replicaset can be done by using two methods. 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. One method of accessing this declarative interface is through kubectl. A ReplicaSet is defined with fields, including a selector that specifies how to identify Pods it can acquire, a number of replicas indicating how many Pods it should be maintaining, and a pod template specifying the data of new Pods it should create to meet the number of replicas criteria. Port Forwarding will make a local port on your machine redirect (forward) traffic to some pod. kubectl get statefulsets <stateful-set-name> Change the number of replicas of your StatefulSet: kubectl scale statefulsets <stateful-set-name> --replicas=<new-replicas> To show you an example, I've deployed a 2 pod StatefulSet called web:@HunzlaSheikh When you run kubectl delete -f render. If you have used the kubectl rollout history command you might have noticed that it displays only the last 10. 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. Run Command $ sudo kubectl create -f service. 1 <none> 443/TCP 9d NAME READY UP-TO-DATE AVAILABLE AGE deployment. The differences in this manifest are: Using kind: Deployment to state the resource type. revisionHistoryLimit' 2 $ kubectl get rs NAME DESIRED CURRENT READY AGE nginx-696171888 2 2 2 59s $ kubectl set image. Can you try kubectl get deploy --field-selector metadata. Delete replica set. Therefore, we have implemented a small handling charge of $1. metadata. This is where you specify how the ReplicaSet. This is managed by a ReplicaSet. yaml. Manually by using the command. Old Replica set are removed. It creates a replica of 4 busybox pods. We will explain: What RS is. ssh -p 2024 admin@`kubectl get svc -A| grep " ops-center-cee" | awk '{print $4}'` show alerts active. As such, it is often used to guarantee the availability of a specified. The challenge I am having is that, I want to be able to loop through all the deployments and save their name and number of replicas so I scale them back to the original after scaling down. List the available StatefulSets. # Get commands with basic output kubectl get services # List all services in the namespace kubectl get pods --all-namespaces # List all pods in all namespaces. You can omit the header by using:163 1 1 14. $ kubectl api-versions. Just change the replica count from 2 to 3 and apply the YAML file. Improve this answer. – lindluni. kubectl logs -f deployment/myapp -c myapp --tail 100 -c is the container name and --tail will show the latest num lines，but this will choose one pod of the deployment, not all pods. kubectl get deployments NAME READY UP-TO-DATE AVAILABLE AGE ngnix-deployment 0/3 3 0 12m kubectl. kubectl get service nginx ip=$(kubectl get svc nginx --template={{. kubectl config set-credentials − Sets a user entry in kubeconfig.