> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensormesh.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Install in SUSE AI Factory with NVIDIA

> Run Tensormesh Platform on SUSE Rancher Prime + RKE2 (SLES) for SUSE AI Factory — supported versions and platform notes.

Tensormesh Platform runs on SUSE — SUSE Rancher managing RKE2 on SUSE
Linux Enterprise Server — the same way it does on vanilla Kubernetes. Unlike OpenShift,
RKE2 permits the `hostIPC` the cache engine needs out of the box, so **no security overlay
is required**.

> [!NOTE]
>
> Read this **after** [Install with Helm](/v1.0.1/installation/helm). This page adds the
> SUSE-specific platform notes; it does not replace the Helm install steps.

## Supported SUSE platform

Tensormesh supports **SUSE AI Factory** on SUSE Rancher Prime–managed RKE2. Validated on:

| Component | Supported version |
| - | - |
| Platform | SUSE AI Factory with NVIDIA |
| SUSE Linux Enterprise Server | 15 SP6 |
| SUSE Rancher Prime | 2.14.3 |
| RKE2 | `v1.35.6+rke2r1` |
| Storage | Longhorn (SUSE Storage) — ReadWriteMany |
| GPU | NVIDIA (validated on L4) |

Tensormesh tracks the latest supported RKE2 and SUSE Rancher Prime versions per the
[SUSE Rancher Prime support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/latest/).
The operator, cache engine, and Helm chart are supported as a matched set — deploy a single
row from the [compatibility matrix](/v1.0.1/installation/compatibility) together.

## Why SUSE needs no extra config

Engine pods request `hostIPC` so the LMCache cache server can share memory with the vLLM
worker processes outside the pod. RKE2's default [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/)
profile is `privileged`, which permits `hostIPC` — so the engine pod starts with no
OpenShift-style SecurityContextConstraint and no `openshift.enabled` flag.

> [!NOTE]
>
> You only need to act if you have **hardened the target namespace to the `baseline` or
> `restricted` PSA level**. In that case either label the namespace
> `pod-security.kubernetes.io/enforce=privileged`, or run the cache in colocated (sidecar)
> mode, which needs no `hostIPC`.

## Prerequisites

* An **RKE2 cluster managed by SUSE Rancher Prime** (the supported versions above).
* **GPU-enabled node(s).** Set up the NVIDIA GPU stack on the cluster first — the driver,
  the containerd runtime integration, and the device plugin — following NVIDIA's guidance for
  RKE2 (for example, the NVIDIA GPU Operator). This is a platform prerequisite, independent of
  Tensormesh; on SLES, match the driver to the running kernel. The cache engine schedules only
  on nodes labeled `nvidia.com/gpu.present=true`.
* A **ReadWriteMany StorageClass** for the shared model hub — **Longhorn (SUSE Storage)** works
  out of the box (install `open-iscsi` on every node first).

## Install

Install with Helm exactly as on vanilla Kubernetes — pin **explicit image tags** (never `latest`):

```bash theme={null}
helm install tensormesh-operator \
  oci://artifacts.tensormesh.ai/tensormesh-production/charts/tensormesh-operator \
  --version <version> \
  --namespace tensormesh-operator --create-namespace \
  --wait
```

> [!NOTE]
>
> The chart is distributed through a private registry. Request an access token from the
> Tensormesh team, then authenticate before installing — see
> [Install with Helm](/v1.0.1/installation/helm#quick-install).

## Verify

```bash theme={null}
# Nodes are SUSE Linux Enterprise + RKE2
kubectl get nodes -o custom-columns=\
'NODE:.metadata.name,OS:.status.nodeInfo.osImage,KUBERNETES:.status.nodeInfo.kubeletVersion'

# The cache engine pod is Running (hostIPC is allowed by default on RKE2)
kubectl get pods -n tensormesh-operator \
  -l app.kubernetes.io/component=cache-engine
```

## Commercial support

Tensormesh provides commercial support for Tensormesh Platform on the SUSE Rancher Prime and RKE2
versions listed above. Contact the Tensormesh team for support terms.

## Next steps

> **[Helm install reference](/v1.0.1/installation/helm)**
>
> Full install, upgrade, and uninstall flow.

> **[Compatibility matrix](/v1.0.1/installation/compatibility)**
>
> The matched operator / cache engine / chart version set.

> **[Troubleshooting](/v1.0.1/installation/troubleshooting)**
>
> Engine scheduling, GPU, and permission diagnostics.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.