You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to standardize the way we describe PostreSQL instances in kubernetes resources, and make this part of upstream, in alpha for the 1.16 version.
As one PG "operator" provider, I'd love your feedback on this.
As a user of your operator, would you find it useful to have a standard resource definition for PG (the same as ingress or PVCs for instance)?
As a developer of this operator, would you adopt it?
What is the biggest challenge you see in this initiative?
If you think this is valuable for the community as a whole like I do, please comment on the draft here.
Thanks for your valuable time!
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'm trying to standardize the way we describe PostreSQL instances in kubernetes resources, and make this part of upstream, in alpha for the 1.16 version.
As one PG "operator" provider, I'd love your feedback on this.
As a user of your operator, would you find it useful to have a standard resource definition for PG (the same as ingress or PVCs for instance)?
As a developer of this operator, would you adopt it?
What is the biggest challenge you see in this initiative?
If you think this is valuable for the community as a whole like I do, please comment on the draft here.
Thanks for your valuable time!
The text was updated successfully, but these errors were encountered: