PostgreSQL 14 on Kubernetes

I always thought it's better to host distributed database, like Cockroachdb and Yugabytedb, in multiple kubernetes clusters. Just in case one of the cluster goes down.

Re: PostgreSQL 14 on Kubernetes

#6

Post by mikesabbagh » Wed, Oct 06, 2021, 4:27 AM UTC

cant think of a scenario where you need to query multiple databases in same query! Nice demo, but deploying it all in a cluster is distracting. Maybe do your next demo with docker-compose!

Re: PostgreSQL 14 on Kubernetes

#7

Post by longcommonname » Wed, Oct 06, 2021, 4:41 AM UTC

voidfunc wrote: post #4

leetrout wrote: post #3

Why would i want to run my database in k8s?

Why not? Its just a workload scheduler. Some of us have competent ops teams

What level of competency do you need to run dbs?

Re: PostgreSQL 14 on Kubernetes

#8

Post by ryanisnan » Wed, Oct 06, 2021, 4:42 AM UTC

voidfunc wrote: post #4

leetrout wrote: post #3

Why would i want to run my database in k8s?

Why not? Its just a workload scheduler. Some of us have competent ops teams

I think while true, this is an incredibly reductive take on what Kubernetes really is.

Re: PostgreSQL 14 on Kubernetes

#9

Post by darthrupert » Wed, Oct 06, 2021, 4:49 AM UTC

longcommonname wrote: post #7

voidfunc wrote: post #4

Earlier quoted context omitted.

Why not? Its just a workload scheduler. Some of us have competent ops teams

What level of competency do you need to run dbs?

Poorly? Almost none.

Well? Significant.

Re: PostgreSQL 14 on Kubernetes

#10

Post by manigandham » Wed, Oct 06, 2021, 5:03 AM UTC

mpwala wrote: post #5

I always thought it's better to host distributed database, like Cockroachdb and Yugabytedb, in multiple kubernetes clusters. Just in case one of the cluster goes down.

A K8S cluster is already designed to be highly available and self healing. Stretching across clusters is usually a special case of scaling across datacenters/regions and brings a lot more overhead and complexity.