No observedGeneration in Customer Resource status

Hello community,

Some context

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
• Where do you run it - cloud or metal? Kubernetes or OpenShift? OVH Managed Kubernetes
• Are you running Postgres Operator in production? no
• Type of issue? feature request

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

Start by reproducing the kubectl command against a PostgreSQL Custom Resource and inspect how the Customer Resource status is defined and updated. Trace the status reconciliation path to determine where the processed generation should be represented. Done means the status exposes observedGeneration consistently after updates, with coverage for the reported version-change scenario.