> For the complete documentation index, see [llms.txt](https://docs.trilio.io/openstack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/openstack/deployment/installing-on-openstack-helm.md).

# Getting started with Trilio on OpenStack-Helm

### 1] Prepare for deployment

#### 1.1] Install Helm CLI Client

Ensure the Helm CLI client is installed on the node from which you are installing Trilio for OpenStack. Skip if helm version already works.

```
curl -O https://get.helm.sh/helm-v3.17.2-linux-amd64.tar.gz
tar -zxvf helm*.tar.gz
mv linux-amd64/helm /usr/local/bin/helm
rm -rf linux-amd64 helm*.tar.gz
```

#### 1.2] (Optional) Install NFS Client Package

If you plan to use NFS as a backup target, install nfs-common on each Kubernetes node where TrilioVault is running. Skip this step for S3 backup targets.

SSH into each Kubernetes nodes which have the following labels

```
kubectl get nodes --show-labels | grep openstack-control-plane
kubectl get nodes --show-labels | grep openstack-compute
```

Run this command on the respective nodes:

```
sudo apt-get install nfs-common -y
```

#### 1.3] Install Necessary Dependencies

Run the following command on the installation node:

```
sudo apt update -y && sudo apt install make jq -y
```

### 2] Clone Helm Chart Repository

{% hint style="info" %}
Refer to the link [Resources](https://docs.trilio.io/openstack/about-trilio-for-openstack/artifacts.md) to get release specific values of the placeholder, viz `trilio_branch`.
{% endhint %}

```
git clone -b {{ trilio_branch }} https://github.com/trilioData/triliovault-cfg-scripts.git
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/
helm dep up
cd ../../../
```

### 3] Configure Container Image Tags

Select the appropriate image values file based on your OpenStack-Helm setup. Update the Trilio-OpenStack image tags accordingly.

```
vi triliovault-cfg-scripts/openstack-helm/trilio-openstack/values_overrides/2023.2.yaml
```

Or

```
vi triliovault-cfg-scripts/openstack-helm/trilio-openstack/values_overrides/2026.1.yaml
```

* 2023.1 → `2023.1.yaml`
* 2023.2 → `2023.2.yaml`
* 2026.1 → `2026.1.yaml`

### 4] Create the `trilio-openstack` Namespace

To isolate `trilio-openstack` services, create a dedicated Kubernetes namespace:

```
kubectl create namespace trilio-openstack
kubectl config set-context --current --namespace=trilio-openstack
```

### 5] Label Kubernetes Nodes for TrilioVault Control Plane

Trilio for OpenStack control plane services should run on Kubernetes nodes labeled with `triliovault-control-plane=enabled`. Only nodes labeled with openstack-control-plane should be selected. For high availability, it is recommended to use three Kubernetes nodes.

#### 5.1] Retrieve the OpenStack control plane node names:

```
kubectl get nodes --show-labels | grep openstack-control-plane
```

#### 5.2] Assign the `triliovault-control-plane` label to the selected nodes:

```
kubectl label nodes <NODE_NAME_1> triliovault-control-plane=enabled
kubectl label nodes <NODE_NAME_2> triliovault-control-plane=enabled
kubectl label nodes <NODE_NAME_3> triliovault-control-plane=enabled
```

#### 5.3] Verify the nodes with the assigned label:

```
kubectl get nodes --show-labels | grep triliovault-control-plane
```

### 6] Provide Cloud Admin Credentials in keystone.yaml

The cloud admin user in Keystone must have the admin role on the cloud domain. Update the required credentials in below file:

```
vi triliovault-cfg-scripts/openstack-helm/trilio-openstack/values_overrides/keystone.yaml
```

### 7] Setup Internal RabbitMQ instance

Separate RabbitMQ Installation:

```
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/utils
./create_rabbitmq.sh
```

Check RabbitMQ pod created

```
root@osh-ctrl-1:~# kubectl get pods
NAME                                                 READY   STATUS      RESTARTS   AGE
rabbitmq-server-0                                    1/1     Running     0          1m
```

### 8] Generate Configuration Values

Run these scripts from the utils directory. Pass the Kubernetes cluster domain and the exact OpenStack public domain of this cloud. Use the domain the public endpoints use, for example `keystone.<public_domain>`.

```
openstack endpoint list --interface public -c "Service Name" -c URL     # e.g. https://keystone.gazpacho.triliodata.demo/v3
helm -n openstack get values keystone -a -o json | jq -r '.endpoints.cluster_domain_suffix, .endpoints.identity.host_fqdn_override.public.host'

./get_admin_creds.sh <internal_domain_name> <public_domain_name>

# example: ./get_admin_creds.sh cluster.local gazpacho.triliodata.demo
```

On 2026.1 the script prints:

```
Found secret openstack/nova-ks-etc: appending nova service credentials to nova-compute.conf
```

OpenStack-Helm 2026.1 nova keeps its service credentials (\[placement], \[neutron], \[cinder], \[keystone\_authtoken], \[service\_user]) in the secret nova-ks-etc instead of nova-compute.conf, and the script appends them. Without them the datamover cannot log in to Placement and restart-loops as Completed.

**Note:** i] The script also prints two NotFound errors, for keystone-tls-public and trilio-ca-cert. They are harmless here: those secrets are only used for Ingress TLS, which app\_gateway.yaml turns off.

ii] The script syncs the nova-compute init script into the datamover templates, which consumes placeholders in templates/bin/. Before re-running it, restore them with git checkout -- ../templates/bin/.

