4 ms·

Deploy a Redis Cluster on Kubernetes within 5 minutes

15 points by michellezzz 2y ago

supersudo 2y ago
kubeblocks? It reminds me a talk this Augest in KubeCon Hongkong
- supersudo 2y ago
  Their joint talk with 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 https://kccncossaidevchn2024.sched.com/event/1eYat/kuaishous...
benterix 2y ago
If you were wondering what this is all about have a look here first: https://kubeblocks.io/docs/preview/user_docs/overview/introduction https://kubeblocks.io/docs/preview/user_docs/overview/introd... Basically Kubeblocks aims to be a universal operator for databases on k8s and they claim they already support ca. 30 db-like projects with a unified API. I wonder if anybody here is using it in production and can comment on it?
- thelastparadise 2y ago
  Me very interested in this too.
- michellezzz 2y ago
  This blog might answer your question. It introduces how Kuaishou, a vibrant short-videos platform, migrated its large-scale Redis cluster to K8s using KubeBlocks.
- AtlasBarfed 2y ago
  Redis is often a cache, so if your persistent data is lost who cares. Not exactly the example I would hope for, in fact it seems duplicitous as a choice. Databases are generally not what k8s is intended for: rapidly scalable stateless servers. There's real concerns with operators I've seen as to all the different conditions (expansions, failover, backups, detailed health checks, persistent disk management, version upgrades, boundary conditions like full disks, and if course encryption headaches). I am not a k8s expert, I was involved with an attempt to migrate Cassandra to k8s and did not like the operator I saw at the time. Every db system has very specific nuances in data storage, io optimization, bandwidth for requests and backups, etc. a one size fits all operator project seems like it will invite trouble.
  - k_roy 2y ago
    > Every db system has very specific nuances in data storage, io optimization, bandwidth for requests and backups, etc. a one size fits all operator project seems like it will invite trouble. And these are all fairly well covered with standard kubernetesisms
    - supersudo 2y ago
      Not a redis guy, but I worked on MySQL for quite a long time. the interesting part in KubeBlocks, in my point of view, is they wrap engine-specific differences in 'Addon' . And I checked their impl for MySQL Addon. I like their idea on hwo to modeling datebase topologies and behaviors. for instence, parameter configurations. seems they have tuned parameters for MySQL replication clusters (e.g. they render parameters w.r.t resources)
theblazehen 2y ago
See also: https://ibm.github.io/operator-for-redis-cluster/ https://ibm.github.io/operator-for-redis-cluster/ We've been using it in production for ~9 months now without any issues, and it handles node failures seamlessly

15 points by michellezzz 2y ago

supersudo 2y ago

kubeblocks? It reminds me a talk this Augest in KubeCon Hongkong

supersudo 2y ago
Their joint talk with 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 https://kccncossaidevchn2024.sched.com/event/1eYat/kuaishous...

benterix 2y ago

If you were wondering what this is all about have a look here first: https://kubeblocks.io/docs/preview/user_docs/overview/introduction https://kubeblocks.io/docs/preview/user_docs/overview/introd... Basically Kubeblocks aims to be a universal operator for databases on k8s and they claim they already support ca. 30 db-like projects with a unified API. I wonder if anybody here is using it in production and can comment on it?

thelastparadise 2y ago
Me very interested in this too.
michellezzz 2y ago
This blog might answer your question. It introduces how Kuaishou, a vibrant short-videos platform, migrated its large-scale Redis cluster to K8s using KubeBlocks.
AtlasBarfed 2y ago
Redis is often a cache, so if your persistent data is lost who cares. Not exactly the example I would hope for, in fact it seems duplicitous as a choice. Databases are generally not what k8s is intended for: rapidly scalable stateless servers. There's real concerns with operators I've seen as to all the different conditions (expansions, failover, backups, detailed health checks, persistent disk management, version upgrades, boundary conditions like full disks, and if course encryption headaches). I am not a k8s expert, I was involved with an attempt to migrate Cassandra to k8s and did not like the operator I saw at the time. Every db system has very specific nuances in data storage, io optimization, bandwidth for requests and backups, etc. a one size fits all operator project seems like it will invite trouble.
- k_roy 2y ago
  > Every db system has very specific nuances in data storage, io optimization, bandwidth for requests and backups, etc. a one size fits all operator project seems like it will invite trouble. And these are all fairly well covered with standard kubernetesisms
  - supersudo 2y ago
    Not a redis guy, but I worked on MySQL for quite a long time. the interesting part in KubeBlocks, in my point of view, is they wrap engine-specific differences in 'Addon' . And I checked their impl for MySQL Addon. I like their idea on hwo to modeling datebase topologies and behaviors. for instence, parameter configurations. seems they have tuned parameters for MySQL replication clusters (e.g. they render parameters w.r.t resources)

theblazehen 2y ago

See also: https://ibm.github.io/operator-for-redis-cluster/ https://ibm.github.io/operator-for-redis-cluster/ We've been using it in production for ~9 months now without any issues, and it handles node failures seamlessly