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.

When using the kubelet's --config-dir flag to specify a drop-in directory for configuration, there is some specific behavior on how different types are merged. Here are some examples of how different data types behave during configuration merging: Structure Fields There are two types of structure fields in a YAML structure: singular (or a scalar type) and embedded (structures that contain scalar types). The configuration merging process handles the overriding of singular and embedded struct fields to create a resulting kubelet configuration.

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

FEATURE STATE: Kubernetes v1.10 [stable] kubeadm init and kubeadm join together provide a nice user experience for creating a bare Kubernetes cluster from scratch, that aligns with the best-practices. However, it might not be obvious how kubeadm does that. This document provides additional details on what happens under the hood, with the aim of sharing knowledge on the best practices for a Kubernetes cluster. Core design principles The cluster that kubeadm init and kubeadm join set up should be:

kubectl is the Kubernetes cli version of a swiss army knife, and can do many things. While this Book is focused on using kubectl to declaratively manage applications in Kubernetes, it also covers other kubectl functions. Command Families Most kubectl commands typically fall into one of a few categories: Type Used For Description Declarative Resource Management Deployment and operations (e.g. GitOps) Declaratively manage Kubernetes workloads using resource configuration Imperative Resource Management Development Only Run commands to manage Kubernetes workloads using Command Line arguments and flags Printing Workload State Debugging Print information about workloads Interacting with Containers Debugging Exec, attach, cp, logs Cluster Management Cluster operations Drain and cordon Nodes Declarative Application Management The preferred approach for managing resources is through declarative files called resource configuration used with the kubectl Apply command.

Production-Grade Container Orchestration

Production-Grade Container Orchestration

There are two official Kubernetes blogs, and the CNCF has its own blog where you can cover Kubernetes too. For the main Kubernetes blog, we (the Kubernetes project) like to publish articles with different perspectives and special focuses, that have a link to Kubernetes. Some articles appear on both blogs: there is a primary version of the article, and a mirror article on the other blog. This page describes the criteria for mirroring, the motivation for mirroring, and explains what you should do to ensure that an article publishes to both blogs.

Package v1beta2 is the v1beta2 version of the custom_metrics API. Resource Types MetricListOptions MetricValue MetricValueList MetricListOptions MetricListOptions is used to select metrics by their label selectors FieldDescription apiVersionstringcustom.metrics.k8s.io/v1beta2 kindstringMetricListOptions labelSelector string A selector to restrict the list of returned objects by their labels. Defaults to everything. metricLabelSelector string A selector to restrict the list of returned metrics by their labels MetricValue Appears in: MetricValueList MetricValue is the metric value for some object

This page shows how to change the default Storage Class that is used to provision volumes for PersistentVolumeClaims that have no special requirements. 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: