Was this page helpful?
Caution
You're viewing documentation for an unstable version of ScyllaDB Operator. Switch to the latest stable version.
Overview¶
Foreword¶
ScyllaDB Operator is a set of controllers and API extensions that need to be installed in your cluster. The Kubernetes API is extended using CustomResourceDefinitions (CRDs) and dynamic admission webhooks to provide new resources (API reference). These resources are reconciled by controllers embedded within the ScyllaDB Operator deployment.
ScyllaDB is a stateful application and ScyllaDB Operator requires you to have a storage provisioner installed in your cluster. To achieve the best performance, we recommend using a storage provisioner based on local NVMEs. You can learn more about different setups in a dedicated storage section.
Components¶
ScyllaDB Operator deployment consists of several components that need to be installed / present in you Kubernetes cluster. By design, some of the components need elevated permissions, but they are only accessible to the administrators.