Skip to main content
The Tensormesh Operator runs on the SUSE platform — 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.
Read this after Install with Helm. This page adds the SUSE-specific platform notes; it does not replace the Helm install steps.

​
Supported SUSE platform

Tensormesh supports SUSE AI on SUSE Rancher–managed RKE2. Validated on: Tensormesh tracks the latest supported RKE2 and SUSE Rancher versions per the SUSE Rancher support matrix. The operator, cache engine, and Helm chart are supported as a matched set — deploy a single row from the compatibility matrix 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 profile is privileged, which permits hostIPC — so the engine pod starts with no OpenShift-style SecurityContextConstraint and no openshift.enabled flag.
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 (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):
The chart is distributed through a private registry. Request an access token from the Tensormesh team, then authenticate before installing — see Install with Helm → Install.

​
Verify

​
Commercial support

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

​
Next steps

Helm install reference

Full install, upgrade, and uninstall flow.

Compatibility matrix

The matched operator / cache engine / chart version set.

Troubleshooting

Engine scheduling, GPU, and permission diagnostics.

Cache sizing

Simulate the hit rate and right-size the L1/L2 cache for your workload — including memory-constrained GPUs.