base on KubeBlocks is an open-source control plane software that runs and manages databases, message queues and other stateful applications on K8s. # Welcome to the KubeBlocks project! [](https://kubeblocks.io) [](https://bestpractices.coreinfrastructure.org/projects/7544) [](https://github.com/apecloud/kubeblocks/actions/workflows/cicd-push.yml) [](https://github.com/apecloud/kubeblocks/actions/workflows/codeql.yml) [](https://github.com/apecloud/kubeblocks/actions/workflows/release-version.yml) [](https://github.com/apecloud/kubeblocks/releases/latest) [](/LICENSE) [](https://goreportcard.com/report/github.com/apecloud/kubeblocks) [](https://hub.docker.com/r/apecloud/kubeblocks) [](https://codecov.io/gh/apecloud/kubeblocks)  [](https://artifacthub.io/packages/search?repo=kubeblocks)  ## Motivation If you are a developer using multiple types of databases in your application and are considering deploying both your application and databases on K8s for cost or efficiency reasons, you need to find suitable operators for each database. Learning so many different operators and their APIs introduces a significant learning curve and time costs, not to mention the effort required to maintain them. KubeBlocks uses a unified set of APIs (CRDs) and code to manage various databases on K8s. For example, we can use the `Cluster` resource to create a PostgreSQL cluster, a Redis cluster, or a Kafka cluster. This abstraction and unified API allow us to further use a single set of operator code to manage multiple types of databases, as well as handle day-2 operations, theoretically extending to any type of database engine. ## What is KubeBlocks KubeBlocks is an open-source control plane software that runs and manages multiple popular database engines on K8s through a unified set of code and APIs. The core of KubeBlocks is a K8s operator, which defines a set of CRDs to abstract the common attributes of various database engines and uses these abstractions to manage the engine's lifecycle and day-2 operations. KubeBlocks manages various types of stateful engines, including RDBMSs (MySQL, PostgreSQL), Caches(Redis), NoSQLs (MongoDB), MQs(Kafka, Pulsar), vector databases(Milvus, Qdrant, Weaviate), and data warehouses(ClickHouse, ElasticSearch, OpenSearch, Doris, StarRocks). Adding a new engine to KubeBlocks can be achieved by writing a KubeBlocks Addon. The community is actively integrating more types of engines into KubeBlocks, and it currently supports 35 types of engines. The name KubeBlocks is inspired by Kubernetes and LEGO blocks, signifying that through the KubeBlocks API, adding, composing and managing database engines on K8s can be easy, standard and productive, like playing with LEGO blocks. ### Why you need KubeBlocks KubeBlocks integrates the most popular database engines and provides rich management functions, along with declarative APIs, in various environments. KubeBlocks offers the following benefits: * Production-level KubeBlocks has already been adopted by large internet companies, private clouds, the financial industry including banks and securities firms, telecom industry, the automotive industry, and SaaS software providers. * Reliability KubeBlocks supports the integration of various mature high-availability best practices, such as Orchestrator, Patroni, and Sentinel. KubeBlocks also supports full backups, continuous backups, and point-in-time recovery (PITR). * Ease of use KubeBlocks not only provides a YAML-based API but also offers an interactive `kbcli` tool to further simplify usage as a complement to `kubectl`. For example, you can install KubeBlocks and launch a playground environment on a desktop or cloud with a single command. * Observability KubeBlocks collects monitoring metrics from rich data sources, integrates with the Prometheus stack, and provides insightful Grafana templates. In addition, troubleshooting tools such as slow logs are also provided. * Extensibility KubeBlocks provides the addon mechanism for integrating new engines. So it can be extended to run the databases your project needs. ### Goals - Smoothing the learning curve of managing various databases on K8s - Exploring standard APIs for managing databases on Kubernetes - Being open and cloud-neutral, as well as engine-neutral ### Key features - Supports various databases, including MySQL, PostgreSQL, Redis, MongoDB, Kafka, Clickhouse, ElasticSearch and more - Provides production-level performance, resilience, and observability - Simplifies day-2 operations, such as upgrading, scaling, monitoring, backup, and restore - Contains a powerful and intuitive command line tool - Be compatible with AWS, GCP, Azure, Alibaba Cloud and more CSP ## Get started with KubeBlocks [Quick Start](https://kubeblocks.io/docs/preview/user_docs/try-out-on-playground/try-kubeblocks-on-your-laptop) shows you the quickest way to get started with KubeBlocks. ## Resources [API Reference](https://kubeblocks.io/docs/release-0.8/developer_docs/api-reference/cluster) [How to write a KubeBlocks Addon?](https://kubeblocks.io/docs/release-0.8/developer_docs/integration/how-to-add-an-add-on) [KubeBlocks: Cloud-Native Data Infrastructure for Kubernetes](https://www.youtube.com/watch?v=KNwpG51Whzg) (A Video made by Viktor Farcic) [Dashboard Demo](https://console.kubeblocks.io/) ## KubeBlocks at KubeCon KubeCon 2024 in HongKong from 21-23 August 2024: [How to Manage Database Clusters Without a Dedicated Operator, By Shanshan Ying, ApeCloud & Shun Ding, China Mobile Cloud](https://kccncossaidevchn2024.sched.com/event/1eYYL/how-to-manage-database-clusters-without-a-dedicated-operator-nanoxi-operatorzha-fa-lia-zhong-shi-shanshan-ying-apecloud-shun-ding-china-mobile-cloud) KubeCon 2024 in HongKong from 21-23 August 2024: [KuaiShou's 100% Resource Utilization Boost: 100K Redis Migration from Bare Metal to Kubernetes, By XueQiang Wu, ApeCloud & YuXing Liu, Kuaishou](https://kccncossaidevchn2024.sched.com/event/1eYat/kuaishous-100-resource-utilization-boost-100k-redis-migration-from-bare-metal-to-kubernetes-zha-100pian-zhi-yi-daeplie-hui-zhe-100k-rediskubernetes-xueqiang-wu-apecloud-yuxing-liu-kuaishou) ## Community If you have any questions, you can reach out to us through: - KubeBlocks [Slack Channel](https://join.slack.com/t/kubeblocks/shared_invite/zt-2pjob3ezp-FzaZM7NId~Tbzp6PYNbOzQ) - KubeBlocks Github [Discussions](https://github.com/apecloud/kubeblocks/discussions) - KubeBlocks Wechat Account: <img src=".\docs\img\wechat-assistant.jpg" alt="wechat" width="100" height="100"> You can also follow us on: - [Twitter](https://x.com/KubeBlocks) - [LinkedIn](https://www.linkedin.com/company/apecloud-ptd-ltd/) ## Contributing to KubeBlocks Your contributions are welcomed and appreciated. - See the [Contributor Guide](docs/CONTRIBUTING.md) for details on typical contribution workflows. - See the [Developer Guide](docs%2F00%20-%20index.md) to get started with building and developing. ## Report Vulnerability We consider security as the top priority issue. If you find any security issues, please [Report a security vulnerability](https://github.com/apecloud/kubeblocks/security/advisories/new) issue. ## License KubeBlocks is under the GNU Affero General Public License v3.0. See the [LICENSE](./LICENSE) file for details.", Assign "at most 3 tags" to the expected json: {"id":"1349","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"