High-level indicators for measuring the reliability and performance of Kubernetes components.

FEATURE STATE: Kubernetes v1.30 [beta] (enabled by default: true) Checkpointing a container is the functionality to create a stateful copy of a running container. Once you have a stateful copy of a container, you could move it to a different computer for debugging or similar purposes. If you move the checkpointed container data to a computer that's able to restore it, that restored container continues to run at exactly the same point it was checkpointed.

English ▾ English Deutsch Français Português (Brasil) 简体中文 Topics ▾ Setup and Config git config help bugreport Creden...

FastAPI framework, high performance, easy to learn, fast to code, ready for production

Production-Grade Container Orchestration

FastAPI framework, high performance, easy to learn, fast to code, ready for production

This page shows how to assign a Kubernetes Pod to a particular node in a Kubernetes cluster. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

This task shows you how to debug a StatefulSet. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. You should have a StatefulSet running that you want to investigate. Debugging a StatefulSet In order to list all the pods which belong to a StatefulSet, which have a label app.kubernetes.io/name=MyApp set on them, you can use the following:

This page shows how to assign a memory request and a memory limit to a Container. A Container is guaranteed to have as much memory as it requests, but is not allowed to use more memory than its limit. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts.

Assign infrastructure resources to your Kubernetes workloads.