Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by dkoston on Monday December 17, 2018 @11:03AM
(#18699756)
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 other commenters noted as well, you have to click at least 3 times before you understand what the software does based on the above link. Linking to the home page rather than the welcome would be a better choice for those not currently familiar with your project.
Either way, appreciate all the work that went into this project!
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by weberc2 on Monday December 17, 2018 @01:11PM
(#18700740)
I thought the front page was quite helpful for figuring out what the product was (once I realized the HN link pointed to the documentation page and not the front page).
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by hosh on Monday December 17, 2018 @01:36PM
(#18700938)
Same here. I didn't know what the elevator pitch is.
On the other hand, when I looked it up, this sounds like a really interesting project, exposing DBs as application resources.
There is something I remember from CloudFoundry (though I don't know if this is working anymore), and that is with adding in dependencies like databases into the specs for an application.
I kinda wonder if that could be done: add an annotation on a pod spec which the operator can look for and set up the database (if it doesn't exist) and provision credentials.
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by noahdesu on Monday December 17, 2018 @10:48AM
(#18699649)
This seems to serve a purpose similar to Rook [0] for deploying distributed (or non-distributed) storage systems, including database. For example, Rook can deploy CockroachDB and also Ceph, which would have a lot of the same challenges as deploying some of the databases supported by KubeDB.
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by manigandham on Sunday December 30, 2018 @10:54AM
(#18789702)
Rook stretching to databases looks like a random tangent trying to do everything at once. The project should focus on being a solid distributed storage provider first and let users run databases themselves on those volumes. It's especially strange since these databases already have their own storage replication and would be duplicating work.
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by tie_ on Tuesday December 18, 2018 @02:55PM
(#18709936)
Kudos for the interesting approach! I do think that DB management on Kubernetes belongs to operators, and maintaining a collection of them would be great.
This being said, you should not be using TPR, but rather CRDs (see https://coreos.com/blog/custom-resource-kubernetes-v17). The welcome video is not really convincing either - condensing it to an animated gif would make it much more attractive imho.
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by snug on Monday December 17, 2018 @02:08PM
(#18701232)
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 datab...
by sciurus on Monday December 17, 2018 @01:45PM
(#18701009)
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.
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by tamalsaha001 on Monday December 17, 2018 @03:48PM
(#18702054)
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 datab...
by tamalsaha001 on Monday December 17, 2018 @03:53PM
(#18702115)
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 datab...
by tamalsaha001 on Monday December 17, 2018 @03:50PM
(#18702078)
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 datab...
by tamalsaha001 on Monday December 17, 2018 @03:58PM
(#18702163)
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
Re:Show HN: KubeDB – Kubernetes-ready production-grade datab...
by merlinsbrain on Monday December 17, 2018 @04:11PM
(#18702255)
I’ve never understood why people are willing to give all their data to Facebook or any other hosted product which collects data, but are unhappy when open source projects collect anonymized metrics to improve the product.
In this case there’s a flag advertized to turn it off, hopefully someone will be reading the docs before it’s deployed in production?
Do you think AWS and GCP don’t collect metrics?
Happy to hear the other side, my knee-jerk reaction is also usually “you don’t need this data”, but when thinking as an owner, i would find this data invaluable to improve the product, getting funding (please donate, there are X millions of users) etc.
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 other commenters noted as well, you have to click at least 3 times before you understand what the software does based on the above link. Linking to the home page rather than the welcome would be a better choice for those not currently familiar with your project.
Either way, appreciate all the work that went into this project!
Other than that, looks cool.
On the other hand, when I looked it up, this sounds like a really interesting project, exposing DBs as application resources.
There is something I remember from CloudFoundry (though I don't know if this is working anymore), and that is with adding in dependencies like databases into the specs for an application.
I kinda wonder if that could be done: add an annotation on a pod spec which the operator can look for and set up the database (if it doesn't exist) and provision credentials.
[0]: https://rook.io
disclaimer: red hat employee working some on rook.
This being said, you should not be using TPR, but rather CRDs (see https://coreos.com/blog/custom-resource-kubernetes-v17). The welcome video is not really convincing either - condensing it to an animated gif would make it much more attractive imho.
I've been skimming the docs and can't find a good reason TBH.
0: https://kubedb.com/docs/0.9.0/guides/postgres/
https://kubedb.com/docs/0.9.0/guides/postgres/clustering/ha_...
https://github.com/kubedb/postgres/blob/master/pkg/leader_el...
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
something like: https://kubernetes.io/docs/reference/generated/kubernetes-ap...
We are also looking to modifying the snapshot option to store encrypted snapshots in future releases.
But just Percona clustering would do.
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....
In this case there’s a flag advertized to turn it off, hopefully someone will be reading the docs before it’s deployed in production?
Do you think AWS and GCP don’t collect metrics?
Happy to hear the other side, my knee-jerk reaction is also usually “you don’t need this data”, but when thinking as an owner, i would find this data invaluable to improve the product, getting funding (please donate, there are X millions of users) etc.