English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

Lower-level detail relevant to creating or administering a Kubernetes cluster.

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

Static Pods are managed directly by the kubelet daemon on a specific node, without the API server observing them. Unlike Pods that are managed by the control plane (for example, a Deployment); instead, the kubelet watches each static Pod (and restarts it if it fails). Static Pods are always bound to one Kubelet on a specific node. The kubelet automatically tries to create a mirror Pod on the Kubernetes API server for each static Pod.

The cloud-controller-manager is a Kubernetes control plane component that embeds cloud-specific control logic. The cloud controller manager lets you link your cluster into your cloud provider's API, and separates out the components that interact with that cloud platform from components that only interact with your cluster. By decoupling the interoperability logic between Kubernetes and the underlying cloud infrastructure, the cloud-controller-manager component enables cloud providers to release features at a different pace compared to the main Kubernetes project.

This page shows how to enable or disable an API version from your cluster's control plane. Specific API versions can be turned on or off by passing --runtime-config=api/<version> as a command line argument to the API server. The values for this argument are a comma-separated list of API versions. Later values override earlier values. The runtime-config command line argument also supports 2 special keys: api/all, representing all known APIs api/legacy, representing only legacy APIs.