Verify that the credentials file is created:

```
cat ../values_overrides/admin_creds.yaml
cat ../templates/bin/_triliovault-nova-compute.conf.tpl
```

### 9] Configure Ceph Storage (if used as Nova/Cinder Backend)

If your setup uses Ceph as the storage backend for Nova/Cinder, configure Ceph settings for Trilio.

#### 9.1] Manual Approach

**9.1.1] Edit the Ceph configuration file:**

```
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/values_overrides/
## Provide rbd_user, keyring. This user needs to have read,write access on vms, volumes pool used for nova, cinder backend.
## By default 'nova' user generally has these permissions. But we recommend to verify and use it for triliovault. 
vi ceph.yaml

## Copy your /etc/ceph/ceph.conf content to following file. Clean existing file content.
vi ../templates/bin/_triliovault-ceph.conf.tpl
```

a) Set rbd\_user and keyring (the user should have read/write access to the Nova/Cinder pools).\
b) By default, the cinder/nova user usually has these permissions, but it’s recommended to verify.

**9.1.2] Copy the contents of /etc/ceph/ceph.conf into the appropriate Trilio template file:**

```
vi ../templates/bin/_triliovault-ceph.conf.tpl
```

#### 9.2] Automated Approach

**9.2.1] Run the Ceph configuration script:**

```
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/utils
./get_ceph.sh
```

**9.2.2] Verify that the output is correctly written to:**

```
cat ../values_overrides/ceph.yaml
cat ../templates/bin/_triliovault-ceph.conf.tpl
```

### 10] Create Docker Image Pull Secret

This creates the triliovault-image-registry secret in the trilio-openstack and openstack namespaces. The Horizon plugin step uses it too.

```
./create_image_pull_secret.sh <TRILIO_REGISTRY_USERNAME> <TRILIO_REGISTRY_PASSWORD>
```

Verify that the secret has been created successfully:

```
kubectl describe secret triliovault-image-registry -n trilio-openstack
kubectl describe secret triliovault-image-registry -n openstack
```

### 11. Install Trilio for OpenStack Helm Chart

#### 11.1] Review the Installation Script

**11.1.1] Open the `install.sh` Script**

The `install.sh` script installs the Trilio Helm chart in the `trilio-openstack` namespace.

```
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/utils/
vi install.sh
```

**11.1.2] Select the Appropriate OpenStack Helm Version**

Use the correct YAML file based on your OpenStack Helm Version:

* Antelope → `2023.1.yaml`
* Bobcat (Default)→ `2023.2.yaml`
* Gazpacho - `2026.1.yaml`

**11.1.3] Validate `values_overrides` Configuration**

Ensure the correct configurations are used:

* Disable Ceph in `ceph.yaml` if not applicable.
* Remove `tls_public_endpoint.yaml` if TLS is unnecessary.

**11.1.4] Validate ingress.yaml/app\_gateway.yaml Configuration**

*Only for OpenStack-Helm 2026.1*

