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 use the Cloud native postgres operator for my personal deployments of anything with a postgres cluster requirement. I can't be the only one who does, as it offers TLS, backups (on demand and scheduled including wal archives and works with local S3 instances), restores, and other scaling features.
The operator helm chart is pretty solid, but when we first started using this operator, it didn't yet have the cloudnative-pg/charts cluster helm chart available, meaning we rolled our own, small-hack/cloudnative-pg-cluster-chart. Now that it's out, although still in development, perhaps we integrate it as an optional way to deploy postgresql with this chart?
I use the Cloud native postgres operator for my personal deployments of anything with a postgres cluster requirement. I can't be the only one who does, as it offers TLS, backups (on demand and scheduled including wal archives and works with local S3 instances), restores, and other scaling features.
The operator helm chart is pretty solid, but when we first started using this operator, it didn't yet have the cloudnative-pg/charts cluster helm chart available, meaning we rolled our own, small-hack/cloudnative-pg-cluster-chart. Now that it's out, although still in development, perhaps we integrate it as an optional way to deploy postgresql with this chart?
Potential blockers
Context
Open to any suggestions or feelings on the matter :)
The text was updated successfully, but these errors were encountered: