Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: KubeDB – Kubernetes-ready production-grade databases

kubedb.com

Post reply on HN
Print view View original

21–30 of 36 posts

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#21

Post by sciurus »

newaccoutnas wrote: post #10
striking wrote: post #6

Earlier quoted context omitted.

The Postgres clustering advertised here[0] seems like a great reason to me. 0: https://kubedb.com/docs/0.9.0/guides/postgres/

How does that compare to something like CitusDB I wonder?

It looks like a standard single r/w master + multiple r/o slave topology with the addition of their own leader election. I'd want to understand how the latter works and how it is tested very well before I'd trust it.

https://kubedb.com/docs/0.9.0/guides/postgres/clustering/ha_...

https://github.com/kubedb/postgres/blob/master/pkg/leader_el...

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#22

Post by bogomipz »

bbromhead wrote: post #13
bogomipz wrote: post #11

Does anyone know if there are plans for a Cassandra operator? Or is running Cassandra on K8S just not recommended?

https://github.com/instaclustr/cassandra-operator :)

Thanks for the link, do you have experience or feedback on using this?

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#23

Post by snug »

tn890 wrote: post #2

Can someone explain to me why I'd run this over a StatefulSet of whatever software I want to deploy? I've been skimming the docs and can't find a good reason TBH.

StatefulSets are not "smart." You would need to manage and configure any kind of replications, leader elections, backups, etc. Operators like KubeDB make this easier to manage, and can make stateful applications more "Cloud Native"

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#24

Post by atombender »

dkoston wrote: post #7

Thanks for putting this together, it's great to have something that covers backups and restore and operation all in one package. I'd recommend updating the name to be more descriptive. Anything xDB sounds like it in itself is a database. That's what I was expecting. KubeDBOperator or similar would let us know: it's related to K8s, it has to do with databases, it likely manages deployments with HA/failover/backups. As…

I agree about the confusing naming. They could reverse it: DBKube!

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#27

Post by tamalsaha001 »

wstrange wrote: post #12

Really nice work! Question: How are snapshots implemented? Are you using k8s native snapshots (which I think are alpha?) or other? EDIT: Looks like snapshots are per db feature: https://github.com/kubedb/project/issues/337 Hopefully Kubedb can leverage K8S snapshots when they mature

Thank you! We are using DB specific tools for taking snapshot. Example, mysqldump for MySQL etc. We are looking into k8s native snapshots for future releases. Here is the tracking issue: https://github.com/kubedb/project/issues/337

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#28

Post by tamalsaha001 »

gigatexal wrote: post #18

No MySQL clustering means no adoption from me for now.

I understand. This is one of primary feature we targeting to suppose in the next quarter. Can you tell me what type of clustering support do you use? Example: Percona, Galera cluster, Vitess ?

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#29

Post by tamalsaha001 »

gigatexal wrote: post #9

Can TLS encryption be used here and does it support encrypting the storage?

Are you talking about TLS encryption for connection url? If so, it is supported for Elasticseach. The others ones are not there yet. Though it might be possible using the available configuration options.

We are also looking to modifying the snapshot option to store encrypted snapshots in future releases.

Re: Show HN: KubeDB – Kubernetes-ready production-grade databases

#30

Post by tamalsaha001 »

xena wrote: post #8

On by default analytics makes me not want to touch this, sorry.

I hear you. The goal of our analytics collection is to know the # of active users of our product. So, we send an event to Google Analytics when a command is run or periodic pings for long running (> 1 hr) commands. You can disable it by setting the flag --enable-analytics=false. You can see further discussion on this matter here: https://github.com/cncf/toc/issues/107#issue-311155675

Lastly, everything is open source. So, you are free to read the code and modify and use your modified version if that's what you prefer. xref: https://github.com/kubedb/operator/blob/0.9.0/pkg/cmds/root....

Post reply on HN