Architecture
Architecture Overview
Platform Component Model
Cloud Orbiter is organized into four functional layers:
| Layer | Components | Technology |
|---|---|---|
| User Interface & API | Management Dashboard, REST API, kubectl Proxy, WebSocket Notifications | React, REST, WebSocket |
| Identity & Access | Authentication, RBAC, SSO federation, session management | Keycloak, OpenID Connect, Okta, Google, Microsoft |
| Cluster Orchestration | CKP cluster provisioning and lifecycle management | Kubernetes API, CKP, CAPI |
| Platform Services | App Lifecycle, Observability, Backup, VMs, Test Suites, Add-ons | Helm, Prometheus, Velero, KubeVirt |
CKP Architecture
CKP (Coredge Kubernetes Platform) operates across two functional layers:
| Layer | Function | Components |
|---|---|---|
| Distribution Layer | Delivers custom-built, validated Kubernetes packages | kubeadm, kubelet, kubectl, Coredge-hosted core images |
| Management Layer | Handles cluster lifecycle through CAPI | Cluster API, Provisioning, Scaling, Upgrades |
Supported Configurations
| Specification | Details |
|---|---|
| Kubernetes Versions | v1.33.7, v1.34.3, v1.35.1 (CNCF Certified) |
| Operating Systems | Ubuntu 22.04, Ubuntu 24.04, Red Hat Enterprise Linux 9 |
| Infrastructure Provider | Orbiter Baremetal (BMS) |
| Architectures | AMD64, ARM64 |
Connectivity Model
Cloud Orbiter uses an outbound agent model for cluster connectivity:
| Component | Role |
|---|---|
| Cloud Orbiter Control Plane | Central management engine — hosts all APIs, dashboards, and orchestration logic |
| Orbiter Agent | Lightweight agent deployed on each target cluster; initiates outbound connection to control plane |
| NAT Gateway | Translates private network addresses for internet-bound agent connections |
| kubectl Proxy | Control plane acts as proxy for all Kubernetes CLI and API access to target clusters |
This model means:
- No inbound firewall rules are required on target clusters
- Clusters behind strict enterprise firewalls, private networks, and edge sites can all be managed
- Cluster access is always mediated through the control plane — enabling centralized audit logging
Tenant & Project Isolation
| Level | Description | Isolation |
|---|---|---|
| Tenant | Top-level organizational boundary (enterprise, department, customer) | Fully isolated identity realm per tenant |
| Project | Logical grouping within a tenant for teams or applications | Resources, clusters, and apps scoped to project |
| Users & Roles | Assigned to projects with explicit RBAC roles | Tenant Admin, Project Admin, Default User |
Add-On Architecture
Cloud Orbiter extends cluster capabilities through pre-configured, tested Add-Ons:
| Add-On | Purpose |
|---|---|
| Prometheus | Metrics collection and alerting for cluster observability |
| Velero | Namespace backup, restore, disaster recovery, and cluster migration |
| KubeVirt | Virtual machine lifecycle management on Kubernetes nodes |
Add-Ons are installed and uninstalled directly from the cluster dashboard without manual Helm commands or YAML editing.