Replace `--values=./trilio-openstack/values_overrides/ingress.yaml` with `--values=./trilio-openstack/values_overrides/app_gateway.yaml`

#### 11.2] Run the Installation Script

Execute the installation:

```
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/utils/
./install.sh
```

#### 11.3] Configure DNS for Public Endpoints

**11.3.1] Retrieve Ingress External IP**

```
kubectl get service -n openstack | grep LoadBalancer
```

Example Output:

```
public-openstack      LoadBalancer   10.105.43.185    192.168.2.50   80:30162/TCP,443:30829/TCP
```

**OpenStack-Helm 2026.1**

For OpenStack-Helm 2026.1 Gazpacho, change two --values lines in utils/install.sh before installing:

Replace "--values=./trilio-openstack/values\_overrides/2023.2.yaml" with "--values=./trilio-openstack/values\_overrides/2026.1.yaml"

Replace "--values=./trilio-openstack/values\_overrides/ingress.yaml" with "--values=./trilio-openstack/values\_overrides/app\_gateway.yaml"

**Note:** for an OpenStack-Helm 2026.1 cloud that has not yet migrated to Application Gateway (still on NGINX Ingress), use ingress.yaml instead of app\_gateway.yaml.

```
vi install.sh
```

Leave every other --values line as it is.

2026.1.yaml sets the T4O images for OpenStack-Helm 2026.1.

app\_gateway.yaml publishes the T4O WLM and Datamover APIs through the OpenStack-Helm 2026.1 Application Gateway. It creates two Gateway API HTTPRoutes attached to openstack/app-gateway, instead of Ingress objects. An OpenStack-Helm 2026.1 cloud that has migrated to Application Gateway has no Ingress controller, so Ingress objects would never be served.

Check that the cloud is on Application Gateway:

```
kubectl get gateway -A                             # copy namespace                              
kubectl -n <NAMESPACE> get gateway app-gateway     # PROGRAMMED = True
kubectl get ingressclass                           # No resources found
```

```
./install.sh
```

The script waits for all trilio-openstack pods to reach the Running state.

**Note:** Image Pull Policy: if you see ImagePullBackOff, edit your override file and change pullPolicy from IfNotPresent to Always.

Verify the public endpoints (OpenStack-Helm 2026.1). Both HTTPRoutes must be accepted by the gateway:

```
kubectl -n trilio-openstack get httproute
kubectl -n trilio-openstack describe httproute | grep -E "Type:|Status:"     # Accepted=True, ResolvedRefs=True
```

Make sure triliovault-wlm.\<public\_domain\_name> and triliovault-datamover.\<public\_domain\_name> resolve to the app-gateway external IP, the same IP as the other OpenStack public endpoints:

```
kubectl -n <NAMESPACE> get svc app-gateway
Example: kubectl -n envoy-gateway-system get svc  envoy-gateway
```

### 12] Verify Installation

**12.1] Check Helm Release Status**

```
helm status trilio-openstack
```

**12.2] Validate Deployed Containers**

Ensure correct image versions are used by checking container tags or SHA digests.

**12.3] Verify Pod Status**

```
kubectl get pods -n trilio-openstack
```

Example Output:

