Hi all, We are currently running a SolrCloud cluster on virtual machines and are planning to migrate it to Kubernetes for easier scalability, deployment, and management.
Our goals for this migration are: - Enable easier scaling of clusters in case of sudden request surges. - Facilitate upgrades and maintenance without downtime. - Optimize infrastructure usage by scaling down during off-peak hours and scaling up during peak hours. - Leverage Kubernetes-native features such as rolling updates, health checks, and monitoring. *we would like to know:* 1. B*est practices* for deploying and operating SolrCloud on Kubernetes? 2. Has anyone migrated an existing VM-based SolrCloud setup to Kubernetes, and what challenges should we be aware of (e.g., stateful storage, Zookeeper integration, network performance)? 3. Any recommended approaches for *persistent volume management* and ensuring data safety during migration? 4. Would you suggest using the *Solr Operator* or custom Helm charts, and what trade-offs have you observed? *Few details fyi:* Current Solr Version on our Production: v9.6.1 Index Size: ~250 GB Number of documents: ~180M Number of Shards: 63 Number of Nodes: 10 Average response time: ~80-100ms *Thanks & Regards,* *Uday Kumar*
