KEP-5067: correct details about mirror pod implementation #5225
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One-line PR description:
Correcting the details about how generation / observedGeneration are handled for mirror pods. Based on discussion in the kep and implementation prs we aren't doing anything special, so generation and observedGeneration on a mirror pod will always be 1.
Discussion comments:
status.observedGeneration
when updating the pod status kubernetes#130352 (comment)/sig node
/assign @mrunalp