Overview of KCI pods

Last updated:2021-04-14 15:43:55

Based on KCI, KSK provides a container service that is fully compatible with the Kubernetes ecosystem.

Pods in a KSK cluster run in a securely isolated container operating environment based on KCI. KCI pods are completely isolated at the underlying layer by a lightweight virtualization technology, without mutual interference.


For more information about the specifications supported by KCI pods, see Specifications.

For more information about how to specify KCI pod specifications, see Specify KCI pod specifications.


The following types of volumes are supported:

  • EmptyDir
  • EBS


By default, a KCI pod runs in a VPC and occupies one elastic network interface (ENI) in a subset. KCI pods have the following characteristics:

  • KCI pods in a cluster are interconnected with pods and nodes on a KEC instance.
  • KCI pods allow you to expose services through SLB.
  • EIPs can be directly attached to KCI pods.
  • Ingress is supported.


KCI can be monitored from two dimensions: pods and containers. For more information, see Monitoring metrics.


Serverless clusters do not contain actual nodes. Some features that rely on nodes, Kubelet, and Kube-proxy are not supported.

  • Running DaemonSet pods on virtual nodes is not supported.
  • HostPath volumes are not supported.
  • Running containers in the privileged mode is not supported.
  • Readiness probe and liveness probe are not supported.
  • Running an init container is not supported.
  • Services whose type is NodePort are not supported.
  • The HostNetwork type is not supported.

Did you find the above information helpful?

Mostly Unhelpful
A little helpful
Very helpful

What might be the problems?

Unclear or awkward
Redundant or clumsy
Lack of context for the complex system or functionality

More suggestions


Please give us your feedback.


Thank you for your feedback.