Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add pod generation to docs #49906

Draft
wants to merge 1 commit into
base: dev-1.33
Choose a base branch
from
+7 −3
Draft

add pod generation to docs #49906

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions content/en/docs/concepts/workloads/pods/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,9 +226,13 @@ like
have some limitations:

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