How rancher/turtles works
Main Components
a. Core Components:
• Rancher Turtles Operator
• Rancher Manager
• Cluster API (CAPI) Components
• Kubernetes API Server
• Fleet GitOps Engine
b. Custom Resources:
• CAPIProvider
• ClusterctlConfig
• ETCDMachineSnapshot (experimental)
• ETCDSnapshotRestore (experimental)
┌─ Control Plane Layer ─────────────────────────────┐
• ┌─ Rancher Manager ─┐ ┌─ Rancher Turtles ─────┐ │
• Controllers │ │
• Cluster Mgmt │◄─┤ - Sync Components │ │
• User Interface │ │ - Provider Management │ │
• ┘ └─────────────────────┬─┘ │
• ┌─ CAPI Operator ────────────────────────────┼──┐│
• Provider Controllers │ ││
• Cluster Management │ ││
• ┘ ││
• ┘
┌─ Infrastructure Layer ┼────────────────────────┐
• ┌─ Provider Layer ────┼─┐ │
• AWS │ │ │
• Azure ◄┘ │ │
• GCP │ │
• vSphere │ │
• ┘ │
• ┘
Key Interactions to Highlight
• Bidirectional communication between Rancher Turtles and Rancher Manager
• Flow of cluster creation/import process
• Provider management and synchronization
• Integration with Fleet GitOps
• ETCD backup/restore flows (experimental feature)
Important Details
a. Controller Flows:
• CAPIProvider Controller
• Import Controller
• Configuration Controller
• ETCD Snapshot Controller (experimental)
b. API Resources:
• CRD relationships
• API versions
• Experimental features
Specific Implementation Notes
• Version information for major components
• Experimental features with appropriate notation