Virtual Kubernetes Cluster
The Virtual Kubernetes Cluster provider gives a team a managed Kubernetes control plane inside Codesphere for cloud-native workloads, Helm-based deployments, and advanced orchestration scenarios.
In the current provider definitions, this provider is a preview Advanced Compute service with a single customizable plan.
| Property | Value | Notes |
|---|---|---|
| Provider name | virtual-k8s | Use this in landscape provider definitions. |
| Version | v1 | Current schema version exposed by the provider. |
| Category | Advanced Compute | Shown in the managed services catalog. |
| Scope | global | Available at team scope rather than being tied to a single workspace runtime. |
| Team singleton | true | A team can only have one Virtual Kubernetes Cluster service instance. |
| Pause support | false | This provider does not support pausing. |
Preview Feature
This provider is currently a preview feature. It is not enabled by default and needs to be enabled by your operator.
Schema
This provider does not expose provider-specific config. Access is handled through the injected kubeconfig and Codesphere networking.
Plan
The provider exposes one plan, Custom (id: 0), which allows all resource limits to be adjusted within the provider-defined ranges.
Example plan: Custom (id: 0).
| Parameter | Type | Default | Minimum | Maximum | Static | Notes |
|---|---|---|---|---|---|---|
cpu | integer | 20 | 20 | 160 | No | vCPU limit, priced as cpu-tenths. |
memory | integer | 5120 | 5120 | 32768 | No | RAM limit in MiB, priced as ram-mib. |
storage | integer | 20000 | 20000 | 120000 | No | Persistent storage limit in MiB, priced as storage-mib. |
ephemeralStorage | integer | 30000 | 30000 | 120000 | No | Ephemeral storage limit in MiB, priced as storage-mib. |
Other runtimes typically access this provider indirectly.
Workspaces and landscapes use the injected ~/.kube/config to deploy into the cluster with kubectl or helm, while services running inside the cluster can access other Codesphere resources over the same team network.
For the runtime-specific URL patterns and kubeconfig workflow, see Virtual Clusters.