-
Notifications
You must be signed in to change notification settings - Fork 1k
No observedGeneration in Customer Resource status #1698
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.
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
Comments
It's true, that our |
/assign |
@FxKu hi, I wanna give a try. May I take it ? |
@hzliangbin yes, please 😃 You might want to create a PR first with your ideas before going straight into implementation. We need to make sure we stay backwards compatible by keeping the |
Hello @hzliangbin, did you have time to take a look at it ? |
For me, ObservedGeneration field should be enough but we should set it synchronously with PostgresClusterStatus |
Hello community,
Some context
Issue
When retrieving the Custom Resource pg with the command:
kubectl get postgresqls.acid.zalan.do -o=jsonpath='{.items[0].status}'
I get :
{"PostgresClusterStatus":"Running"}
I would have expected to have the field observedGeneration like in many Custom Resources / Resources.
I don't know how to check programmatically that an update on the Custom Resource has been processed without observedGeneration mechanism.
I mean if for example I modify the version of the Postgres and I only check the PostgresClusterStatus value it could be Running but not on the right Postgres version.
The only way I see is using ResourceVersion but it's not really user friendly.
What do you think ?
Thank you,
Thomas
The text was updated successfully, but these errors were encountered: