Kubernetes and ScyllaDB: 10 Questions and Answers

The blog post covers a webinar discussing the integration of ScyllaDB with Kubernetes, addressing several key questions raised during the event. Helm and YAML manifest files are compared, with Helm being a packaging system that simplifies managing multiple manifest files through Helm Charts. It explains that if a ScyllaDB pod fails within a StatefulSet, it is replaced without changing its identity, and multi-datacenter deployments are supported by creating separate StatefulSets for each region. Pod readiness is determined by the status probe, specifically using nodetool status, while internal DNS management is handled by the StatefulSet. Despite a current performance degradation of 25% to 40% when using Docker containers, Kubernetes offers a unified deployment platform across various infrastructures, unlike AMIs that are AWS-specific. Upgrading ScyllaDB involves taking snapshots and reattaching upgraded containers to existing persistent storage. Helm Charts for ScyllaDB deployment are available and being integrated into main repositories, and the impact of data volume on deployment and decommissioning is discussed, highlighting increased throughput requirements. The post also promotes an upcoming webinar on powering Spark with ScyllaDB and provides links for further exploration of ScyllaDB, including downloads and user feedback.