Was this page helpful?
Caution
You're viewing documentation for an unstable version of Scylla Operator. Switch to the latest stable version.
Overview¶
There are generally 2 types of resources in Kubernetes: namespaced and cluster-scoped resources.
Tip
You can discover the available resources (for the installed version in your cluster) by running
kubectl api-resources --api-group=scylla.scylladb.com
and explore their schema using
kubectl explain --api-version='scylla.scylladb.com/v1alpha1' NodeConfig.spec
Namespaced resources¶
ScyllaClusters
ScyllaCluster defines a single datacenter ScyllaDB cluster and manages the racks within.
ScyllaDBClusters
ScyllaDBCluster defines a multi datacenter ScyllaDB cluster spanned across multiple Kubernetes clusters and manages the datacenters and racks within.
ScyllaDBMonitorings
ScyllaDBMonitoring defines and manages a ScyllaDB monitoring stack.
Cluster scoped resources¶
Cluster scoped resources declare the state for the whole cluster or control something at the cluster level which isn’t multitenant. Therefore, working with these resources requires elevated privileges.
Generally, there can be multiple instances of these resources but for some of them, like for ScyllaOperatorConfigs, it only makes sense to have one instance. We call them singletons and the single instance is named cluster.
NodeConfigs
NodeConfig manages setup and tuning for a set of Kubernetes nodes.
ScyllaOperatorConfigs
ScyllaOperatorConfig configures the Scylla Operator deployment and reports the status.
RemoteKubernetesClusters
RemoteKubernetesCluster configures the access for Scylla Operator to remotely deployed Kubernetes clusters.