If you already have one or more database deployments, click Create. revisionHistoryLimit is an optional field that specifies the number of old ReplicaSets to retain to allow rollback. To start with the deployment of the new cluster, go to the deploy option in the top right corner. In this method, we’ll be setting up replica sets with the access control disabled for deploying it in a testing environment. root@k8s:. In docs about owners and dependents it says:. the old replica sets are not removed they are retained for the versioning. The deployment will indicate the current "revision" of the replica set with the deployment. The relation between Deployment, Replicaset & POD. However, if you just want to distribute a deployment among all nodes then you can use pod anti affinity in your pod manifest file. The Deployment is managing the ReplicaSet and the ReplicaSet is managing the pods. This is how the deployment is usually rolled out. Now we’ll create a Kubernetes service using our deployment from the previous section. The Deployment creates a ReplicaSet that creates three replicated Pods, indicated by the . The deployment automatically creates a replicaset object. Update the deployment. Manages the deployment and scaling of a set of Pods, and provides guarantees about the ordering and uniqueness of these Pods. Therefore, it is recommend to use Deployments instead of directly using ReplicaSets unless you don’t require updates at all. It uses a template to describe what each Pod must contain. Cet objet est souvent utilisé pour garantir la disponibilité d'un certain nombre identique de Pods. We first create a deployment: kubectl apply -f d. While this command doesn’t explicitly restart any Pods, it. Understanding Deployment s. If this is your first database deployment, click Build a Database, then click Advanced Configuration Options. A replica set is a core Kubernetes object called ReplicaSet. Stateless applications are those that do not. This is actually happening only for one specific ReplicaSet. For Deployment, ReplicaSet, Replication Controller, only scale, if the number of existing replicas matches. selector to know what Pods it should manage. Its purpose is to maintain the specified number of Pod instances running in a cluster at any given time to prevent users from losing access to their application when a Pod fails or is inaccessible. spec. If you just have a Replicaset with one replica and no PodDisruptionBudget specified, the pod will be terminated and a new pod will be created on other nodes. caret right icon. create a deployment. I guess Deployments and ReplicaSets will. A standalone mongod instance is useful for testing and development. ReplicaSet. yml shown below. ¶ The Advanced Configuration Options section allows you to set MongoDB runtime options for each MongoDB process in your deployment. Use the kubectl apply command to create the ReplicaSet by applying the manifest:DaemonSet is a controller similar to ReplicaSet that ensures that the pod runs on all the nodes of the cluster. This will tell you what "owns" the pod. Create a file called. 下記の図のようにDeploymentはReplicaSetを生成・管理し、ReplicaSetはPodを生成・管理します。 This way the deployment will be marked as paused and won't be reconciled by the controller. ReplicaSet is the next-generation ReplicationController that supports the new set-based label selector. If you want to create Deployment you must specify this properties. The number of replicas in this ReplicaSet is specified in the Deployment YAML file. After you destroy the ReplicaSet, the running Pods will also get deleted. template. StatefulSets. 14, 2023 Updated Nov. 2. # deployment name and namespace deployment_name=mydeployment deployment_ns=mynamespace # get replica set identifier for deployment dep_rs=$. However, more sophisticated selection rules are possible, as. Here’s a basic tutorial on how to scale an application using the vim terminal editor and adjusting the replicas property in a ReplicaSet configuration file: Step 1: Open the ReplicaSet configuration file in the vim terminal editor: $ vim my-rs. ; Click Select a Startup Option and select the configuration option. StatefulSet is the workload API object used to manage stateful applications. It scales up 7 because 25% of 25 (your maxSurge value) is 6. It manages the deployment of. In Kubernetes, a HorizontalPodAutoscaler automatically updates a workload resource (such as a Deployment or StatefulSet), with the aim of automatically scaling the workload to match demand. Objectives Create an nginx deployment. Deployment and replicaset id are same only pod id is different than previous pod. Deleting the Pod will kick in the current deployment configuration to be applied by Kubernetes to restart and redeploy the Pod. yaml and you see that replicaset is not deleted - try to kubectl get replicaset xxxxxxx -o json and same for at least 1 pod in this replicaset. It was shortly discussed in the Kubernetes: running metrics-server in AWS EKS for a Kubernetes Pod AutoScaler post, now let’s go deeper to check. . To create a deployment, you can use the kubectl apply or kubectl create commands. Note: In Kubernetes, Deployments don’t manage Pods directly. Say we have d. Reload to refresh your session. replicas field. Of the data bearing nodes, one and only one member is deemed the primary node, while the other nodes are deemed secondary nodes. Deployment provides you the capabilities to upgrade your applications smoothly using rolling updates, undo changes, pause, and resume changes as required. 現時点で、Deployment では、問題の発生時の最後に正常にデプロイされた ReplicaSet への自動ロールバックをサポートしていません。 トリガー Deployment の場合、デプロイメントの Pod テンプレートに変更があるたびに新しいロールアウトが自動的にトリガーさ. replicas field. Now that we have learned about ReplicaSet and Deployment, let’s summarize their key differences: Abstraction level: A Deployment is a higher-level abstraction that. Even though the new replica set is created. A Replicaset is a K8s object, a set of Pod templates that describe a set of Pod replicas. The deployment process for Deployments is driven by a controller loop, in contrast to DeploymentConfigs which use deployer pods for every new rollout. Despite both controllers being instrumental in managing high-availability. In the simplest case, a deployment just creates a new replication. yaml file of helm) to any number. Both are related to the limited control that deployments provide over how an application runs: Lack of granular control. Deployment sử dụng ReplicaSet để quản lý các Pod. Kubernetes allows the implementation of HPA both as a controller and an API resource. of pods as mentioned in the yaml file. Kubernetes marks a Deployment as complete when it has the following characteristics:Relationship between Deployment and ReplicaSet in kubernetes. Deploy ReplicaSet. deployment; replicaset; statefulset; job; cronjobs; Deleting resources matching a label. Using electromagnetic waves to flummox and follow smarter weapons has become a critical part of the cat-and-mouse game between Ukraine and Russia. A pod is the smallest unit of deployment in Kubernetes, consisting of one or more containers that share resources and networks. The straightforward way to achieve this is to create a service object that exposes the deployment. 롤링업데이트, 배포 중단, 롤백이 가능합니다. 1. »A replica set is a group of MongoDB deployments that maintain the same data set. Walaupun ReplicaSet dapat digunakan secara independen, seringkali ReplicaSet digunakan oleh Deployments sebagai mekanisme untuk mengorkestrasi pembuatan,. In other words, a ReplicationController makes sure that a pod or a. Behind the scenes, Kubernetes stored numbers of old ReplicaSet so that you can switch to any Replicaset anytime. However, a Deployment is a higher-level. apps and replicaset. Deployment creates ReplicaSet with the number of replicas=3. Comment un ReplicaSet fonctionne Un ReplicaSet est défini avec des champs, incluant un selecteur qui spécifie comment. To create a ClusterIP service (default), use the following command: $ kubectl expose deployment nginx-deployment –name my-nginx-service –port 8080 –target-port=80. Notice that the name of the ReplicaSet is always formatted as [DEPLOYMENT-NAME]-[RANDOM-STRING]. ConclusionThough the Deployment is more suitable than the ReplicaSet, this answer focuses on ReplicaSet over Pod cause the question is between the Pod and ReplicaSet. When you create a Deployment, a ReplicaSet resource is created underneath. Reading the documents it is not clear if the default behaviour should. From kubernetes terminology you can delete any component with below pattern. yml deployment. The ReplicaSet uses a pod template with the app: web-app label, and the pod specification includes a container named web using the nginx image with specified resource limits and requests. For any of the mentioned triggers, the Deployment controller will do a Deployment sync. Method 2: Configuring a MongoDB Replica Set for Deployment and Testing. Data Directory. To specify a port to connect to on localhost, you can use either: A connection string with the chosen port. So first I created a replicaset named rs. Kubernetes has emerged as the de facto standard for container orchestration. With deployment you should be able to do rolling upgrade or rollback. ReplicaSet có số lượng pod mong muốn (DESIRED) là 10, và số lượng Pod hiện tại (CURRENT) là 10. It specifies the application's life cycle, including the pods assigned to the application. However, more sophisticated selection rules are possible, as. A Deployment's Status does not match with what the corresponding ReplicaSet/Pods are showing. It creates a replica of 4 busybox pods. Note-: Giving each pod its own required identity makes the difference between stateful and deployment. We also covered hands-on Lab 14 , Lab 15 , Lab 16 , Lab 17 Lab 22 & Lab 24 out of our 30+ extensive labs. If you are connected to your self-hosted MongoDB Enterprise or MongoDB Community deployment, run db. 9) is a Kubernetes resource used to manage stateful applications. A Deployment is a higher-level resource meant for deploying applications and updating them declaratively, instead of doing it through a ReplicationController or a ReplicaSet, which are both considered lower. ReplicaSets are the smart way to. When you create a Deployment in Kubernetes, a ReplicaSet is created automatically. Nếu có bất kỳ sự cố nào xảy ra và các Pod bị lỗi. El Deployment está escalando su ReplicaSet más nuevo. Kubectl Scale use cases. New pods become available. When to use a ReplicaSet. Actually, you will notice that the only change between declaring a Deployment and a ReplicaSet is the kind Note: A Deployment that configures a ReplicaSet is now the recommended way to set up replication. By default, 10 old ReplicaSets will be kept, however its ideal value depends on the frequency and stability of new Deployments. Without it, ReplicaSet might create new pods when existing pods are deleted. A Deployment allows you to create a newer revision of a ReplicaSet and then migrate existing pods from a previous ReplicaSet into the new revision. Hay nuevos Pods disponibles y listos (listo por lo menos MinReadySeconds). これまで、Pod、ReplicaSetの動作を確認してきましたので、今回はDeploymentの動作を確認します。 Deploymentは、ReplicaSet、Podの上位概念で、以下のような関係になります。 Deploymentの作成 yamlファイルの作成とapply. Here you see that when you first created the Deployment, it created a ReplicaSet (nginx-deployment-2035384211) and scaled it up to 3 replicas directly. Declarative config management. . tier=backend. A. Step 4: Viewing live updates from the cluster. Related content: read our guide to Kubernetes Persistent Volumes. @HunzlaSheikh When you run kubectl delete -f render. Check if there are any finalizers which block delition. but the problem is i need to clean all old deployment and replica set once new version deployed successfully. The ReplicaSet ensures that the desired number of replicas (copies) are running at all times by creating or deleting Pods as needed. In your terminal, change to the directory where you saved the deployment file, and run: $ kubectl apply -f The above command will create the deployment with two pods. e. Deployment resources within Kubernetes have simplified container deployments, and they are one of the most used Kubernetes resources. Actually, you will notice that the only change between declaring a Deployment and a. kubectl delete <component type> <name> <-n namespace>. Let's say if your deployment had 4 replicas. The desired replica of the old. 2. So, for example if we need our ReplicaSet to manage all pods with the label role=webserver, the controller will search for any pod with that label. The Deployment is scaling up its newest ReplicaSet. kind: Deployment name: php-apache minReplicas: 1 maxReplicas: 10 targetCPUUtilizationPercentage: 50. While ReplicaSets can be used independently, today they're mainly used by Deployments as a mechanism to orchestrate Pod creation, deletion and updates. What might be used instead is the imperative option of kubectl create deployment. yml. Kubernetes provides a guarantee that the established Pod order will be respected. You signed in with another tab or window. List the nodes on your cluster: kubectl get nodes. spec. An example output is as follows. The standard replica set deployment for a production system is a three-member replica set. You can use the delete command to delete an object from a cluster: delete <type>/<name>. Whenever we create a new deployment, K8s triggers a Rollout. affinity. reason: NewReplicaSetAvailable message: >- ReplicaSet "integrated-repository-webapp-d69879c5f" has successfully progressed. When we create a deployment it create a replica set and number of pods (that we gave in replicas ). When a Deployment is changed, the previous ReplicaSet needs to. Create a deployment configuration. Declarative way, edit this line in your Yaml file: replicas: 2. This option is mandatory as we aren’t updating the value of the spec. Important. the pod template specified inside the Deployment's yaml file, and the value of the replica field (which defines the size of the pod set). Creating Your First Deployment. Under the hood, Deployment creates a ReplicaSet which in turn creates pods on our cluster. Specifically, we define the desired state of the application using DeploymentSpec. # Create the MySQL StatefulSetusing deployment we can undo deployment, pause deployment, resume deployment. The kubectl scale command is used to change the number of running replicas inside Kubernetes deployment, replica set, replication controller, and stateful set objects. Create a Deployment to rollout a ReplicaSet. An ordinary Deployment or ReplicaSet could not implement this workflow. While ReplicaSets can be used independently, today it’s mainly used by Deployments as a mechanism to orchestrate. If a user-facing Pod fails or becomes overworked, the Deployment allocates work to a Pod from the ReplicaSet to maintain responsiveness. It uses a template to describe what each Pod must contain. 25, so it rounds up to 7. The standard replica set deployment for a production system is a three-member replica set. However, more sophisticated selection rules are possible, as. restart で、ロールアウトを再実行します。. how to refer ReplicaSet in deployment? 0. Accordingly Replicaset is owned by Deployment Alternatives to ReplicaSet: Deployment (recommended). The deployment controller extends the ReplicaSet Controller and is responsible for rolling out software updates when you create pods with deployment resources and update them with new versions of your software. kubectl label nodes <node> <key>=<value>. StatefulSet is the workload API object used to manage stateful applications. Alternativas al ReplicaSet Deployment (recomendado) UnDeployment es un objeto que puede poseer ReplicaSets y actualizar a estos y a sus Pods mediante actualizaciones en línea declarativas en el servidor. A ReplicaSet is a process that runs multiple instances of a Pod and keeps the specified number of Pods constant. This last is. A Deployment is a higher-level resource meant for deploying applications and updating them declaratively, instead of doing it through a ReplicationController or a ReplicaSet, which are both considered lower-level concepts. Deployment 是 kubernetes 中最常用的资源对象，为 ReplicaSet 和 Pod 的创建提供了一种声明. Rolling deployment is the default strategy in Kubernetes. However, more sophisticated selection rules are possible, as. kubernetes deployment 컨트롤러는 지속적으로 배포된 인스턴스들을. When you create a deployment, the template is needed for creationupdate of ReplicaSet and PODs, in this case, they need to match the selector, otherwise you would end up with orphan. For the value. The kubectl set env command updates the environment variables for a Kubernetes resource, such as a Deployment, ReplicaSet, or StatefulSet. yaml. spec. ReplicaSet ：同じ仕様のPodを期待する数に維持するオブジェクト. The Deployment is scaling down an existing ReplicaSet. ReplicaSet then fulfills its purpose by creating and deleting Pods as needed to reach the desired number. The configuration of each Deployment revision is stored in its ReplicaSets; therefore, once an old ReplicaSet is deleted, you lose the ability to rollback to that revision of Deployment. 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. revisionHistoryLimit is an optional field that specifies the number of old ReplicaSets to retain to allow rollback. 🕸️Simple Difference Between ReplicaSet and Deployment. Existing package dependencies might be removed if required. Use this procedure to deploy a new replica set managed by Cloud. Create a new OpenShift Container Platform project. Like deployment replicaset cant rollout or rollback to different version of application nor maintain any revisions for the same. // +optional CollisionCount *int32 `json:"collisionCount,omitempty" protobuf:"varint,8,opt,name=collisionCount"` }It seems a deployment has gotten stuck. a deployment (called web in this example), a replicaset (web-65899c769f), a pod (web-65899c769f-dhtdx). Once your Pods have started, you can scale the StatefulSet up or down without risking the destruction of the MySQL primary node. Deploymentはローリングアップデートやロールバックといったデプロイ管理の仕組みを提供するものです。 Deployment の仕組み. Published Nov. The United States and China, the world’s two largest climate polluters, have agreed to jointly tackle. The kubectl create deployment command causes Kubernetes to create a Deployment named monolith on. Kubernetes HorizontalPodAutoscaler automatically scales Kubernetes Pods under ReplicationController, Deployment, or ReplicaSet controllers basing on its CPU, memory, or other metrics. To scale up set --replicas=1 (or any other required number) accordingly. 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. 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. This item links to a third party project or product that is not part of Kubernetes itself. When you increase the replica count, to scale up your service. Every pod owned by a ReplicaSet will get the unique "metadata. When you install your database nodes, always use clean and minimal VMs. A ReplicaSet is a set of identical backup Pods maintained on the backend side to ensure a Pod is always available. 8 user guide shows how to create a deployment in. Deployment is a higher-level API object that updates its underlying Replica Sets and their Pods in a similar fashion as kubectl rolling-update. spec section is similar to the ReplicaSet’s, defining the pod template for each replica. During the research on how to deploy MongoDB on Kubernetes cluster I found two approaches: 1- Vanilla Manifests. kubectl rollout restart deployment myapp deployment. By evaluating pod. Entonces, continuó escalando el nuevo y el viejo ReplicaSet con la misma. yaml --namespace=custom-namespace. It seems to support some of the same features of a ReplicationController - scale up/down and auto restart, but it's not clear if it supports rolling upgrades or autoscale. We can also roll out an app via a ReplicaSet but a deployment resource give us a declarative application update. kubectl delete deploy inginx-deploy. ReplicaSets can be used independently. Deployment is a supervisor for pods. In other words, a ReplicationController makes sure that a pod or a homogeneous set of pods is always up and available. ReplicaSetは指定された数のPodを複製し、実行してくれる。. replicas of the Deployment and / or StatefulSet be removed from their manifest (s). I am creating a deployment using this yaml file. Create or generate a Kubernetes Operator ConfigMap. 2. A deployment creates replicaset and replicaset in turn creates pod. Vì vậy, ta nên sử dụng Deployment Container thay vì sử dụng trực tiếp ReplicaSet trừ khi ta có nhu cầu đặc biệt cần phối hợp. Now, let’s scale them down by specifying the –replicas=1 option to the command: $ kubectl scale -. How Deployment uses spec. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to. This is where you specify how the ReplicaSet should. For more. The Replica Set Controller detect the change then according to the number of replica, create Pod objects. ReplicaSet. Deployment is nothing but the higher-level of abstraction for Replicaset. A Deployment creates Replicaset. replicas field. The interesting thing here is that when there is pod that actually matches the selector labels of the RS without. Puedes monitorizar el progreso de un Deployment usando el comando kubectl rollout status. Terraform by-default uses Deployment for ReplicaSet. This annotation is set by Kubernetes. Deployment Strategy. The old ReplicaSet is scaled down as the new one is scaled up, ensuring that the. The Deployment is scaling down its older ReplicaSet(s). Overview. The goal is to ensure that the applications running in the pods have enough resources and do not experience downtime, even if one or more pods fail. It maintains a ReplicaSet with the desired configuration, with some additional configuration for managing updates and. It will create Deployment object in imperative way. Kubernetes deployments manage stateless services running on your cluster (as opposed to for example StatefulSets which manage stateful services). In the case of a Job, this option is ignored. yaml, this will instruct Kubernetes to scale the current number of Pods to the value of. StatefulSets. kubectl get replicaset. ReplicaSet は、管理すべき Pod の集合・一覧を Label によってフィルタリング・識別し、クラスタ内で動作する Pod を追跡するのに. A ReplicaSet’s purpose is to run a specified number of pods at any given time. selector field defines how the created ReplicaSet finds which Pods to manage. Create a Deployment to rollout a ReplicaSet. Deployment is an abstraction over ReplicaSet. @Jonas I did. This setting corresponds to the _id replica configuration option. Example: kubectl delete deployment hello-world -n mynamespace. A ReplicaSet uses labels to match the pods that it will manage. Officially, there is no limit to how high this can be set but, of course, you have to keep in mind the underlying resources of your Kubernetes cluster. As mentioned in the previous section, there are two ways to define or configure a ReplicaSet; directly through a YAML configuration file or through a deployment. yaml After some time, we modify d. StatefulSet is also a Controller but unlike Deployments, it doesn’t create ReplicaSet rather itself. Tuy nhiên, Deployment Controller, 1 khái niệm ở mức cao hơn sẽ quản lý các ReplicaSet và cung cấp các cập nhật cho pod kèm theo các tính năng hữu ích khác. spec. This old ReplicaSet tries to spin up a pod and it stays in pending because of the resource limitations on the node. As mentioned in the previous section, there are two ways to define or configure a ReplicaSet; directly through a YAML configuration file or through a deployment. ReplicaSet is the next-generation ReplicationController that supports the new set-based label selector. The ReplicaSet data includes the number of desired replicas, the selector to identify which pods are being controlled, and the template for the pod. When you revise a deployment, a ReplicaSet is created that. You can define a deployment to create a ReplicaSet or to remove deployments and adopt all their resources with new deployments. To add an option: Click Add Advanced Options. By default, it ensures that at most 125% of the desired number of Pods are up (25% max surge). 9) is a Kubernetes resource used to manage stateful applications. Replica Count: The number of replicas (pods) the controller should. As you stated the deployment was created but no pods were, what we need is the output of the replicaset to figure out why it wasn't able to create the pods, can you do a kubectl get replicaset and then find the one corresponding to you deployment and then kubectl describe replicaset <replicaset_name>updatedReplicas - the number of pods reachable by deployment, that match the spec template. You cannot create any Deployment (RelicaSet) without container properties description (images, volumes etc. There is this thing called inter pod anti affinity that does exactly this. Avoid complexity when possible, but let your application requirements dictate the architecture. The Kubernetes docs explicitly suggest using a deployment rather than a ReplicaSet directly. kubernetes. Deleting ReplicaSet. However if you change labels and. Previously, we have learned how to roll back to an old version in case of an issue with a current deployment. For example, you define how many replicas ( pods) of your app you want to run in the. The Deployment creates a ReplicaSet that creates three replicated Pods, indicated by the . one may never need to manipulate ReplicaSet objects when using a Deployment)Alternatives to ReplicaSet Deployment (recommended) Deployment is an object which can own ReplicaSets and update them and their Pods via declarative, server-side rolling updates. The . There are many private registries in use. However, a Deployment is a higher-level concept that manages ReplicaSets and provides declarative updates to pods along with a lot of other useful features. Remove a member from a replica set. A replica set contains several data bearing nodes and optionally one arbiter node. Kubernetes events are a resource type in Kubernetes that are automatically created when other resources have state changes, errors, or other messages that should be broadcast to the system. When an HPA is enabled, it is recommended that the value of spec. selector field defines how the created ReplicaSet finds which Pods to manage. readyReplicas - the number of pods that are reachable from deployment through all the replicas. Deployment is recommended for application services. When you update a Deployment, it will update the ReplicaSet, which in turn updates the Pods. The standard replica set deployment for a production system is a three-member replica set. 15340e5036f2fec1. As per the name, ReplicaSet is used for managing the replicas. In this case, you select a label that is defined in the Pod template (app: nginx). It increases the pods one by one while the old replicaset decreases the pods one by one. # deployment name and namespace deployment_name=mydeployment deployment_ns=mynamespace # get replica set identifier for deployment dep_rs=$ (kubectl describe. Alternatives to ReplicaSet Deployment (recommended) Deployment is an object which can own ReplicaSets and update them and their Pods via declarative, server-side rolling updates. Un ReplicaSet (ensemble de réplicas en français) a pour but de maintenir un ensemble stable de Pods à un moment donné. io/revision: "4" This will exist on both the deployment and the replicaset. The Deployment creates a ReplicaSet that creates three replicated Pods, indicated by the . The deployment process for Deployments is driven by a controller loop, in contrast to DeploymentConfigs which use deployer pods for every new rollout. I put an example on my gitlab page that you can also find in Kubernetes Blog. , creating a Deployment will automatically create a ReplicaSet based on the Deployment’s pod template and desired number of replicas Updating the Deployment’s pod template causes it to temporarily create a new ReplicaSet and “move” Pods from the old ReplicaSet to the new one at a. We are using Kubernetes 1. Frequently, when deploying a specific pod-template, the deployment fails to create a successful replicaset and no instance is created. apps/kuard created $ kubectl get deployment,replicaset,pod --show-labels NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE LABELS deployment. The ReplicaSet is responsible to manage the Pods. For example, If you create a deployment with 1 replica, it will check that the desired state of ReplicaSet. Does any one have implemented blue green deployment while cleaning the old stuff?The solution(s) : Use a StatefulSet, ReplicaSet or DaemonSet to ensure the Pod creation after a Node failure. From the table, you see one Kubernetes deployment. Therefore, we recommend using Deployments instead of directly using ReplicaSets, unless you require custom update orchestration or don't require updates at. Deployment with name backend is created indicated by metadata. A ReplicaSet, as the name implies, is a set of replicas (Pods) maintained with their Revision history. ReplicaSet: StatefulSet is also a Controller but unlike Deployments, it doesn’t create ReplicaSet rather itself creates the Pod with a unique naming convention. In the MongoDB spec section, the type of deployment was defined as ReplicaSet with the desired number of replicas of 3.