```
NAME                                                 READY   STATUS      RESTARTS   AGE
rabbitmq-server-0                                    1/1     Running     0          3d
triliovault-datamover-api-79cc455759-7sjzt           1/1     Running     0          2d23h
triliovault-datamover-api-79cc455759-bxjgk           1/1     Running     0          2d23h
triliovault-datamover-api-79cc455759-gcrq5           1/1     Running     0          2d23h
triliovault-datamover-db-init-b9cnh                  0/1     Completed   0          2d23h
triliovault-datamover-db-sync-qh8h2                  0/1     Completed   0          2d23h
triliovault-datamover-ks-endpoints-nw5f4             0/3     Completed   0          2d23h
triliovault-datamover-ks-service-np282               0/1     Completed   0          2d23h
triliovault-datamover-ks-user-n6cqc                  0/1     Completed   0          2d23h
triliovault-datamover-openstack-compute-node-d56c2   1/1     Running     0          2d23h
triliovault-datamover-openstack-compute-node-s6fh4   1/1     Running     0          2d23h
triliovault-datamover-rabbit-init-9gxrs              0/1     Completed   0          2d23h
triliovault-dms-697d7b545d-n62hj                     1/1     Running     0          2d23h
triliovault-dms-697d7b545d-ptv48                     1/1     Running     0          2d23h
triliovault-dms-697d7b545d-s6cpz                     1/1     Running     0          2d23h
triliovault-dms-openstack-compute-node-q9mcd         1/1     Running     0          2d23h
triliovault-dms-openstack-compute-node-vzgcn         1/1     Running     0          2d23h
triliovault-wlm-api-6d74b545d6-f4bt7                 1/1     Running     0          2d23h
triliovault-wlm-api-6d74b545d6-fhtmc                 1/1     Running     0          2d23h
triliovault-wlm-api-6d74b545d6-t7p7p                 1/1     Running     0          2d23h
triliovault-wlm-cron-75b7b6bbf8-xj987                1/1     Running     0          2d23h
triliovault-wlm-db-init-n7n9g                        0/1     Completed   0          2d23h
triliovault-wlm-db-sync-zf67b                        0/1     Completed   0          2d23h
triliovault-wlm-ks-endpoints-ccgfc                   0/3     Completed   0          2d23h
triliovault-wlm-ks-service-222h6                     0/1     Completed   0          2d23h
triliovault-wlm-ks-user-wdt5k                        0/1     Completed   0          2d23h
triliovault-wlm-rabbit-init-mnssq                    0/1     Completed   0          2d23h
triliovault-wlm-scheduler-55d6696497-x86dt           1/1     Running     0          2d23h
triliovault-wlm-workloads-7844db69-48k9x             1/1     Running     0          2d23h
triliovault-wlm-workloads-7844db69-698gp             1/1     Running     0          2d23h
triliovault-wlm-workloads-7844db69-n8r8b             1/1     Running     0          2d23h
```

**12.4] Check Job Completion**

```
kubectl get jobs -n trilio-openstack
```

Example Output:

```
NAME                                 STATUS     COMPLETIONS   DURATION   AGE
triliovault-datamover-db-init        Complete   1/1           4s         3d
triliovault-datamover-db-sync        Complete   1/1           9s         3d
triliovault-datamover-ks-endpoints   Complete   1/1           14s        2d23h
triliovault-datamover-ks-service     Complete   1/1           8s         2d23h
triliovault-datamover-ks-user        Complete   1/1           17s        2d23h
triliovault-datamover-rabbit-init    Complete   1/1           4s         2d23h
triliovault-wlm-db-init              Complete   1/1           4s         3d
triliovault-wlm-db-sync              Complete   1/1           21s        2d23h
triliovault-wlm-ks-endpoints         Complete   1/1           14s        2d23h
triliovault-wlm-ks-service           Complete   1/1           7s         2d23h
triliovault-wlm-ks-user              Complete   1/1           18s        2d23h
triliovault-wlm-rabbit-init          Complete   1/1           4s         2d23h
```

Trilio-OpenStack Helm Chart Installation is Done!

Logs:

1] triliovault-datamover-api service logs.

Logs available on kubernetes nodes

```
kubectl get nodes --show-labels | grep triliovault-control-plane
-- SSH to these kubernetes nodes
ssh <KUBERNETES_NODE_NAME>
-- See logs
vi /var/log/triliovault-datamover-api/triliovault-datamover-api.log
## Other approach: kubectl stdout and stderr logs
-- List triliovault-datamover-api pods
kubectl get pods | grep triliovault-datamover-api
-- See logs
kubectl logs <triliovault-datamover-api-pod-name>
# Example:
root@helm1:~# kubectl get pods | grep triliovault-datamover-api
triliovault-datamover-api-c87899fb7-dq2sd            1/1     Running     0          3d18h
triliovault-datamover-api-c87899fb7-j4fdz            1/1     Running     0          3d18h
triliovault-datamover-api-c87899fb7-nm8pt            1/1     Running     0          3d18h
root@helm1:~# kubectl logs triliovault-datamover-api-c87899fb7-dq2sd
```

2] triliovault-datamover service logs

Logs available on kubernetes nodes

