Examples of using Replicationcontroller in English and their translations into Indonesian
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Ecclesiastic
A ReplicationController also needs a. spec section.
Check on the status of the ReplicationController using this command.
The ReplicationController can itself have labels(. metadata. labels).
More details about the API object can be found at: ReplicationController API object.
A ReplicationController manages all the pods with labels that match the selector.
If there are too few, the ReplicationController starts more pods.
We will not add scheduling policies(for example,spreading) to the ReplicationController.
If there are too many pods, the ReplicationController terminates the extra pods.
A ReplicationController ensures that a specified number of pod replicas are running at any one time.
When using the REST API or go client library,simply delete the ReplicationController object.
This allows the ReplicationController to be replaced without affecting the running pods.
Also you should not normally create any pods whose labels match this selector,either directly, with another ReplicationController, or with another controller such as Job.
ReplicaSet is the next-generation ReplicationController that supports the new set-based label selector.
ReplicationController is often abbreviated to“rc” or“rcs” in discussion, and as a shortcut in kubectl commands.
Similarly, the population of pods that a replicationcontroller should manage is also defined with a label selector.
A ReplicationController delegates local container restarts to some agent on the node(for example, Kubelet or Docker).
As with all other Kubernetes config, a ReplicationController needs apiVersion, kind, and metadata fields.
A ReplicationController will never terminate on its own, but it isn't expected to be as long-lived as services.
For this reason, we recommend that you use a ReplicationController even if your application requires only a single pod.
Use a ReplicationController, ReplicaSet, or Deployment for Pods that are not expected to terminate, for example, web servers.
In addition to required fields for a Pod, a pod template in a ReplicationController must specify appropriate labels and an appropriate restart policy.
The ReplicationController makes it easy to scale the number of replicas up or down, either manually or by an auto-scaling control agent, by simply updating the replicas field.
The two serve the same purpose, and behave similarly, except that a ReplicationController does not support set-based selector requirements as described in the labels user guide.
Note: You should not create other Pods whose labels match this selector, either directly, by creating another Deployment,or by creating another controller such as a ReplicaSet or a ReplicationController.
In other words, a ReplicationController makes sure that a pod or a homogeneous set of pods is always up and available.
Using a PD on a Pod controlled by a ReplicationController will fail unless the PD is read-only or the replica count is 0 or 1.
Kubectl will scale the ReplicationController to zero and wait for it to delete each pod before deleting the ReplicationController itself.
As mentioned above, whether you have 1 pod you want to keep running,or 1000, a ReplicationController will ensure that the specified number of pods exists, even in the event of node failure or pod termination(for example, due to an action by another control agent).
Pods created by a ReplicationController are intended to be fungible and semantically identical, though their configurations may become heterogeneous over time.
Unlike in the case where a user directly created pods, a ReplicationController replaces pods that are deleted or terminated for any reason, such as in the case of node failure or disruptive node maintenance, such as a kernel upgrade.