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

Jump to bottom

Set observedGeneration in ytsaurus resource status #307

Closed
l0kix2 opened this issue Jul 3, 2024 · 1 comment
Closed

Set observedGeneration in ytsaurus resource status #307

l0kix2 opened this issue Jul 3, 2024 · 1 comment

Comments

@l0kix2
Copy link
Collaborator

l0kix2 commented Jul 3, 2024

To distinguish if the operator already has updated all resources and resource is Running and happy or not yet have received new update.
@l0kix2
Copy link
Collaborator Author

l0kix2 commented Sep 5, 2024

Common idea can be read on the internet, for example:
https://alenkacz.medium.com/kubernetes-operator-best-practices-implementing-observedgeneration-250728868792

To test this we could check that observedGeneration is expected in the simple update scenario e2e

@wilwell wilwell mentioned this issue Sep 6, 2024
Merged
@l0kix2 l0kix2 closed this as completed Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
yt-k8s-operator project
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@l0kix2