```
kubectl get nodes --show-labels | grep openstack-compute-node
-- SSH to these kubernetes nodes
ssh <KUBERNETES_NODE_NAME>
-- See logs
vi /var/log/triliovault-datamover/triliovault-datamover.log
## Other approach: kubectl stdout and stderr logs
-- List triliovault-datamover-api pods
kubectl get pods | grep triliovault-datamover-openstack
-- See logs
kubectl logs <triliovault-datamover-pod-name>
# Example:
root@helm1:~# kubectl get pods | grep triliovault-datamover-openstack
triliovault-datamover-openstack-compute-node-2krmj   1/1     Running     0          3d19h
triliovault-datamover-openstack-compute-node-9f5w7   1/1     Running     0          3d19h
root@helm1:~# kubectl logs triliovault-datamover-openstack-compute-node-2krmj
```

3] triliovault-wlm-api, triliovault-wlm-cron, triliovault-wlm-scheduler, triliovault-wlm-workloads services logs

Logs available on Kubernetes nodes

```
kubectl get nodes --show-labels | grep triliovault-control-plane
-- SSH to these Kubernetes nodes
ssh <KUBERNETES_NODE_NAME>
-- Log files are available in following directory.
ls /var/log/triliovault-wlm/
## Sample command output
root@helm4:~# ls -ll /var/log/triliovault-wlm/
total 26576
-rw-r--r-- 1 42424 42424  2079322 Mar 20 07:55 triliovault-wlm-api.log
-rw-r--r-- 1 42424 42424 25000088 Mar 20 00:41 triliovault-wlm-api.log.1
-rw-r--r-- 1 42424 42424    12261 Mar 16 12:40 triliovault-wlm-cron.log
-rw-r--r-- 1 42424 42424    10263 Mar 16 12:36 triliovault-wlm-scheduler.log
-rw-r--r-- 1 42424 42424    87918 Mar 16 12:36 triliovault-wlm-workloads.log
## Other approach: kubectl stdout and stderr logs
-- List triliovault-wlm services pods
kubectl get pods | grep triliovault-wlm
-- See logs
kubectl logs <triliovault-wlm-service-pod-name>
# Example:
root@helm1:~# kubectl get pods | grep triliovault-wlm
triliovault-wlm-api-7b956f7b8-84gtw                  1/1     Running     0          3d19h
triliovault-wlm-api-7b956f7b8-85mdk                  1/1     Running     0          3d19h
triliovault-wlm-api-7b956f7b8-hpcpt                  1/1     Running     0          3d19h
triliovault-wlm-cloud-trust-rdh8n                    0/1     Completed   0          3d19h
triliovault-wlm-cron-78bdb4b959-wzrfs                1/1     Running     0          3d19h
triliovault-wlm-db-drop-dhfgj                        0/1     Completed   0          3d19h
triliovault-wlm-db-init-snrsr                        0/1     Completed   0          3d19h
triliovault-wlm-db-sync-wffk5                        0/1     Completed   0          3d19h
triliovault-wlm-ks-endpoints-zvqtf                   0/3     Completed   0          3d19h
triliovault-wlm-ks-service-6425q                     0/1     Completed   0          3d19h
triliovault-wlm-ks-user-fmgsx                        0/1     Completed   0          3d19h
triliovault-wlm-rabbit-init-vsdn6                    0/1     Completed   0          3d19h
triliovault-wlm-scheduler-649b95ffd6-bkqxt           1/1     Running     0          3d19h
triliovault-wlm-workloads-6b98679d45-2kjdq           1/1     Running     0          3d19h
triliovault-wlm-workloads-6b98679d45-mxvhp           1/1     Running     0          3d19h
triliovault-wlm-workloads-6b98679d45-v4dn8           1/1     Running     0          3d19h
# kubectl logs triliovault-wlm-api-7b956f7b8-84gtw
# kubectl logs triliovault-wlm-cron-78bdb4b959-wzrfs
# kubectl logs triliovault-wlm-scheduler-649b95ffd6-bkqxt
# kubectl logs triliovault-wlm-workloads-6b98679d45-mxvhp
```

### 13] Create Cloud Admin Trust

**NOTE: This step is required only for OpenStack-Helm 2026.1 Gazpacho release**

OpenStack-Helm 2026.1 uses a admin username, so read it from your OpenRC file when you create the trust.

