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.

To learn how to generate certificates for your cluster, see Certificates.

This page explains how to configure your DNS Pod(s) and customize the DNS resolution process in your 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 page shows how to safely drain a node, optionally respecting the PodDisruptionBudget you have defined. Before you begin This task assumes that you have met the following prerequisites: You do not require your applications to be highly available during the node drain, or You have read about the PodDisruptionBudget concept, and have configured PodDisruptionBudgets for applications that need them. (Optional) Configure a disruption budget To ensure that your workloads remain available during maintenance, you can configure a PodDisruptionBudget.

FEATURE STATE: Kubernetes v1.33 [beta] (enabled by default: false) Kubernetes 1.33 includes a beta feature that allows control plane components to deterministically select a leader via coordinated leader election. This is useful to satisfy Kubernetes version skew constraints during cluster upgrades. Currently, the only builtin selection strategy is OldestEmulationVersion, preferring the leader with the lowest emulation version, followed by binary version, followed by creation timestamp. Enabling coordinated leader election Ensure that CoordinatedLeaderElection feature gate is enabled when you start the API Server: and that the coordination.

FEATURE STATE: Kubernetes v1.18 [beta] This page explains how to add Windows worker nodes to a kubeadm cluster. Before you begin A running Windows Server 2022 (or higher) instance with administrative access. A running kubeadm cluster created by kubeadm init and following the steps in the document Creating a cluster with kubeadm. Adding Windows worker nodes Note:To facilitate the addition of Windows worker nodes to a cluster, PowerShell scripts from the repository https://sigs.

To avoid CNI plugin-related errors, verify that you are using or upgrading to a container runtime that has been tested to work correctly with your version of Kubernetes. About the "Incompatible CNI versions" and "Failed to destroy network for sandbox" errors Service issues exist for pod CNI network setup and tear down in containerd v1.6.0-v1.6.3 when the CNI plugins have not been upgraded and/or the CNI config version is not declared in the CNI config files.

This page shows how to assign a CPU request and a CPU limit to a container. Containers cannot use more CPU than the configured limit. Provided the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests. 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.

This page shows how to configure quotas for API objects, including PersistentVolumeClaims and Services. A quota restricts the number of objects, of a particular type, that can be created in a namespace. You specify quotas in a ResourceQuota object. 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.