Merge pull request #17782 from sftim/20191123_reword_pod_overview
Reword Pod concept (overview page)
This commit is contained in:
@@ -4,7 +4,7 @@ id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
|
||||
A repeating task (a Job) that runs on a regular schedule.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
||||
@@ -4,7 +4,7 @@ id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
An API object that manages a replicated application.
|
||||
Manages a replicated application on your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
@@ -12,9 +12,10 @@ tags:
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
An API object that manages a replicated application.
|
||||
An API object that manages a replicated application, typically by running Pods with no local state.
|
||||
|
||||
<!--more-->
|
||||
|
||||
Each replica is represented by a {{< glossary_tooltip term_id="pod" >}}, and the Pods are distributed among the {{< glossary_tooltip text="nodes" term_id="node" >}} of a cluster.
|
||||
|
||||
Each replica is represented by a {{< glossary_tooltip term_id="pod" >}}, and the Pods are distributed among the
|
||||
{{< glossary_tooltip text="nodes" term_id="node" >}} of a cluster.
|
||||
For workloads that do require local state, consider using a {{< glossary_tooltip term_id="StatefulSet" >}}.
|
||||
|
||||
@@ -4,7 +4,7 @@ id: pod
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/pods/pod-overview/
|
||||
short_description: >
|
||||
The smallest and simplest Kubernetes object. A Pod represents a set of running containers on your cluster.
|
||||
A Pod represents a set of running containers in your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
||||
@@ -4,7 +4,7 @@ id: statefulset
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/statefulset/
|
||||
short_description: >
|
||||
Manages the deployment and scaling of a set of Pods, *and provides guarantees about the ordering and uniqueness* of these Pods.
|
||||
Manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
@@ -18,3 +18,5 @@ tags:
|
||||
<!--more-->
|
||||
|
||||
Like a {{< glossary_tooltip term_id="deployment" >}}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods. These pods are created from the same spec, but are not interchangeable: each has a persistent identifier that it maintains across any rescheduling.
|
||||
|
||||
If you want to use storage volumes to provide persistence for your workload, you can use a StatefulSet as part of the solution. Although individual Pods in a StatefulSet are susceptible to failure, the persistent Pod identifiers make it easier to match existing volumes to the new Pods that replace any that have failed.
|
||||
|
||||
Reference in New Issue
Block a user