```
# Get the name of the WLM API Pod
WLM_POD=$(kubectl get pods -n trilio-openstack -l component=wlm-api -o jsonpath="{.items[0].metadata.name}")

# Execute into the pod
kubectl exec -it -n trilio-openstack $WLM_POD -- bash

# Force internal routing and source credentials
export OS_ENDPOINT_TYPE=internal
source /tmp/admin-openrc.sh

# Create the cloud Trust
workloadmgr --insecure trust-create --is_cloud_trust True admin
```

**Note:** If the public \*.\<public\_domain\_name> names usually cannot be resolved inside the cluster. If you get HTTPSConnectionPool(host='keystone.\<public\_domain>' …): Name or service not known, point the CLI at the internal Keystone endpoint after sourcing the OpenRC file:

```
export OS_AUTH_URL=<OS_AUTH_URL>
export OS_INTERFACE=internal
export OS_ENDPOINT_TYPE=internalURL
```

### 14] Add Backup Targets

To add a new backup target, refer to the [Add a new backup target](https://docs.trilio.io/openstack/admin-guide/backup-targets/add-a-backup-target.md).

### 15] Install Trilio for OpenStack Horizon Plugin <a href="#install-trilio-horizon" id="install-trilio-horizon"></a>

**(For releases earlier than OpenStack-Helm 2026.1 Gazpacho release)**

Below are the steps to patch the Horizon deployment in an OpenStack Helm setup to install the **Trilio Horizon Plugin**.

#### 15.1] Pre-requisites

* Horizon is deployed via OpenStack Helm and is running in the `openstack` namespace.
* Docker registry secret `triliovault-image-registry` must already exist in the `openstack` namespace from the steps performed during Trilio Installation.

```
kubectl describe secret triliovault-image-registry -n openstack
```

* If not already created, follow this command:

```
kubectl create secret docker-registry triliovault-image-registry \
  --docker-server="docker.io" \
  --docker-username=<TRILIO_REGISTRY_USERNAME> \
  --docker-password=<TRILIO_REGISTRY_PASSWORD> \
  -n openstack
```

#### 15.2] Patch Horizon Deployment

Use the command below to patch the Horizon deployment with the **Trilio Horizon Plugin** image. Update the image tag as needed for your release.

```
kubectl -n openstack patch deployment horizon \
  --type='strategic' \
  -p '{
    "spec": {
      "template": {
        "spec": {
          "containers": [
            {
              "name": "horizon",
              "image": "docker.io/trilio/trilio-horizon-plugin-helm:<TRILIOVAULT_HORIZON_PLUGIN_IMAGE_TAG>"
            }
          ],
          "imagePullSecrets": [
            {
              "name": "triliovault-image-registry"
            }
          ]
        }
      }
    }
  }'
```

**Install Trilio Horizon Plugin (for OpenStack-Helm 2026.1 Gazpacho release)**

Use the install\_horizon\_plugin.sh script in utils/. It pre-pulls the private plugin image on all openstack-control-plane nodes, using a short-lived DaemonSet and the triliovault-image-registry secret.

It upgrades the Horizon chart through HORIZON\_CHART.

Checks that the Trilio panels are enabled.

```
cd triliovault-cfg-scripts/openstack-helm/trilio-openstack/utils/
HORIZON_CHART=<path to the horizon chart> \
  ./install_horizon_plugin.sh docker.io/trilio/trilio-horizon-plugin-helm:<TRILIOVAULT_HORIZON_PLUGIN_IMAGE_TAG>
# example:
# HORIZON_CHART=/opt/openstack-helm/horizon ./install_horizon_plugin.sh docker.io/trilio/trilio-horizon-plugin-helm:6.2.1-test-2026.1
```

It ends with:

```
Trilio Horizon plugin installed (9 panel files enabled in horizon-...).
```

Log out of Horizon and log in again. The Backups tab appears under Project, and Backups-Admin under Admin.

#### 15.3] Verification Horizon pods

After patching:

1. Ensure the Horizon pods are restarted and running with the new image:

```
kubectl get pods -n openstack -l application=horizon,component=server -o jsonpath="{.items[*].spec.containers[*].image}" | tr ' ' '\n'
```

2. Access the Horizon dashboard and verify the **TrilioVault** section appears in the UI.

### 16] Apply License

Log into the Horizon UI as the cloud admin and go to the TrilioVault License tab. Upload your tvault\_license.lic file and accept the EULA to activate the product.
