Deploying ScyllaDB Operator with GitOps

Deploying the ScyllaDB Operator on Kubernetes clusters involves various methods, including using GitOps practices and Helm charts, to manage infrastructure and application configurations. ScyllaDB Operator provides support for different deployment strategies, with versions 1.1 and 1.2 introducing Helm charts and publishing deployment manifests for manual or GitOps automation, respectively. GitOps employs Git as the single source of truth, making system states visible and auditable, with Kubernetes manifests stored in a Git repository. The deployment process involves setting up local storage using Kubernetes persistent volumes and installing necessary components like the cert-manager for internal webhooks. The deployment manifests are organized into specific folders and need to be applied in sequence due to interdependencies, ensuring components such as scylla-manager and ScyllaDBCluster are established. Customization is possible through Git, allowing adjustments to manifest resources without compromising supported deployments. The ScyllaDB team is working to simplify deployment further and plans to introduce an Operator Lifecycle Manager bundle on operatorhub.io.