How scylladb/scylla-operator works
Core Architectural Layers (Use horizontal layers)
Top Layer - Kubernetes API Server:
• Custom Resource Definitions (CRDs)
• Webhooks for validation
• RBAC components
Middle Layer - Operator Control Logic:
• Controller reconciliation loops
• Resource management
• State handling
Bottom Layer - Managed Resources:
• Scylla database pods
• Monitoring components
• Storage and networking resources
a. Control Flow:
b. Data Flow:
Specific Components
a. Custom Resources (from pkg/api/scylla):
• ScyllaCluster
• NodeConfig
• ScyllaDBMonitoring
• ScyllaOperatorConfig
b. Controllers (from pkg/controller):
• ScyllaCluster controller
• NodeConfig controller
• Monitoring controller
• Sidecar controller
c. Supporting Services:
• Certificate management
• Resource management
• Health checking
• Backup/restore functionality
Integration Points
a. External Systems:
• Prometheus monitoring
• Grafana dashboards
• Cloud provider services
• Storage systems
b. Internal Components:
• CQL client interfaces
• Management APIs
• Metrics endpoints
Operational Flows
• Cluster deployment
• Scaling operations
• Upgrade procedures
• Backup processes
• Component groupings