Allow the operator and postgresql cluster to be deployed independent of each other. #130
Description
Is your feature request related to a problem? Please describe.
The postgres-operator package currently enables configuring a single postgres cluster after it sets up the operator. If you have multiple databases (gitlab, keycloak, etc), they all have to go in the same postgres cluster. It would be nice if there were a separate standalone postgres package that configured the postgresql custom resource and did all of the same secret management, networking, extension enabling, etc that the operator config chart supports doing for a single postgres cluster. This package could be deployed multiple times to configure multiple postgres clusters in different namespaces.
Describe the solution you'd like
- Given a state
- When an action is taken
- Then something happens
Describe alternatives you've considered
Options are to either make the package optionally deploy the operator and/or the cluster, support a list of clusters in the values or create a separate postgres package that will allow just the properly configured cr to be deployed.
The most reasonable option it probably to modify the config chart to be more generic and create a separate package internal to this repo to do a standalone database deployment assuming the operator already exists. This should be able to reuse the existing chart with some light conditionals in the template and should be able to be deployed multiple times with the recently added zarf namespaceOverride functionality.
Additional context
Add any other context or screenshots about the feature request here.