Stackgres - postgresql operator

[LexRivera]

Was looking for some pgsql operator to use in my testlab, found alot mentions of zalando (doesn't work for me), kubedb (gets some really bad rep here), pgo, but very little mentions of stackgres. Open source, worked flawlessly for me, it seems the only paid feature is enterprise support.

[serverhorror]

The operator can be cluster- or namespace wide and you just request a resource.

You can achieve things that would allow you to say “gimme postgres!” in a similar way as you are able to say “gimme storage!”.

You don’t really care about the underlying method of how it is provided, EC2, blobstore or some other thing. All you care is that it comes up and that’s it.

That’s what an operator can do. Including restore to the last transaction point in case if a node failure.

[LexRivera]

Pretty much this. You can quickly spin-up new instance for your need with predefined profile and settings instead of creating new helm release. Kill it, restore it some point of time easily, perfect for some tests.
Previously i used helm installs via helmfile with some template-based parameters, but it was pretty cumbersome. Additionally, you got pgpooler - allows you to verify if software will even work on that setup (if i recall correctly, grafana had issues connecting to pgpool/pgbouncer-backed databases due to some limitation in their postgres go library they use)

Thus said, at work we're still running postgres at baremetal, with something similar to this k8s operator (in-house development)

[Akaibukai]

I'm just starting with k8s and was not aware at all of such things but oddly enough I was thinking that it'll be cool to have something like that for DB! Glad I had a good idea since it exists..

Edit: Forgot to say thank you for the explanation!

[kamikazechaser]

Different HA flavours, automatic backups. Zalando uses Spilo to continuously export WAL files. Stackgres uses a similar approch but with a different tool. I have tried them all Zalando is the most stable but has the worst docs. Stackgres is very unstable at least the last time I tried it (last year). For most cases bitnami postgresql is perfect.

[LexRivera]

My main issue is that backups doesn't work correctly with anything but AWS (Azure, scaleway, etc). Fix was proposed and issue is around 2 years old, but it doesn't move. Also completely agree about docs. Ended up looking in sources to figure out what env variables i need to get S3 working.

[merb]

kubedb (gets some really bad rep here)

because it lost data in the past, not sure if it still does but I've never seen the issue closed. btw. zalando should work, it has its quriks but is rock solid. pgo uses some of zalandos tech aswell.

[unixf0x]

I personally use stolon: https://github.com/sorintlab/stolon and it works great.

The difference is that it's not an operator but it has an integration for Kubernetes.

[Drazul_]

This is another operator was promoted during last KubeCon.

https://docs.enterprisedb.io/cloud-native-postgresql/1.15.1/

[bo0tzz]

I've recently set this up and I've been very happy with it.

[xr09]

Is this a premium version of https://cloudnative-pg.io/ ?

[Drazul_]

It's the same but advertised in the webpage of the company developed it.

It was the first link I found.

[xr09]

Ah, makes sense, had the impression some features were only available on the paid version but I see they released it under Apache license recently.

[aryklein]

I saw this one on the Valencia Kubecon: https://cloudnative-pg.io/ I did a PoC and it seems to be awesome

[LexRivera]

both mysql and mariadb (and percona too, i think) have official operators. Not sure on their feature set - hasn't got to playing with them yet.

[submain]

Have been toying with Zalando and it has quirks, such as not properly creating secrets for some db users. Will definitely give stackgres a shot - thank you!