Skip to main content
This page describes the minimum cluster capacity required to install Vantage 3.0 self-hosted. Because there are countless VM sizes and SKUs that can serve as Kubernetes nodes, requirements are expressed as total resource requests per node pool rather than as a node count. Resource requests are a floor, not a measure of load. Treat the numbers on this page as the bare minimum needed to get Vantage installed, then size for your document volume, concurrency, availability, and failure tolerance on top of them.
The figures below do not include service mesh sidecars (for example, Istio proxies).

​
Assumptions

The tables assume the recommended node pool layout described in Kubernetes node requirements: TechCore workers and training workers each run in their own node pool, separate from the rest of the Vantage workloads. The base figures exclude optional components:
  • TechCore 4 only. Earlier TechCore versions are listed under Optional components.
  • No custom blob storage service. Object storage is provided by Azure Blob Storage or S3-compatible storage, not the spec.storage.custom backend.
  • No optional workers or services.

​
How to read the tables

  • Pods, CPU, and Memory are the sum of resource requests across all workloads scheduled in that node pool.
  • Minimum node size is set by the largest single pod scheduled in that pool. A node smaller than this cannot run that pod regardless of how many nodes you add.
  • For the default pool, figures marked with an asterisk (*) include installation processes such as database migration jobs, in addition to long-lived deployments and stateful sets. Migration jobs are short-lived, but several applications sync at once during installation and upgrades, so their requests must be counted alongside the long-lived workloads.

​
Minimal install

A minimal install deploys Vantage with the lowest pod replica counts and resource requests. Use it to prove out networking and identity configuration, or as a test environment.

​
Production install

A production install deploys Vantage with production pod replica counts and resource requests, with KEDA autoscaling enabled.

​
Optional components

Enable these workloads only when your requirements call for them, and add their requests to the base figures above. Where two values are shown as n / m, n applies to a minimal install and m to a production install. A single value applies to both.

​
What’s next

Prerequisites

Label and taint the TechCore and training node pools.

Autoscaling with KEDA

Plan cluster capacity for autoscaled workloads.

Helm chart reference

Chart values for the vantage-selfhosted release.

API reference

Field-level contract for the Vantage custom resource.