apiVersion: extensions/v1beta1 kind: ReplicaSet metadata: name: frontend # these labels can be applied automatically # from the labels in the pod template if not set # labels: # app: guestbook # tier: frontend spec: # this replicas value is default # modify it according to your case replicas: 3 # selector can be applied automatically # from the. To add node selectors to an existing pod, add a node selector to the controlling object for that pod, such as a ReplicaSet object, DaemonSet object, StatefulSet object, Deployment object, or DeploymentConfig object. 1. a number of replicas indicating how many Pods it should be maintaining. In the simplest case, a deployment just creates a new replication controller and lets it start up pods. It default to 1 if it was not. busybox default to the docker command sh which opens a shell and because the container is neither not started with a terminal attached the sh process exits immediatly after container startup leading to the CrashLoopBackOff Status of your pods. Kubernetes is only told what it can work with by the apiVersion and kind parameters, which should never be different. If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Seperti objek API Kubernetes lainnya, sebuah ReplicaSet membutuhkan field apiVersion, kind, dan metadata. yaml": no matches for apps/, Kind=ReplicaSet. name that you specified in your Ops Manager resource definition. 1. Table 7. Hopefully, the theoretical concept of Replicaset is clear; now, let’s quickly jump to some practical examples. After creating a NodePort Service Type I am getting errors that the local dns names cannot be resolved. It will be composed by the number of. The example below creates a ReplicaSet using a YAML file:. Deployments control the updating of its underlying entities. MongoDBCommunity metadata: name: example-mongodb spec: members: 3 type: ReplicaSet version: "4. below is the yaml file: kind: type of object trying to be created. The operator creates a config (and updates it) for the agent’s sidecar container responsible for configuring MongoDB in each Pod. youbudong Update go. The example 9-1 describing a simple ReplicaSet seems to be invalid, when you try to create the ReplicaSet the k8s responds: no matches for kind "ReplicaSet" in version "v1beta1" You can use `apiVersion: apps/v1` instead of `extensions/v1beta1` but you still need to inform the `spec. allowWatchBookmarks requests watch events with type "BOOKMARK". Add docker. 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. Just following the documentation examples here:As per Describe Pod command listing, your Container inside the Pod has been already completed with exit code 0, which states about successful completion without any errors/problems, but the life cycle for the Pod was very short. The manifest file for a deployment looks similar to a replicaset but the kind is deployment. It is responsible for monitoring the health of the. observed state, so it. As per the name, ReplicaSet is used for managing the replicas of our pods. Both of them ensure that a specified number of pod replicas are running at any given time. It is an open-source, general purpose, document-based, distributed NoSQL database server that is especially popular with JavaScript projects. apiVersion: apps/v1 kind: ReplicaSet # this defines to create the object of replication type metadata: name: nginx spec: replicas: 3 # the element defines the desired number of pods selector:. I couldn't figure, whether the issue is with my code or api resources. ReplicaSetHorizons feature does not work without using SSL/TLS certificates. apiVersion: extensions/v1beta1 kind: ReplicaSet metadata: name: rep-with-vol2 spec:. yaml. net core web application that gets some information from MongoDB replica set but from time to time I'm getting a timeout errors. ReplicaSet is a Kubernetes object that ensures that a specified number of replicas of a pod are running at any given time. Each rollback updates the revision of the Deployment. Once our ReplicaSet template gets ready. mongodbResourceRef. Kubernetes の実践. kubectl create -f kubia-replicaset. Deploy a MongoDBMultiCluster Resource. Try using one envFrom with multiple entries under it as below: - name: integration-app image: my-container-image envFrom: - secretRef: name: intercom-secret - secretRef: name: paypal-secret - secretRef: name: postgres-secret - secretRef: name: redis-secret. In this example: A Deployment named nginx-deployment is created, indicated by the . This included ReplicationController, ReplicaSet, StatefulSet, DaemonSet, and Deployment. Query parameters; Parameter Type Description; allowWatchBookmarks. We also define a number of labels through which we can identify it. Here is an example ConfigMap object using the output from ssh-keyscan above: The argocd-ssh-known-hosts-cm ConfigMap will be mounted as a volume at the mount path /app/config/ssh in the pods of argocd-server and argocd-repo-server. In Kubernetes, Admission Controllers enforce policies on objects during create, update, and delete operations. string. The replicaSet controller ensure that three pods are running at any point of time in the cluster. Then you need to define the other. kubectl delete pods <pod> --grace-period=0 --force. My 2 cents on the subject, don't mix POD status with Container status (it's true that they're correlated). The job of a ReplicaSet is to maintain a stable number of pod copies or replicas. 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. # deployment name and namespace deployment_name=mydeployment deployment_ns=mynamespace # get replica set identifier for deployment dep_rs=$ (kubectl describe. template. The basic format is <server_name> <keytype> <base64-encoded_key>, one entry per line. A ReplicaSet’s purpose is to maintain a stable set of replica. We will use the following YAML file to create our ReplicaSet. This will cause the deployment controller to create a ReplicaSet, with one replica (which means it will only start one pod). Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. The Deployment creates a ReplicaSet that creates three replicated Pods, indicated by the. com. In Kubernetes, Admission Controllers enforce policies on objects during create, update, and delete operations. In this example: A Deployment named nginx-deployment is created, indicated by the . cat replicaset. yaml’, and we will be submitting this. La version de l'API apps/v1beta2 est obsolète. Then you are at the right place. In this case, it's set to 3. There's an example at the bottom of this blog post by. replicas. ReplicaSetCondition describes the state of a replica set at a certain point. apiVersion. If you’re using any version of kubectl <= 1. spec: replicas: 3. The continue option should be set when retrieving more results from the server. The label selector is the core grouping primitive in Kubernetes. Here, this replicaset will monitor Pods with the label tier: frontend. Here’s an example: kubectl get pods -l app=nginx NAME READY STATUS RESTARTS AGE nginx-pod 1/1 Running 0 2m56s. If even after these commands the pod is stuck on Unknown state, use the following command to remove the pod from the cluster:A ReplicaSet (RS) is a Kubernetes object that ensures there is always a stable set of running pods for a specific workload. ownerReferences field, to tell which resource owns the current Pod(s). A ReplicaSet is a Kubernetes object that runs multiple instances of a pod and ensures a certain number of pods is running at all times. The name of a ReplicaSet must be a valid DNS subdomain value, but this can produce unexpected In kubernetes 1. A ReplicaSet ensures that a specified number of pod replicas are running at any given time. StatefulSet (stable-GA in k8s v1. replicas 来指定要同时运行的 Pod 个数。 ReplicaSet 创建、删除 Pod 以与此值匹配。 A ReplicaSet is defined with fields, including a selector that specifies how to identify Pods it can acquire, a numberof replicas indicating how many Pods it should be maintaining, and a pod template specifying the data of. I tried it with several different files and also the samples from the K8s documentation, but all result in this failure. This is where replicasets come into play. ReplicaSet 管理所有标签匹配与标签选择器的 Pod。. Deployment および DeploymentConfig について. selector: # Pods label should be defined in ReplicaSet label selector matchLabels: app: myapp2 template: metadata: name: myapp2-pod labels: app: myapp2 # Atleast 1 Pod label should match with. metadata. 3. Table 10. The above. For ReplicaSets, the kind is always a ReplicaSet. To begin with, create an Express app first. 1 ReplicaSets in a nutshellA ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. MySQL 5. - apiVersion: apps/v1 kind: ReplicaSet name: router-default-66d5cf9464 uid: d81dd094-da26-11e9-a48a-128e7edf0312 controller: true blockOwnerDeletion: true. ReplicaSet is the next-generation ReplicationController that supports the new set-based label selector. Provide details and share your research! But avoid. When you create a ReplicaSet, you are essentially telling Kubernetes that you want a specific pod replicated x amount of times. Add a comment. yaml": no matches for apps/, Kind=ReplicaSet. yaml apiVersion: autoscaling/v1 kind: HorizontalPodAutoscaler metadata: name: web-app-scaler spec: scaleTargetRef: kind: ReplicaSet name: web-app. This is the file for the ReplicaSet: apiVersion: apps/v1 kind: ReplicaSet metadata: name: myapp-replicaset labels: app: myapp spec: selector: matchLabels: env: production name: nginx replicas: 3 template: metadata: name: nginx. string. For ReplicaSets, the kind is always just. copy. Labels are the properties attached to each item/object. containers field. For example, in a StatefulSet deployment called “statest”, the pod “statest-0” will be created first, then “statest-1”, and so on. Query parameters; Parameter Type Description; allowWatchBookmarks. Creating a Kubernetes ReplicaSet. When you instantiate a ReplicaSet, it creates the desired number of replicas using the pod template. In a nutshell label selectors depend on labels to select a group of resources such as pods. Create a ReplicaSet. Nifty! Now that we’ve covered the first two fields we can move on to metadata:. 0 8m54s pod/metrics-server-694d47d564-cc4m2 1/1 Running 0 8m54s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/metrics-server ClusterIP 10. yaml": no matches for apps/, Kind=ReplicaSet . A pod is the smallest unit of deployment in Kubernetes, and it usually…My minikube version: v1. 9 版本中，API. io/master:}, that the pod didn't tolerate. apiVersion: v1 kind: Pod. labels field to them. ReplicationController can only match a label with a value (As we saw in rs’s example). The config is saved to the Kubernetes Secret. When intercepting a service that has multiple ports, the name of the service port that has been intercepted is also listed. replicas. (kind: ReplicaSet) ReplicaSet (rs) functions are almost identical to ReplicationController. spec can be used such as minReadySeconds, paused and more. template: here we specify the specs of the Pods to be created by this replicaset. DaemonSetは、ReplicaSetの特殊な形のリソースになります。Replicasetは、各Nodeに均等に配置されるものではないが、DaemonSetは各Nodeに確実に1つずつPodを配置します。 そのため、レプリカ数の指定はできなく、1つのNodeに2つのPodを配置することもできません。The alerts and rules keys in the serverFiles group of the values. kind: ReplicaSet; The main difference between replicationController and replicaSet is, the replicaSet requires a field named selector as a child of main spec. I found this trick though till I could find a better way. Besides that, it has a spec that specifies that it should make sure that there is always 3 replicas of pods that match the specified label selector in the cluster. Kubernetes troubleshooting is the process of identifying, diagnosing, and resolving issues in Kubernetes clusters, nodes, pods, or containers. But rs can do complex matching. The spec part is mandatory in the ReplicaSet object. kubectl delete $ (kubectl get all | grep replicaset. 245. We also define a number of labels through which we can identify it. In the future, when we update the current deployment, it will create a new ReplicaSet. A Deployment owns and manages one or more ReplicaSets. When the control plane creates new Pods for a ReplicaSet, the . ReplicaSet is the next-generation ReplicationController that supports the new set-based label selector. Clients should not assume bookmarks are. 3. 2. allowWatchBookmarks requests watch events with type "BOOKMARK". replicas field in the manifest. The prefix/suffix transformer adds a prefix/suffix to the. Cách ReplicaSet hoạt động. How Does The ReplicaSet Manifest Look? APIVersion, kind, and Metadata look like any other object in Kubernetes but the Spec section appear somewhat different from other objects. And Replica Set manages the basic units in Kubernetes - Pods. copy. helm install enterprise-operator mongodb/enterprise-operator --namespace mongodb --create-namespace. 2. See here for an example of how to provide the required configuration for a MongoDB replica set. It is used to make sure that we have a specified number of pod replicas that are always up and running. spec. 16 replicaset was moved to apps/v1 apiVersion from extensions/v1beta1. Here in our case it is ReplicaSet. Replicaset rather than the replication controller is used by other objects like deployment. Then, it’ll gradually move the Pods from the old ReplicaSet to the new one at a controlled rate. template. Openshift Depoyment create replicaset the same with old. While Kubernetes, both natively and through ingress controllers, offers a number of ways to expose a service, we will use the standard Service resource of type LoadBalancer. See morekind: ReplicaSet. Environment: AWS Region: eu-central-1 EKS Platform version: eks. The Deployment creates a ReplicaSet that creates three replicated Pods, indicated by the . Rest all is same as the replication controller. ReplicaSetは指定された数のPodを複製し、実行してくれる。. 9$ kubectl create -f replicasets. list or watch objects of kind ReplicaSet. If you don't already have Octopus. Kubernetes is only told what it can work with by the apiVersion and kind parameters, which should never be different. metadata. . For ReplicaSets, the kind is always a ReplicaSet. As such, it is often used to guarantee the availability of a specified number of identical Pods. apiVersion: apps/v1 kind: Deployment metadata: name: my-nginx labels: app: my-nginx # LABEL-A: <--this label is to manage the deployment itself. metadata: It contains the metadata for the ReplicaSet, such as its name. 1. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. We no do deploy or manual changes. Db. 3. 7 is the version used. What did you expect? Mongodb-agent ready and cluster OKFor ReplicaSets, the kind is always a ReplicaSet. replicas: It specifies the desired number of replicas (pods) to maintain. name of the ReplicaSet is part of the basis for naming those Pods. This name will become the basis for the ReplicaSets and Pods which are created later. 8 user guide shows how to create a deployment in. The selector and matchingLabels is used by the replicaset to monitor other pods as well who have the matching labels. metadata. The ReplicaSet is also responsible for creating and managing pods based on a template specification. Thanks for your response. 8. A ReplicaSet represents a group of Pod replicas (exact copies of a Pod). and you can actually do what you want , just use your pod as here in template spec. (Several days). yaml. 1 Answer. For example :While creating ReplicaSet, I am getting following error: The ReplicaSet "julrs" is invalid: spec. name of the ReplicaSet is part of the basis for naming those Pods. To do this we will write a YAML configuration. Does Kubernetes GET API actually support fieldSelector parameter to query values of array fields?. Below is an example of a. Rollback to an earlier Deployment revision if the current state of the Deployment is not stable. Menulis manifest ReplicaSet. 0. It's a cheap solution but it's not that big an issue either. The . For ReplicaSets, the kind is always a ReplicaSet. metadata. Pour ReplicaSets, l'attribut kind est toujours ReplicaSet. For ReplicaSets, the kind is always a ReplicaSet. Let’s have an example: When you instantiate a ReplicaSet, it creates the desired number of replicas using the pod template. The above RS manifest file uses a ReplicaSet to run three copies of the my-image: latest container image. I found this trick though till I could find a better way. kind: ReplicaSet metadata: name: 1st-replicaset spec: podSelector: matchLabels: app: Web-app replicas: 5. The name of a ReplicaSet must be a valid DNS subdomain value, but this can produce unexpected results for the Pod hostnames. Labels, selectors, and annotations are key concepts in Kubernetes for managing objects. Kubernetes manages the relationship between Pods and Services using Labels and Selectors . I’m a beginner with Kubernetes and YAML. spec. you can type. 4, you should omit the --force option and use: kubectl delete pods <pod> --grace-period=0. Try using one envFrom with multiple entries under it as below: - name: integration-app image: my-container-image envFrom: - secretRef: name: intercom-secret - secretRef: name: paypal-secret - secretRef: name: postgres-secret - secretRef: name: redis-secret. apiVersion: apps/v1 kind: ReplicaSet metadata: name. It's very strange. tier: Backend → We have defined the label tier as backend which creates a matching selector. Below is the YAML I'm using for the deployment . metadata. See here for an example of how to. 1. metadata: data about object at issue. A ReplicaSet is a Kubernetes object that ensures that a specified number of replicas of a pod are running at any given time. You can put in there the configuration you want (for example take inspiration by the blog post you linked) and it will be used by Prometheus to handle the alerts. A ReplicaSet is one of the controllers responsible for keeping a given number of replica Pods running. They are followed by a metadata section with fields such as name, labels, etc. Create a deployment via kubectl run, as shown below. Some possible values are Pod, ReplicaSet, Deployment and it is a CASE SENSITIVE string. metadata. ReplicaSet ensures that defined numbers of pods are running on the cluster at a given time. Deployment. The name of a ReplicaSet must be a valid DNS subdomain value, but this can produce unexpected results for the Pod hostnames. ReplicaSet: It is an object that ensures a specified number of identical pod replicas are running at all times. metadata. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. More broadly defined, Kubernetes troubleshooting also includes effective ongoing management of faults and taking measures to prevent issues in Kubernetes components. . apiVersion and kind specify the API version and resource type, respectively, indicating that this is a ReplicaSet. When you create a ReplicaSet, you are essentially telling Kubernetes that you want a specific pod replicated x amount of times. Use ReplicaSets instead. metadata includes the name for the ReplicaSet, which is "my-replicaset". name of the ReplicaSet is part of the basis for naming those Pods. spec. If one Pod goes down in a ReplicaSet, another will be created to replace it. Phần chính trong định nghĩa đối tượng ReplicaSet nằm trong phần spec với định. 它的主要作用是 确保Pod以你指定的副本数运行 ，即如果有容器异常退出，会自动创建新的 Pod 来替代；而异常多出来的容器也会. As you can see, it uses the apps/v1 API version, the kind is ReplicaSet, and in this case the name is set to hello-world_v1. kind: This specifies the Kubernetes resource type. If the Labels of a. deployment "my-nginx" created. 你可以通过设置 . Trong định nghĩa spec trên thì “kind: ReplicaSet” là tên đối tượng Kubernetes mà chúng ta cần tạo với name và các Label được gán cho đối tượng ReplicaSet này được định nghĩa trong phần metadata. #Get list of Pods kubectl get pods kubectl describe pod <pod-name> # Get list of Pods with Pod IP and Node in which it is running kubectl get pods -o wide Also, the apiVersion of replicaSet is apps/v1. "This integration runtime is being used by the other 23 linked services, they are all working fine. じゃあ、ReplicaSetで十分だから「Deployments」は使うことないのかというと、これは新しいバージョンのアプリをデプロイする時に役に立つ。. string. Query parameters; Parameter Type Description; continue. This entry was posted in Docker, Kubernetes and tagged Cluster, Docker, Docker Swarm, Kubernetes, Orchestrator, Pod, ReplicaSet, Scheduler, Service on December 15, 2017 by Viktor Farcic. Setup KinD. Deployments and Deployment Configurations. metadata. For ReplicaSets, the kind is always a ReplicaSet. Share. This is because when the ReplicaSet creates new Pods, it adds the labels from the spec. Let’s use a ReplicaSet to scale up to five instances of our kuard container. $ kubectl run my - nginx -- image = nginx. I’ve been trying to deploy a ReplicaSet with YAML. Step 1: Create a ReplicaSet with three PODs Step 1. A new ReplicaSet is created and the Deployment manages moving the Pods from the old ReplicaSet to the new one at a controlled rate. replicas: 5 indicates that you want to maintain five replicas of the. I'm trying to deploy mongodb with the kubernetes operator on AWS EKS with EFS for the storage class. replication controllers are deprecated and is not recommended any more. 1: Check that Namespace has not ReplicaSets. The difference comes with the usage of selectors to replicate pods. A ReplicaSet is a Kubernetes controller that keeps a certain number of Pods running at any given time. To manually delete a ReplicaSet, run the following command: kubectl delete rs <ReplicaSet_NAME> --cascade=false Next steps. Pod template: ReplicaSet uses a pod template to create and manage the replicated pods. A ReplicaSet represents a group of Pod replicas (exact copies of a Pod). Most common metadata: name. . Clients should not assume bookmarks are. OwnerReferences[0]. ReplicaSet. The name of a ReplicaSet must be a valid DNS subdomain value, but this can produce unexpected results for the Pod hostnames. These lines are: apiVersion: apps/v1. Kubernetes对象之Pod. Template is not a list ( so you are overwriting the template), instead you just need one template for the pod creation , and inside the pod you will have multiple containers then. name of the ReplicaSet is part of the basis for naming those Pods. The ReplicaSet controller guarantees that a specified number of identical Pods is running at all times. Code. func NewForConfigAndClient (c * rest. Then create a Deployment object by running the following command: 1. 8-eks-7c9bda Webhook Version: How do. Note that we recommend using Deployments instead of directly using Replica Sets, unless you require custom update orchestration or. 在旧版本的Kubernetes中，只有ReplicationController对象。. This is 100% reproducible on update from the. Setting the replicas count to 1 seems to do the trick. By adjusting the value in the manifest and re-applying it, you can alter the number of copies (kubectl apply -f my-manifest. spec. In this case (the example above), we’re creating a ReplicaSet. I found this with trial and error, so this is the diff file. name of the ReplicaSet is part of the basis for naming those Pods. Asking for help, clarification, or responding to other answers. Sorted by: 1. If I run db. Possible values include “Orphan”, “Foreground”, or “Background”. In this blog, I will. boolean. However we also want to delete the replicasets and pods that below to 'our-deployment-name'. By using the command kubectl delete rs <rs name>, where rs name is the name of your ReplicaSet, you can destroy ReplicaSets. The selector is used to identifying the Pods it can acquire. Kubernetes deployment drawbacks. I also can't set the replica set to desire 0 pods, but that might be by design. For this the recommended approach is to use a Deployment, which under the hood create a ReplicaSet. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. spec can be used such as minReadySeconds, paused and more. Additional fields in . Note. Hashes for kubesplit-0. We have n number of different type of objects in Kubernetes, like Pods, ReplicaSet, Deployments, Services, etc. this may be used to filter the deployment based on this label. Mounts: <none> Volumes: <none> Conditions: Type Status Reason ---- ----- ----- Progressing True NewReplicaSetAvailable Available False MinimumReplicasUnavailable ReplicaFailure True FailedCreate OldReplicaSets: <none> NewReplicaSet: integrated-repository-webapp-d69879c5f (0/1 replicas created) Events: Type Reason Age From. Kind: Defines the resource as a ReplicaSet for the Kubernetes API. yaml example for guidance. So the apiVersion of ReplicaSet will be apps/v1. Reading the documents it is not clear if the default behaviour should. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. apiVersion: apps/v1 kind: ReplicaSet metadata: name: frontend labels: app: guestbook tier: frontend; The first two fields are straightforward and constant, so they never change. spec. npm init && npm i express --save. A ReplicaSet is a set of identical backup Pods maintained on the backend side to ensure a Pod is always available. Labels are like tags that identify and categorize Kubernetes objects. That's because two replica sets have two different . This is different from vertical. Use this procedure to create a new replica set in a member Kubernetes cluster in a multi-Kubernetes-cluster deployment. name field. The IP address generated from the Load balancer SVC should be bound to the domain names mentioned in the replicaSetHorizons, for example: mongo-replicaset-0. Extract the pod template hash from the replica set. This is just a replication source instance and one (or more) asynchronous replica: This is the status of the ReplicaSet object in. This setting allows you to provide different DNS settings within the Kubernetes cluster and to the Kubernetes cluster. Here the deployment type is chosen as ReplicaSet using the kind option. The job of a ReplicaSet is to maintain a stable number of Pod copies or replicas. apps values should count 2 available instances. boolean. Assuming that you name the two with different values, the two deployment sets would also spin up isolated pods with same labels. 16 replicaset was moved to apps/v1 apiVersion from extensions/v1beta1. Admission control is fundamental to policy enforcement in Kubernetes. whl; Algorithm Hash digest; SHA256: 94beb3553b2127c97680ad9f14c588b4189d15c286e177e3f70c2dd4b7fa0998: Copy : MD5Deploy CRDs and ReplicaSet. Replace <domain-rs-1>, <domain-rs-2>, and <domain-rs-3> with the external FQDNs of the MongoDB replicaset members. In the case of a Job, update parallelism only if the current parallelism value matches. It manages the deployment and scaling of a set of Pods, and provides guarantee about the ordering and uniqueness of these Pods. name values hence they both have their own isolated resources. Here is the output that Powershell is giving me. also, another suggestion don't use the Replicasets by default Deployment create the Replicaset in the background. ; You can check a Pod's status (which is a. 3-py3-none-any. com, mongo-replicaset-1. It's mainly used by Deployment as a. name of the ReplicaSet is part of the basis for naming those Pods. A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. We will create one . Means that GKE does not recognize ReplicaSet within apiVersion: apps/v1 I checked my cluster (I normally use deployments), pulled my replicaSet and it shows up as: apiVersion: extensions/v1beta1 kind: ReplicaSetThe kind of this object is ReplicaSet; In the metadata part, we define the name by which we can refer to this ReplicaSet. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for. In the simplest case, a. 92. Load 7 more related questions Show fewer related questions Sorted by: Reset to default Know someone who can answer?. In case, these pods go down then this replicaset can use it’s template to replace these pods.