Install on Kubernetes (Helm)
Superna Data Security for Dell AI Infrastructure can run entirely inside your Kubernetes cluster, installed with its Helm chart. Everything runs as pods in one namespace:
- The console.
- PostgreSQL, through the CloudNativePG operator.
- ClickHouse, through the Altinity operator.
- The pipeline agents (extraction, linguistic coherence, and classify).
Both operators are bundled with the chart. To run the console as a VMware appliance instead, see Install on VMware (OVA).
Choose your platform
Each guide is complete on its own, with the validated values file for its platform, the checks to run before you install, and troubleshooting.
| Your platform | What the guide covers |
|---|---|
| RKE2 | RKE2's bundled ingress-nginx; storage from the local-path provisioner or your own StorageClass. |
| kubeadm | Adds ingress-nginx on the host network and storage, which kubeadm doesn't include. |
| OpenShift / OKD | The OpenShift router, the nonroot-v2 security context constraint, and OpenShift storage. |
On another Kubernetes distribution, start from the kubeadm guide and use your own ingress controller and StorageClass. Every chart setting, with its type and default, is in the Helm Values Reference. The version and build to install are on Releases.
In every guide, users reach the console over HTTPS on port 443, through an ingress controller. An air-gapped cluster can install from a private registry inside your network that holds all the images; each guide explains how. Without a registry, use the VMware appliance.
Pipeline agents on Kubernetes
Each pipeline stage runs as a StatefulSet in the release namespace, and its agents register with the console on their own. To scale a stage, set pipeline.stages.<stage>.replicas in your values file and run helm upgrade.
Because the chart manages the agents, System Operations > Fleet Management > Agent Installation, System Operations > Fleet Management > Agents Upgrade, and Settings > Software Update are disabled on a Kubernetes install.
Upgrade
The guides keep each release's chart in its own directory, <install-dir>/charts/<version>-<build>/aisec, and your settings in <install-dir>/override-values.yaml.
-
Download the new release's chart into its own directory:
mkdir -p <install-dir>/charts/<new-version>-<new-build>
helm pull oci://northamerica-northeast2-docker.pkg.dev/superna-579/oci/aisecurity/charts/aisec \
--version <new-version>-<new-build> --untar --untardir <install-dir>/charts/<new-version>-<new-build> -
Set the four image tags in
<install-dir>/override-values.yamlto<new-version>-<new-build>. -
Upgrade with the new chart directory:
helm upgrade aisec <install-dir>/charts/<new-version>-<new-build>/aisec \
-n aisec -f <install-dir>/override-values.yaml --timeout 15m
Never upgrade from an older release's chart directory: that re-applies the old chart.
Restart and roll back
- To restart the pods when nothing in the values changed, add
--set deployTimestamp=$(date +%s)to thehelm upgradecommand. - To list the revisions, run
helm history aisec -n aisec. - To return to a revision, run
helm rollback aisec <revision> -n aisec.
Roll back only to a revision that was installed with your full values. Revision 1 of the two-phase install has both databases turned off, and rolling back to it removes them. Keep the database image versions that the chart pins: ClickHouse data can't be read by an older ClickHouse version.
Uninstall
helm uninstall aisec -n aisec
The generated database and enrollment secrets are kept, so a later install into the same namespace reuses them.