Open ravina-c opened 2 weeks ago
Let's start small first and have maybe only observedGeneration (because it was also mentioned in #1698) and lastTransitionTime - I would also need to look up which status fields K8s currently recommends. I think, showing status of child resources could also be useful. But let's start small first and also be backwards compatible with the current status field.
Sure, I am working on the code changes, will submit a draft PR soon.
/assign
Hi, Currently the status field of the
postgresql
CR looks something like:I'd like to propose following changes to the status:
post these changes, the status field of the
postgresql
CR would look something like this:Along with this, I am proposing to add scale subresource in the CRD of
postgresql
as well, which would use some of the fields proposed above, and then this scale subresource can be further used by external systems to scale or monitor the CR. This scale subresource would look something like this: