Expose an application running in your cluster behind a single outward-facing endpoint, even when the workload is split across multiple backends.

Ways to provide both long-term and temporary storage to Pods in your cluster.

FEATURE STATE: Kubernetes v1.21 [alpha] CSI volume health monitoring allows CSI Drivers to detect abnormal volume conditions from the underlying storage systems and report them as events on PVCs or Pods. Volume health monitoring Kubernetes volume health monitoring is part of how Kubernetes implements the Container Storage Interface (CSI). Volume health monitoring feature is implemented in two components: an External Health Monitor controller, and the kubelet. If a CSI Driver supports Volume Health Monitoring feature from the controller side, an event will be reported on the related PersistentVolumeClaim (PVC) when an abnormal volume condition is detected on a CSI volume.

kubeadm does not support automated ways of reconfiguring components that were deployed on managed nodes. One way of automating this would be by using a custom operator. To modify the components configuration you must manually edit associated cluster objects and files on disk. This guide shows the correct sequence of steps that need to be performed to achieve kubeadm cluster reconfiguration. Before you begin You need a cluster that was deployed using kubeadm Have administrator credentials (/etc/kubernetes/admin.

Production-Grade Container Orchestration

This page shows how to install and use Antrea CNI plugin on Kubernetes. For background on Project Antrea, read the Introduction to Antrea. Before you begin You need to have a Kubernetes cluster. Follow the kubeadm getting started guide to bootstrap one. Deploying Antrea with kubeadm Follow Getting Started guide to deploy Antrea for kubeadm. What's next Once your cluster is running, you can follow the Declare Network Policy to try out Kubernetes NetworkPolicy.

This page shows how to enable and configure autoscaling of the DNS service in your 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:

FEATURE STATE: Kubernetes v1.20 [stable] Kubernetes allow you to limit the number of process IDs (PIDs) that a Pod can use. You can also reserve a number of allocatable PIDs for each node for use by the operating system and daemons (rather than by Pods). Process IDs (PIDs) are a fundamental resource on nodes. It is trivial to hit the task limit without hitting any other resource limits, which can then cause instability to a host machine.

Since release v1.32, we introduced configurable version compatibility and emulation options to Kubernetes control plane components to make upgrades safer by providing more control and increasing the granularity of steps available to cluster administrators. Emulated Version The emulation option is set by the --emulated-version flag of control plane components. It allows the component to emulate the behavior (APIs, features, ...) of an earlier version of Kubernetes. When used, the capabilities available will match the emulated version:

Managing confidential settings data using Secrets.