Kube-DC platform
Kube-DC is a Kubernetes-based platform for Organizations to run virtual machines, containers, managed services, object storage, and Managed Clusters. This section is for the operators who install, secure, and run the management cluster.
Start here
| Goal | Documentation |
|---|---|
| Understand the product model | Architecture overview |
| Plan an installation | Installation overview |
| Install the platform | Installation guide |
| Understand Organizations, Projects, and access | Multi-tenancy and access control |
| Design provider and Project networks | Networking architecture |
| Operate internal platform endpoints | Internal platform endpoints |
| Publish and operate a managed services catalog | Managed services overview, Enabling managed services, Publishing the catalog, Operating the service |
| Review platform controls and trust boundaries | Security model |
| Operate metrics, logs, alerts, and dashboards | Observability |
| Send operator alerts to Slack and Opsgenie | Set up alert notifications with Fleet |
| Provision and bill organizations from a hosting portal | Provisioning API for hosting providers |
Product vocabulary
- An Organization is the tenant boundary for identity, membership, billing, shared quota, and policy.
- A Project is the governed workload boundary inside an Organization.
Kubernetes implements it with a backing namespace named
{organization}-{project}and a dedicated Kube-OVN VPC. - A Managed Cluster is a separate Kubernetes API and control plane created from a Project. It has its own authorization boundary.
Use backing namespace only when an operator must work with the underlying Kubernetes object. Use cluster only for the management cluster or a Managed Cluster.