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

# Operator Framework

> Operator Lifecycle Manager and the OperatorHub.io catalog come installed on every Kubernetes cluster, giving teams one-step access to production operators.

## 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.

<Note>
  The operator framework is delivered as a default add-on through
  [Polystack K8SaaS cluster templates](/services/kubernetes/user-guide/cluster-templates).
  Every cluster created from a platform template has it installed from its first boot.
</Note>

***

## Components

| Component | Role |
| - | - |
| **Operator Lifecycle Manager (OLM)** | Installs operators, resolves their dependencies, and manages upgrades through subscription channels |
| **OperatorHub.io catalog** | The community catalog of Kubernetes operators, available on every cluster |
| **Cluster template add-on** | Deploys OLM and the catalog automatically during cluster creation |

***

## How It Works

```mermaid theme={null}
graph LR
    TPL[Cluster Template<br/>operator framework add-on] --> CL[New Kubernetes Cluster]
    CL --> OLM[Operator Lifecycle Manager]
    CAT[OperatorHub.io Catalog] --> OLM
    OLM --> OP1[Installed Operators]
    OP1 --> WL[Managed Workloads]
```

<Steps>
  <Step title="Cluster is created from a platform template" icon="boxes-stacked">
    The cluster template includes the operator framework as a default add-on.
  </Step>

  <Step title="OLM and the catalog are deployed" icon="puzzle-piece">
    OLM is installed on the cluster and connected to the OperatorHub.io catalog.
  </Step>

  <Step title="Teams subscribe to operators" icon="download">
    Cluster users browse the catalog and subscribe to the operators they need. OLM installs
    each operator and keeps it updated on its subscribed channel.
  </Step>
</Steps>

***

## Benefits

<CardGroup cols={2}>
  <Card title="Consistent on every cluster" icon="clone" color="#bf9667">
    Every cluster starts with the same operator tooling, with no per-cluster setup.
  </Card>

  <Card title="Managed upgrades" icon="arrows-rotate" color="#bf9667">
    OLM tracks operator versions and applies upgrades through subscription channels.
  </Card>

  <Card title="Dependency resolution" icon="sitemap" color="#bf9667">
    Operators that depend on other operators or APIs are resolved and installed together.
  </Card>

  <Card title="Broad catalog" icon="store" color="#bf9667">
    The OperatorHub.io catalog covers databases, messaging, observability, and AI tooling.
  </Card>
</CardGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Runtime Vulnerability Scanning" icon="shield-halved" href="/services/ai-platform/vulnerability-scanning" color="#bf9667">
    Security components that are also deployed to every cluster automatically.
  </Card>

  <Card title="MLOps Platform" icon="diagram-project" href="/services/ai-platform/mlops" color="#bf9667">
    The AI cluster template built on this operator foundation.
  </Card>

  <Card title="Cluster Templates" icon="file-lines" href="/services/kubernetes/user-guide/cluster-templates" color="#bf9667">
    How cluster templates define the add-ons installed on new clusters.
  </Card>

  <Card title="GPU-Capable VMs and Containers" icon="server" href="/services/ai-platform/gpu-vms-and-containers" color="#bf9667">
    The GPU-enabled Kubernetes clusters the operators run on.
  </Card>
</CardGroup>