Removing VAM is done at the levels below, and only the first is a supported self-service operation.

Level

How

One package

Configuration Service, on the package detail view. Supported for optional packages.

The whole installation

Not a workflow in the installer. See Removing a Whole Installation.

Uninstalling is destructive. A package uninstall deletes that package's data, and removing an installation deletes every asset, all configuration and all metadata held on the cluster. Take a backup first if there is any chance you want the data back.

Uninstalling a Package

You uninstall a single package in the Configuration Service, with Uninstall in the ... menu of its detail view. The steps, and the cases in which a package cannot be uninstalled, are in Managing Packages > Uninstalling a Package.

Removing a Whole Installation

The installer has no uninstall workflow. None of the workflows on the Choose Workflow step removes a deployment.

A deployment from the installer removes packages in these cases:

  • With Upgrade existing installation clear, it uninstalls the existing VAM releases and deletes their data before it installs from scratch.
  • In upgrade mode, it removes a deployed package that is no longer part of the deployment, for example an Optional Components entry that you clear on Deployment Options. It never removes the AMD GPU Operator and the NVIDIA Device Plugin this way.

How you remove an installation therefore depends on who owns the cluster:

  • The installer created the cluster on Hyper-V or vSphere: the nodes are virtual machines that exist only for VAM, so removing them in Hyper-V Manager or vCenter removes the installation with them. Delete the VMs and their disks, then clean the installer host as below.
  • You brought your own Kubernetes cluster: VAM was deployed as Helm releases into your cluster. Contact Vizrt support before removing them by hand, because the removal order matters and some components hold persistent volumes.

Contact Vizrt support if an installation must be removed cleanly from a production environment. Reinstalling over a half-removed installation is not supported.

Cleaning the Installer Host

vamctl leaves the following on the installer host, separate from anything in the cluster:

  • Configuration, logs and exports, in %APPDATA%\Vizrt\vamctl\.
  • Cached packages, in %LOCALAPPDATA%\Vizrt\vamctl\packages\, and in %LOCALAPPDATA%\Vizrt\vamctl\packages-local\ if local package overrides were used.
  • Working files, such as staged images and boot media, under %APPDATA%\Vizrt\vamctl\work\.
  • The registry credential, in %LOCALAPPDATA%\VizAM\registry-auth\.
  • Cluster credentials, in %USERPROFILE%\.kube\config and %USERPROFILE%\.talos\config, with earlier copies in the backups folder next to each. They give cluster-admin access. If they also hold contexts for other clusters, remove only the VAM contexts.
  • Installer backups, by default in %USERPROFILE%\VizAM_Backups\. They hold asset data.
  • Hyper-V virtual switches that the installer created. Their default names are VAMPublicSwitch and VAMPrivateSwitch. The private switch exists only on a cluster with worker nodes, and it comes with a NAT named InternalNat.
  • The Podman machine, which is the WSL distribution podman-machine-default. Remove it with podman machine stop and podman machine rm unless something else on the host uses Podman.

Delete these to leave the host clean. Keep the installer backups until you are sure that you do not need the asset data in them.

The installer also installed command-line tooling on the host, such as kubectl, Helm, talosctl and Podman. Removing that tooling, or turning off Hyper-V, is a decision about the host itself, not part of removing VAM.