FEATURE STATE: Kubernetes v1.30 [alpha] (enabled by default: false) Kubernetes relies on API data being actively re-written, to support some maintenance activities related to at rest storage. Two prominent examples are the versioned schema of stored resources (that is, the preferred storage schema changing from v1 to v2 for a given resource) and encryption at rest (that is, rewriting stale data based on a change in how the data should be encrypted).

This page shows how to use kubectl to list all of the Container images for Pods running in a 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 section is relevant for people adopting a new built-in sidecar containers feature for their workloads. Sidecar container is not a new concept as posted in the blog post. Kubernetes allows running multiple containers in a Pod to implement this concept. However, running a sidecar container as a regular container has a lot of limitations being fixed with the new built-in sidecar containers support. FEATURE STATE: Kubernetes v1.29 [beta] (enabled by default: true) Objectives Understand the need for sidecar containers Be able to troubleshoot issues with the sidecar containers Understand options to universally "inject" sidecar containers to any workload Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.

Security is an important concern for most organizations and people who run Kubernetes clusters. You can find a basic security checklist elsewhere in the Kubernetes documentation. To learn how to deploy and manage security aspects of Kubernetes, you can follow the tutorials in this section.

FEATURE STATE: Kubernetes v1.21 [stable] This page shows how to limit the number of concurrent disruptions that your application experiences, allowing for higher availability while permitting the cluster administrator to manage the clusters nodes. Before you begin Your Kubernetes server must be at or later than version v1.21. To check the version, enter kubectl version. You are the owner of an application running on a Kubernetes cluster that requires high availability.

Scale an existing app manually using kubectl.

This page shows how to perform a rollback on a DaemonSet. 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:

Extend kubectl by creating and installing kubectl plugins.

Configure and schedule GPUs for use as a resource by nodes in a cluster.

System component metrics can give a better look into what is happening inside them. Metrics are particularly useful for building dashboards and alerts. Kubernetes components emit metrics in Prometheus format. This format is structured plain text, designed so that people and machines can both read it. Metrics in Kubernetes In most cases metrics are available on /metrics endpoint of the HTTP server. For components that don't expose endpoint by default, it can be enabled using --bind-address flag.