[FG:PodObservedGenerationTracking] Kubelet sets pod status.observedGeneration when updating the pod status#130352
Conversation
|
Skipping CI for Draft Pull Request. |
status.observedGenerationstatus.observedGeneration when updating the pod status
status.observedGeneration when updating the pod statusstatus.observedGeneration when updating the pod status
2571a7b to
a0d3203
Compare
|
/assign @tallclair |
|
/lgtm For Kubelet changes. I think you still need a scheduler review. |
|
LGTM label has been added. DetailsGit tree hash: f80f6f34380051872e8814bcba06a59e53d38b3c |
|
/approve |
| // Owner: sig-node | ||
| // Marks tests that require a cluster with PodObservedGenerationTracking | ||
| PodObservedGenerationTracking = framework.WithFeature(framework.ValidFeatures.Add("PodObservedGenerationTracking")) | ||
|
|
There was a problem hiding this comment.
This might not be needed, depending on whether #130580 gets merged.
There was a problem hiding this comment.
ack, I'll keep an eye on it. Thanks!
|
/remove-sig instrumentation |
|
Hello @natasha41575 Friendly reminder that code freeze is starting at 02:00 UTC Friday 21st March 2025 (about 2 weeks from now), and while there is still time, we want to ensure that each PR has a chance to be merged on time. Please make sure the PR has both lgtm and approved labels before the code freeze. Thanks! |
|
/triage accepted |
|
/retest |
1 similar comment
|
/retest |
|
@liggitt tests are all passing after the rebase! |
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 44108f946e4060fab857aa9067110174575a7a02 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpbetz, liggitt, natasha41575, tallclair The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR updates the kubelet to set
pod.status.observedGenerationas described in https://kep.k8s.io/5067.Which issue(s) this PR fixes:
Pod generation KEP: https://kep.k8s.io/5067
Special notes for your reviewer:
In the KEP, it was decided that for
conditions.ObservedGenerationneed only to be added to the API for alpha; actual implementation of them is only required for graduation for beta.Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: