expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

If you want to control traffic flow at the IP address or port level (OSI layer 3 or 4), NetworkPolicies allow you to specify rules for traffic flow within your cluster, and also between Pods and the outside world. Your cluster must use a network plugin that supports NetworkPolicy enforcement.

When you specify a Pod, you can optionally specify how much of each resource a container needs. The most common resources to specify are CPU and memory (RAM); there are others. When you specify the resource request for containers in a Pod, the kube-scheduler uses this information to decide which node to place the Pod on. When you specify a resource limit for a container, the kubelet enforces those limits so that the running container is not allowed to use more of that resource than the limit you set.

This document describes persistent volumes in Kubernetes. Familiarity with volumes, StorageClasses and VolumeAttributesClasses is suggested. Introduction Managing storage is a distinct problem from managing compute instances. The PersistentVolume subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this, we introduce two new API resources: PersistentVolume and PersistentVolumeClaim. A PersistentVolume (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using Storage Classes.

FEATURE STATE: Kubernetes v1.25 [stable] You can customize the behavior of the kube-scheduler by writing a configuration file and passing its path as a command line argument. A scheduling Profile allows you to configure the different stages of scheduling in the kube-scheduler. Each stage is exposed in an extension point. Plugins provide scheduling behaviors by implementing one or more of these extension points. You can specify scheduling profiles by running kube-scheduler --config <filename>, using the KubeSchedulerConfiguration v1 struct.