Instead of letting the installer create and manage a cluster for you (on Hyper-V or vSphere with Talos Linux), you can deploy VAM into a Kubernetes cluster you already run, on-prem or in the cloud. The installer then skips all VM / OS provisioning and only deploys VAM's platform components and services as Helm packages into your cluster.
This page covers the prerequisites for that cluster and how the install proceeds.
This page is for a Kubernetes or platform administrator who owns an existing cluster and wants VAM deployed onto it. If you want the installer to build the cluster for you, see Prerequisites > Hyper-V (Windows): Single Host or VMware vSphere Deployment instead.
What the Installer Deploys into Your Cluster
VAM is not a single container but a platform. When you point the installer at your cluster, it deploys (as packages) the components VAM depends on, alongside the VAM services themselves:
Layer | Component(s) | Role |
|---|---|---|
Ingress / gateway | Traefik (Gateway API) | Terminates HTTPS and routes to the internal services. |
Certificates | cert-manager + trust-manager + an issuer (the built-in certificate authority or ADCS) | Issues and renews the gateway certificate and distributes the CA bundle. |
Object storage | AIStor (operator and object store) | The authoritative media store (S3 API). |
Block storage | DirectPV and/or local-path-provisioner | Local NVMe/SSD provisioning for the stateful workloads. |
Databases / index | SurrealDB, OpenSearch | Cache / index over the object store. |
Messaging | RabbitMQ | Event bus between services. |
Identity | Your identity provider (Microsoft Entra ID) | Sign-in for users and services. |
Container registry | Harbor | Optional in-cluster OCI registry. The installer does not deploy it, so install it from the Configuration Service. |
Observability | OpenTelemetry Collector | Collects metrics, logs and traces and forwards them to your own monitoring system, which VAM does not install. See Prerequisites > Monitoring and Log Storage. |
GPU (optional) | NVIDIA device plugin, AMD GPU operator | Exposes host GPUs to workloads that need them (for example, AI features). |
VAM services | VAM core and the Configuration Service. Other applications, such as the MCP server and the Workflow Bridge, are installed later from the Configuration Service. | The application itself. |
You can let the installer deploy all of these or, if your cluster already provides some of them (for example your own ingress controller or an existing StorageClass), configure VAM to use what you have.
Component versions are pinned per VAM release. Each package declares the exact upstream chart and app versions it ships, so an installation is reproducible and you do not choose the versions of these components yourself. The release notes name the main bundled components, and the versions running in your installation are shown per package in Configuration Service > Packages after install.
Cluster Prerequisites
Area | Requirement |
|---|---|
Kubernetes version | A version that the Kubernetes project still supports. The installer creates new clusters on Hyper-V and VMware vSphere with Kubernetes 1.37. |
Access | An admin |
Isolation | The cluster, or at least dedicated namespaces, not shared with unrelated workloads. |
Capacity | Enough total CPU / RAM / disk for the worker sizing in Prerequisites > Multi-Node Production. |
Storage | Block devices for DirectPV, or an existing default |
Ingress / exposure | A |
DNS | An A record for the public hostname (for example, |
TLS | A certificate issuer: the built-in certificate authority or ADCS (see below). |
Identity | An identity provider configured per Identity Provider Setup. |
Storage: DirectPV or a StorageClass
VAM's object store (AIStor) needs fast local block storage.
- DirectPV, recommended for local NVMe or SSD drives: DirectPV is installed with the
kubectlkrew plugin, discovers and formats raw drives and exposes adirectpv-min-iostorage class. The high-level flow iskubectl directpv install, thenkubectl directpv discover, then review the generateddrives.yaml, thenkubectl directpv init drives.yaml. See the DirectPV documentation. - An existing
StorageClass: if your cluster already provides suitable persistent block storage, VAM can use it instead. Provision capacity sized to your media volume.
For storage spread across multiple nodes, use the MinIO Erasure Code Calculator to size the layout.
Certificates: cert-manager Issuers
The gateway serves HTTPS using a certificate issued by cert-manager. The installer offers the following issuers, set in the cert-manager (ADCS) section of Deployment Options.
- Built-in certificate authority: self-signed, for evaluation. The installer uses it when the cert-manager (ADCS) fields are empty.
- Enterprise certificate authority with Active Directory Certificate Services (ADCS): for on-premises Microsoft environments, VAM uses an ADCS issuer with
cert-manager, which requests the certificates from your ADCS server.trust-managerthen distributes the CA bundle so in-cluster clients (such as AIStor) trust the issued certificate. The fields are described in Running the Installer > View 2: Deployment Options, and the template requirements in Prerequisites > Certificate Template for ADCS.
Identity: Microsoft Entra ID
Sign-in works exactly as for a provisioned cluster. Set up Microsoft Entra ID as described in Identity Provider Setup.
Running the Install
- Have an admin
kubeconfigfor the target cluster on the installer host. - Prepare storage, DNS, certificate inputs and (if external) the OIDC details ahead of time.
- Launch
vamctl.exeand follow Running the Installer through Prepare Installer and Registry Login. - On Cluster Setup, select Use Existing Cluster and select your cluster in Cluster context. To add a kubeconfig first, run Manage Cluster Contexts.
- The installer skips cluster provisioning and goes straight to Deployment Configuration. Set the public hostname, the certificate issuer, the identity provider and the license server, then deploy.
- Finish with the sanity check as in the main walkthrough.