Kubernetes Workload Resources: Difference between revisions
| Line 16: | Line 16: | ||
<font color=darkkhaki>Describe the relationship between pod, deployment, ReplicaSet and workload resources. Which one are controllers and which are not?</font> | <font color=darkkhaki>Describe the relationship between pod, deployment, ReplicaSet and workload resources. Which one are controllers and which are not?</font> | ||
=To Distribute= | =To Distribute= | ||
====ReplicationController==== | ====ReplicationController==== | ||
{{Internal|Kubernetes ReplicationController|ReplicationController}} | {{Internal|Kubernetes ReplicationController|ReplicationController}} | ||
Revision as of 00:13, 13 July 2023
Internal
Overview
Workload resources exist to create and manage Pods, which should not usually be created directly. Various workload resources implement different pod operational patterns. The pod-managing resources described here are some times referred to as higher-level pod controllers or "templated controllers".
From the simplest to the most complex ones, the workload resources are Jobs, CronJobs, ReplicaSets, Deployments, DaemonSets and StatefulSets.
Jobs and CronJobs are aimed mainly at running individual pods, as part of one-off or repeated executions.
A ReplicaSet is a workload resource aimed at maintaining a stable set of replica Pods running at any given time, guaranteeing the availability of a specified number of identical Pods.
The Deployment is a resource that delegates to a ReplicaSet.
These controllers are part of and supervised by the controller manager.
Describe the relationship between pod, deployment, ReplicaSet and workload resources. Which one are controllers and which are not?