Index

IVAAP Deployment Operations Guide

IVAAP 2026.1

IVAAP delivery packages are available from the SLB Software Download Center. Starting with IVAAP 2026.1, each release is a single zip built around the ivaap installer binary. For most deployments and conversations, the only version that matters is 2026.1 (major.minor) — the full 2026.1.0-x form is reserved for precise package references.

Series	Delivery format	Primary install path
2025.x	Zip archive containing `deploy-ivaap.sh` plus chart, images, and seed	Run `deploy-ivaap.sh` on the target host
2026.x	Single zip containing the `ivaap` binary (embedded chart, images, seed, docs)	`./ivaap install` for k3s; `./ivaap retag-images` + `./ivaap generate-yaml` for BYO Kubernetes

The 2025.x script-based delivery is legacy. New deployments and upgrades should use the 2026.x ivaap binary.

To get started deploying IVAAP, be sure to first refer to the IVAAP Technical Data Sheet to make sure your environment meets required specifications for your deployment method. Once ready, start with the installation guide for your deployment method — Single-Node K3s Installation Guide for K3s deployments, and Multi-Node Kubernetes Installation Guide if you are deploying on AKS, EKS, or OpenShift.

These installation guides will get you up and running with the basic setup. Once this is done, proceed to Post-Deployment Advanced Configuration and the other guides for more advanced configuration and tuning.

For a full subcommand reference of the ivaap binary used throughout these guides — install, upgrade, TLS, connector enable/disable, status, uninstall — see IVAAP All-in-one Binary.

Reading the documentation before install

Windows — the delivery zip includes IVAAP_Documentation_*.exe, a standalone documentation browser. Run it on any Windows workstation to read the deployment guide without a Linux host.
Linux — keep IVAAP_Documentation_*.zip in the same directory as the ivaap binary and run ./ivaap docs start to serve the bundled MkDocs site on loopback. Stop with ./ivaap docs stop.

Contents¶

How to use this guide

The IVAAP Helm Template itself is meant to be considered a drop in replacment for upgrades. This means that it should never be directly modified. If modification is required, let SLB know so we can look into finding a permanent solution to make the modificaiton a configuration option. Otherwise - this modification will need to be added back after each upgrade of IVAAP versions.
Starting with IVAAP 2026.1, deliveries are a unified zip from the SLB Software Download Center. The primary artifact is the ivaap binary — it embeds the Helm chart, container images, and connectors. The zip also ships a Windows documentation executable (IVAAP_Documentation_*.exe), a documentation zip for ./ivaap docs start on Linux, a lightweight Helm chart config archive, and a README.md. Push the full zip to your Linux VM and extract there. Run ./ivaap install for a fully guided k3s deploy — no separate install scripts required.
The installation guides in this section deploy IVAAP with basic configuration: HTTP (no TLS certificates) and local authentication. In most scenarios, advanced configuration is required to add TLS and usually external authentication. First get IVAAP deployed successfully with the basic configuration, then follow Post-Deployment Advanced Configuration.
IVAAP should always be installed using two values files.
- The default values.yaml found in the IVAAPHelmTemplate (this contains default configuration, and the specific IVAAP versions for the helm release).
- Your generated deployment configuration YAML — /opt/ivaap/ivaap.values.yaml on k3s, or the file produced by ivaap generate-yaml on multi-node clusters. This YAML contains your deployment-specific configuration and may override image tags from the default values.yaml.
```
helm upgrade --install ivaap /path/to/IVAAPHelmTemplate \
-f /path/to/IVAAPHelmTemplate/values.yaml \
-f /path/to/<deployment-config>.values.yaml \
--namespace <namespace>
```