Repository navigation
Discuss PostgreSQL yaml #6
Description
This is the proposal for the YAML of the CRD.
I have a first doubt, defining a standard like an ingress, or a pvc resource, we can be really conservative and keep only the 1% of commonality between different implementation or try to abstract 99% of the underlying implementation. I think our main challenge here is to find the right balance between these 2 extreme.
I think the current yaml is at one end of the spectrum, trying to abstract everything, I'd love your comments about that.
And please mention the high level keys you'd like to get rid of, because you think they don't make sense at all, and the reasoning behind.
I'd love to make this alpha in 1.16.
Activity
davisford commentedon Jul 16, 2019
@pierreozoux i just came from using the Couchbase Kubernetes operator, now trying to use this one. I much prefer a CRD to define the DB cluster as opposed to having to use a CLI client. We aim to put everything in Terraform. I've converted all of your scripts + yaml to Terraform so we can create the operator now. I was hoping you would define a CRD for the db cluster, too. It looks like you are going that route. Here is the Couchbase CRD in case you want to have a look. Obviously much different in many respects, but some things may be similar. I'll try to provide more feedback as we get deeper into the pg operator and CRD.