How kcp-dev/kcp works
Main Components
a. Core Components:
• API Server Layer
• Virtual Workspaces
• API Export/Import System
• Authentication/Authorization
• Workspace Management
• Cache Server
• Front Proxy
• Storage (etcd)
b. Key Subsystems:
• Admission Controllers
• Reconcilers
• Virtual API Framework
• Client SDK
┌─ External Clients/Users ─────────────────────┐
• Front Layer ────────────────────────────────┤
• kcp-front-proxy │
• Authentication/Authorization │
• Core Services Layer ────────────────────────┤
• ┌─ Workspace Management ─┐ ┌─ API Services ─┐│
• Workspace Controller │ │ - APIExports ││
• Workspace Types │ │ - APIBindings ││
• ┘ └───────────────┘ │
• Virtual Framework Layer ───────────────────┤
• Dynamic API Registration │
• API Resource Management │
• Storage Layer ──────────────────────────────┤
• etcd │
• Cache Server │
• ┘
Connection Types
• Double lines: High-bandwidth data paths
Key Elements to Highlight
a. Workspace Isolation:
• How workspaces are isolated from each other
• Workspace type inheritance
• Resource boundaries
b. API Management:
• APIExport flow
• APIBinding relationships
• Schema management
c. Authentication Flow:
• User authentication path
• Authorization decisions
• RBAC integration
Additional Details
Annotations for:
• Key configuration points
• Scaling components
• High availability pairs
• Security boundaries
• API version management
Implementation Notes
• Relationship between /pkg/virtual and API management
• How /pkg/reconciler components maintain system state
• Demonstrate how /pkg/admission controls access and validation
• Cache server's role from /pkg/cache
Security Boundaries
Clearly mark:
• Trust boundaries
• Authentication checkpoints
• Authorization enforcement points
• Isolation mechanisms
Remember to maintain consistency with the project's actual implementation as shown in the file structure, particularly the core components in /pkg and the API definitions in /sdk/apis.