postgres-operator icon indicating copy to clipboard operation
postgres-operator copied to clipboard

Create official postgres-operator-cluster helm chart

Open whazor opened this issue 2 years ago • 6 comments

A postgres-operator-cluster helm chart would be useful for creating new Postgres instances via helm and via this operator.

This helm chart already exists and is created by the k8s at home community. However, an official chart would be better.

The helm chart could contain extra features like creating teams if wanted by the user.

whazor avatar Apr 11 '22 10:04 whazor

See https://github.com/zalando/postgres-operator/blob/master/docs/quickstart.md#helm-chart and #1812.

ibotty avatar Apr 12 '22 10:04 ibotty

I am proposing a new helm chart besides the existing two, with its soul purpose of creating new clusters. Build around the Cluster manifest.

whazor avatar Apr 12 '22 11:04 whazor

Yeah, I misunderstood. I don't quiet see why that might be useful though, but I am not in charge anyway.

ibotty avatar Apr 12 '22 19:04 ibotty

Maybe I misunderstanding it as well :smiley: The helm chart is there to create the postgres operator deployment. To create Postgres clusters you then submit YAML manifests. Why do it with helm? What's the benefit?

FxKu avatar Apr 13 '22 17:04 FxKu

The reasons I can think of:

  • Helm charts can have dependencies, you can make creating instances dependent on rolling out the operator. In this case you would not get an error about missing CRD's.
  • Certain places have standards with tooling that make deploying software build around Helm, for example helmfile. In companies you might only have the permission to install helm charts as well.
  • I have seen a helm chart for this in my company, but as stated in first post also someone else already created a helm chart already. I am curious if more people are interested in this, or that it might be too niche 😄

whazor avatar Apr 16 '22 19:04 whazor

I agree with @Whazor, having a helm chart to create the CRs is very useful and allows to create dependencies between the helm charts avoiding errors about missing CRD's. For example, in my company we are using Flux, therefore it would be very helpful to have this chart to use in Flux since it will ensure that the operator is installed before installing the CRs. You can see this approach already being followed by several other operators, just two examples:

  • Minio Operator: https://github.com/minio/operator/tree/master/helm
  • Operator Chart
  • Tenant Chart (CR's)
  • Zookeeper Operator: https://github.com/pravega/zookeeper-operator/tree/master/charts
  • Zookeeper Operator
  • Zookeeper (CR's)

We also created one for RabbitMQ since only the chart for the operator is provided. We were already thinking of creating one for this Postgres operator but I will take a look at the one from k8s@home. Thanks @Whazor

jcsf avatar Sep 01 '22 15:09 jcsf