Overview
Every Kubernetes cluster on the On-Prem AI Infrastructure Platform includes the Operator Lifecycle Manager (OLM) and the OperatorHub.io catalog. Teams install, upgrade, and manage Kubernetes operators for databases, messaging, monitoring, and AI tooling from a curated catalog, without building or maintaining deployment manifests by hand.The operator framework is delivered as a default add-on through
Polystack K8SaaS cluster templates.
Every cluster created from a platform template has it installed from its first boot.
Components
How It Works
Cluster is created from a platform template
The cluster template includes the operator framework as a default add-on.
OLM and the catalog are deployed
OLM is installed on the cluster and connected to the OperatorHub.io catalog.
Teams subscribe to operators
Cluster users browse the catalog and subscribe to the operators they need. OLM installs
each operator and keeps it updated on its subscribed channel.
Benefits
Consistent on every cluster
Every cluster starts with the same operator tooling, with no per-cluster setup.
Managed upgrades
OLM tracks operator versions and applies upgrades through subscription channels.
Dependency resolution
Operators that depend on other operators or APIs are resolved and installed together.
Broad catalog
The OperatorHub.io catalog covers databases, messaging, observability, and AI tooling.
Next Steps
Runtime Vulnerability Scanning
Security components that are also deployed to every cluster automatically.
MLOps Platform
The AI cluster template built on this operator foundation.
Cluster Templates
How cluster templates define the add-ons installed on new clusters.
GPU-Capable VMs and Containers
The GPU-enabled Kubernetes clusters the operators run on.