Skip to content

Commit 6b565ec

Browse files
committed
add pod generation to docs
1 parent edf6a64 commit 6b565ec

File tree

1 file changed

+7
-3
lines changed
  • content/en/docs/concepts/workloads/pods

1 file changed

+7
-3
lines changed

Diff for: content/en/docs/concepts/workloads/pods/_index.md

+7-3
Original file line numberDiff line numberDiff line change
@@ -226,9 +226,13 @@ like
226226
have some limitations:
227227

228228
- Most of the metadata about a Pod is immutable. For example, you cannot
229-
change the `namespace`, `name`, `uid`, or `creationTimestamp` fields;
230-
the `generation` field is unique. It only accepts updates that increment the
231-
field's current value.
229+
change the `namespace`, `name`, `uid`, or `creationTimestamp` fields.
230+
- The `generation` field is unique. It will be automatically set by the
231+
system such that new pods have a `generation` of 1, and every update to
232+
mutable fields in the pod's spec will increment the `generation` by 1. If the
233+
alpha feature gate PodObservedGenerationTracking is set, the
234+
pod's `status.observedGeneration` will reflect the `metadata.generation` of
235+
the pod at the point that the pod status is being reported.
232236
- If the `metadata.deletionTimestamp` is set, no new entry can be added to the
233237
`metadata.finalizers` list.
234238
- Pod updates may not change fields other than `spec.containers[*].image`,

0 commit comments

Comments
 (0)