Skip to main content
CKS is an unmanaged Kubernetes cluster provided by the GPU Cloud. It is suitable for running training, inference, data processing, or online services in containers, while using Kubernetes to centrally schedule computing resources, organize workloads, and maintain the runtime environment.

​
Applicable Scenarios

When your workloads require container orchestration, coordinated execution of multiple tasks, or ongoing maintenance of online services, you can choose a CKS cluster. If you need only one or a small number of compute resources for development and debugging, temporary experiments, single-node training, or manual O&M, you can prioritize CES instances. For more information, see Select Computing Resources.

​
Usage Process

  1. Create a CKS cluster and select the Kubernetes version, compute resources, and initial node pool.
  2. View cluster status and configuration and confirm that the cluster is available.
  3. Depending on the access method, create a cluster access role or access the cluster using KubeConfig.
  4. Scale nodes and install components as required by your workloads, and prepare namespaces, configurations, and persistent storage.
  5. Select a workload suitable for your business requirements and submit the YAML. Configure Ingress when you need to provide an entry point for HTTP or HTTPS services.
  6. Monitor business operations through workload status, monitoring, logs, and alerts, and clean up resources that are no longer needed when operations end.

​
Core Resources

​
Maintenance Responsibilities and Precautions

  • A CKS cluster is an unmanaged cluster. You must maintain the Kubernetes resources, workloads, and runtime environment within the cluster.
  • Node specifications and inventory may affect the creation of clusters or node pools.
  • Creating, modifying, or deleting Kubernetes resources may affect running tasks. Before performing any actions, confirm the resource scope, dependencies, and data impact.
  • Deleting a cluster releases its nodes and deletes the Kubernetes resources and node disk data within the cluster. Data in persistent storage is retained.