Introduce custom Jekyll tags for better glossary integration

This commit is contained in:
Jessica Yao
2017-10-17 18:23:17 -07:00
committed by Andrew Chen
parent 8ff083b0f3
commit 46d9cbe5ae
51 changed files with 546 additions and 197 deletions
+4 -4
View File
@@ -1,5 +1,6 @@
id: statefulset
name: StatefulSet
full-link: /docs/concepts/workloads/controllers/statefulset/
aka:
- PetSet
related:
@@ -9,10 +10,9 @@ tags:
- core-object
- workload
- storage
short-description: |
Manages the deployment and scaling of a set of [Pods](/docs/concepts/workloads/pods/pod), *and provides guarantees about the ordering and uniqueness* of these Pods.
short-description: >
Manages the deployment and scaling of a set of {% glossary_tooltip text="Pods" term_id="pod" %}, *and provides guarantees about the ordering and uniqueness* of these Pods.
long-description: |
Like a [Deployment](/docs/concepts/workloads/controllers/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.
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.
A StatefulSet operates under the same pattern as any other Controller. You define your desired state in a StatefulSet *object*, and the StatefulSet *controller* makes any necessary updates to get there from the current state.