Skip to main content
This page covers the OpenShift-specific bits. The actual Helm install (values, ingress, env vars) lives in Install with Helm.

​
Persistent storage

The shared RWX PVC (used by prismeai-functions) must be backed by CephFS (via OpenShift Data Foundation) or NFS, with the right RWX storage class set on the PVC.

​
Security Context Constraints (SCCs)

OpenShift restricts container privileges by default. Apply (or grant) an SCC compatible with running the platform images as non-root:
  • restricted-v2 works for most services if the chart’s default securityContext.runAsUser is honored.
  • prismeai-functions forks isolated child processes; review its SCC requirements with Prisme.ai before granting elevated privileges.
Make sure the service account used by each Helm release is bound to the appropriate SCC.

​
Routes vs Ingress

Prisme.ai’s chart ships Kubernetes Ingress resources by default. On OpenShift you have two options:
  1. Keep Ingress: OpenShift’s Ingress Operator translates them to Routes automatically.
  2. Use Routes directly: disable the chart’s Ingress and create two Routes (api, studio) with TLS edge termination and a haproxy.router.openshift.io/timeout: 300s annotation to keep SSE / websocket connections alive.

​
DNS and TLS

Create two records:
Certificate covering both, managed by cert-manager or imported as a Route TLS secret.

​
Next Steps

Install with Helm

Configure values and deploy core + apps namespaces.

Databases

PostgreSQL or MongoDB, Redis, Elasticsearch or OpenSearch.

Install products

Fresh-install walkthrough.

Migration v27

Migrate an existing instance to v27.