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...

Specifics of npm's package.json handling

Update packages

Your workload can discover Services within your cluster using DNS; this page explains how that works.

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

A StatefulSet runs a group of Pods, and maintains a sticky identity for each of those Pods. This is useful for managing applications that need persistent storage or a stable, unique network identity.

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:

This tutorial demonstrates running Apache Zookeeper on Kubernetes using StatefulSets, PodDisruptionBudgets, and PodAntiAffinity. Before you begin Before starting this tutorial, you should be familiar with the following Kubernetes concepts: Pods Cluster DNS Headless Services PersistentVolumes PersistentVolume Provisioning StatefulSets PodDisruptionBudgets PodAntiAffinity kubectl CLI You must have a cluster with at least four nodes, and each node requires at least 2 CPUs and 4 GiB of memory. In this tutorial you will cordon and drain the cluster's nodes.