How clastix/kamaji works
Main Components
a. Management Cluster Layer:
• Kamaji Controller (core component)
• Custom Resources (TenantControlPlane and Datastore)
• Webhook Server (for validation and mutation)
• Certificate Management System
b. Data Layer:
• Multiple Datastore options (etcd, MySQL, PostgreSQL, NATS)
• Kine adapter for non-etcd datastores
• Storage configuration and migration components
c. Control Plane Layer:
• Tenant Control Plane Pods
• Core Kubernetes components (API Server, Controller Manager, Scheduler)
• -ons (CoreDNS, kube-proxy)
• Konnectivity Server/Agent
Relationship Flows
• Control flow from Kamaji Controller to Tenant Control Planes
• Data flow between Control Planes and Datastores
• Certificate management flows
• Webhook validation/mutation paths
• Worker node connections through Konnectivity
Specific Implementation Details
• Custom Resources (purple rectangles)
• Controllers (blue rectangles)
• Kubernetes components (orange rectangles)
Key Architectural Patterns to Highlight
• Operator pattern for TenantControlPlane management
• Multi-tenancy support in datastores
• Blue/Green deployment for updates
• Webhook-based validation chain
• Certificate rotation mechanism
Additional Elements
Include:
• Version information
• Supported Kubernetes versions
• External integration points (Cluster API, etc.)
• Resource requirements and scaling indicators
Technical Details
• API versions (v1alpha1)
• Supported datastore types
• Certificate management flows
• Resource boundaries
• Network paths for control plane access
• The separation between management and tenant clusters
• The flexibility in datastore selection
• The automated certificate management
• The scalability aspects
• The multi-tenancy capabilities
Remember to:
• Keep components grouped logically
• Clear boundaries between different responsibility areas
• Failure domains and high availability patterns
• Document all external integration points
This system design should reflect Kamaji's role as a control plane manager while showing its integration with standard Kubernetes components and external systems.