whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reword pod template concept information

Browse Source 
- Mention address family in pod concept
  Preparing to reword this for IPv4 / IPv6 dual stack
- Fix capitalization for “cluster”, “container” and “volume”
  These are not resources you manage via kubectl
- Harmonize short descriptions for workload objects in glossary
- Expand definition of StatefulSet
- Use tooltip for “kubelet”
- Revise pod template text
- Revise What's Next section
This commit is contained in:
Tim Bannister
2019-11-23 18:54:30 +00:00
parent 91da908de0
commit 068f8e4c69
5 changed files with 57 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/glossary/statefulset.md
+3 -1
View File
@@ -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&#58; 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.