I recently discovered a Kubernetes operator named KubeBlocks, which claims it is capable of managing a variety of databases within a Kubernetes environment. I am interested in understanding why many remain skeptical about deploying databases on Kubernetes. What technical or practical obstacles are contributing to this hesitation? Are there concerns about performance, security, or maintenance that need further resolution? Please share additional expertise with us.
im not completely sold either, but i feel critics fear k8s ops complexity plus data loss if misconfigs occur. db setups sometimes need physical servers for untouchable stability, and handling persistence properly is still a pain, in my opinion
Running databases on Kubernetes presents several challenges that are often underestimated. In my experience, managing stateful applications in a dynamic orchestrated environment requires careful configuration of storage and networking. Persistent storage handling, backup operations, and ensuring proper high availability often demand additional manual intervention that can introduce complexity. Furthermore, performance unpredictability due to shared resources and the overhead of containerization can lead to inconsistent results, especially under heavy load. These factors combined make some administrators hesitant to rely solely on Kubernetes for critical database workloads.