An open-source MySQL alternative for running database on Kubernetes

This seems interesting but this passage from the readme is a red flag to me:<p>&gt;You do not have to learn database tuning. KubeBlocks can leverage storage and computing resources to achieve optimal database performance.<p>No one has ever delivered on this pipe dream.

So now instead of debugging database performance issues you also have to debug the third party database orchestration middleware and the Kubernetes cluster workloads.

If this is supposed to be used in production as open source, then I am a little surprised that it&#x27;s under AGPL 3.0, especially given there&#x27;s no mention of commercial version.

&gt;An open-source MySQL alternative for running database on Kubernetes<p>Very confusing title. It made me think it&#x27;s some kind of open-source database compatible with MySQL (and kind of implies that MySQL isn&#x27;t open-source).<p>It seems it&#x27;s a tool for managing databases in Kubernetes.

After looking at the readme, I&#x27;m still unclear on what kind of product it is - another database operator? In the readme I don&#x27;t see any advantages it has compared to other operators, why not I choose other more mature operators?<p>Are the &quot;Goals&quot; serious? That looks more like empty slogans. Perhaps it would be better to explain in detail what it have actually done and how did it.<p>Furthermore, when can change that misleading title?

I like the message it conveyed &#x27;No need to be a K8s professional&#x27;. That is exactly how I feel after creating a mysql cluster smoothly. I tried oracle mysql opertor months earlier, but failed to install it on AWS EKS without knowing why.

This &quot;why you need KubeBlocks&quot; reads like a bunch of pointless marketing speak (quoted below).<p>&quot; &gt;Why you need KubeBlocks When adopting a multi-cloud or hybrid cloud strategy, it is essential to prioritize application portability and use software or services that offer consistent functionality across different infrastructures.&quot;<p>I&#x27;d rather read some concrete examples or use cases.

Is it just me, or are the comments on this post swarming with people that seem to only talk about this particular product. This feels like a borderline coordinated self promotion effort with several new&#x2F;young accounts speaking highly positively in contrast to what seems like some reasonable skepticism of a product.

It looks like this project is for more than just MySQL. Should the title get updated?<p>Also, the `Quick Start` link in the readme goes to a 404.

The animated screenshot looks promising. I&#x27;d like to try it out. What&#x27;s a good way to get SQL dumps inside the cluster? On the overview page there&#x27;s a diagram for production deployment that includes a LoadBalancer for external clients. What Loadbalancer can I use that can proxy the MySQL protocol?

I had been keeping an eye on this project before, and upon checking it out recently, I&#x27;ve noticed many minor improvements. It&#x27;s not just that one operator now supports multiple engines, but the feature experiences of several engines have also gradually become more well-rounded.

I&#x27;m still not sure what is the purpose of this, the README is not clear.

It looks like a fully managed database service alternative. MySQL, PostgreSQL, Redis, MongoDB... all the popular db engines.

There are docs for Postgresql and Kafka, but they do not look as fleshed out. Are those production-ready?

The title is misleading and made me think there was a new open source database.

It seems that this can not only manage databases but also support Kafka and Pulsar.

Like the way you make HA visible in the format of lovely cats.

As we know, although Kubernetes (K8s) can be used to build and deploy various applications, including databases, there are still some challenges and limitations related to databases that cannot be fully addressed. Here are some of these issues:<p>1. Data Consistency: Kubernetes does not directly provide guarantees for data consistency in databases, while databases typically require integrity and consistency of data. This may rely on mechanisms such as database replication, sharding, and transactions to ensure data consistency, rather than solely relying on Kubernetes.<p>2. Data Persistence and Performance: While Kubernetes provides solutions for persistent storage, such as Persistent Volumes (PVs), it may still not fully meet the requirements of high-performance databases, such as large-scale data processing or high-concurrency workloads in relational databases.<p>3. Distributed Deployment and Maintenance of Databases: Distributed databases often require data synchronization and load balancing among different nodes. Kubernetes can provide partial support, such as StatefulSets for managing stateful applications, but the distributed nature and complexity of databases may require additional configuration and management to ensure data consistency and high availability.<p>4. Database Scaling and Fault Recovery: In large-scale applications, databases may need horizontal scaling and fault recovery capabilities. While Kubernetes can dynamically scale and manage containers, scaling and fault recovery at the database level may require more complex configuration and strategies, depending on the specific database engine and architecture.<p>5. Database Backup and Recovery: Backup and recovery are critical tasks in database management. Although Kubernetes provides snapshot and backup functionality, the backup and recovery process for databases may require additional considerations, such as handling transaction logs and ensuring data consistency.<p>While Kubernetes provides some convenience and abstraction layers for building databases, the above issues indicate that specialized database architectures and solutions are still required for specific database requirements and scenarios to meet the needs of data consistency, persistence, performance, and scalability.<p>I have been downloaded kubeblocks and running it on local k8s, AWS EKS, GCP GKE, it can create many kind of databases very quickly. Also, kubeblocks includes day2 operations keep me free from tons of DBA jobs.<p>I will keep trying kubeblocks. When the day it meet the needs of data consistency, persistence, performance, and scalability, go production and take a good sleep.