Skip to content

Document how pod observedGeneration can be useful with InPlacePodVerticalScaling #51248

Open
@natasha41575

Description

@natasha41575

In v1.33, we introduced status.observedGeneration and conditions[].observedGeneration fields in pods that tells you which podspec has been ack'd by the kubelet.

The primary motivation for this new field was in the context of in-place-pod-resize. With both IPPR and observedGeneration enabled:

  • status.observedGeneration lets you know the latest resize request that has been ack'd by the kubelet
  • conditions[].observedGeneration on the PodResizePending and PodResizeInProgress conditions lets you know which resize request is currently being reflected by that condition.

We should add this to the documentation on k/website, probably here: https://kubernetes.io/docs/tasks/configure-pod-container/resize-container-resources/.

/kind documentation
/triage accepted
/assign

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.kind/documentationCategorizes issue or PR as related to documentation.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions