Resource Types DefaultPreemptionArgs InterPodAffinityArgs KubeSchedulerConfiguration NodeAffinityArgs NodeResourcesBalancedAllocationArgs NodeResourcesFitArgs PodTopologySpreadArgs VolumeBindingArgs ClientConnectionConfiguration Appears in: KubeSchedulerConfiguration ClientConnectionConfiguration contains details for constructing a client. FieldDescription kubeconfig [Required] string kubeconfig is the path to a KubeConfig file. acceptContentTypes [Required] string acceptContentTypes defines the Accept header sent by clients when connecting to a server, overriding the default value of 'application/json'. This field will control all connections to the server used by a particular client. contentType [Required] string contentType is the content type used when sending data to the server from this client.

This website is maintained by Kubernetes SIG Docs. The Kubernetes project welcomes help from all contributors, new or experienced! Kubernetes documentation contributors: Improve existing content Create new content Translate the documentation Manage and publish the documentation parts of the Kubernetes release cycle Note:To learn more about contributing to Kubernetes in general, see the general contributor documentation site. Getting started Anyone can open an issue about documentation, or contribute a change with a pull request (PR) to the kubernetes/website GitHub repository.

Resource Types CloudControllerManagerConfiguration LeaderMigrationConfiguration KubeControllerManagerConfiguration ClientConnectionConfiguration Appears in: GenericControllerManagerConfiguration ClientConnectionConfiguration contains details for constructing a client. FieldDescription kubeconfig [Required] string kubeconfig is the path to a KubeConfig file. acceptContentTypes [Required] string acceptContentTypes defines the Accept header sent by clients when connecting to a server, overriding the default value of 'application/json'. This field will control all connections to the server used by a particular client. contentType [Required] string contentType is the content type used when sending data to the server from this client.

Each major Kubernetes release introduces new features that require documentation. New releases also bring updates to existing features and documentation (such as upgrading a feature from alpha to beta). Generally, the SIG responsible for a feature submits draft documentation of the feature as a pull request to the appropriate development branch of the kubernetes/website repository, and someone on the SIG Docs team provides editorial feedback or edits the draft directly.

This page shows how to use Weave Net for NetworkPolicy. Before you begin You need to have a Kubernetes cluster. Follow the kubeadm getting started guide to bootstrap one. Install the Weave Net addon Follow the Integrating Kubernetes via the Addon guide. The Weave Net addon for Kubernetes comes with a Network Policy Controller that automatically monitors Kubernetes for any NetworkPolicy annotations on all namespaces and configures iptables rules to allow or block traffic as directed by the policies.

This page shows how to configure and enable the ip-masq-agent. 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:

Perform common configuration tasks for Pods and containers.

FEATURE STATE: Kubernetes v1.27 [stable] An increasing number of systems leverage a combination of CPUs and hardware accelerators to support latency-critical execution and high-throughput parallel computation. These include workloads in fields such as telecommunications, scientific computing, machine learning, financial services and data analytics. Such hybrid systems comprise a high performance environment. In order to extract the best performance, optimizations related to CPU isolation, memory and device locality are required. However, in Kubernetes, these optimizations are handled by a disjoint set of components.

Note This tutorial applies only for new clusters. Pod Security Admission is an admission controller that applies Pod Security Standards when pods are created. It is a feature GA'ed in v1.25. In this tutorial, you will enforce the baseline Pod Security Standard, one namespace at a time. You can also apply Pod Security Standards to multiple namespaces at once at the cluster level. For instructions, refer to Apply Pod Security Standards at the cluster level.

Setting up an extension API server to work with the aggregation layer allows the Kubernetes apiserver to be extended with additional APIs, which are not part of the core Kubernetes APIs. 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.