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

# OpenShift (ROSA) Deployment | Collate Kubernetes Guide

> Deploy Collate on Red Hat OpenShift Service on AWS (ROSA) using Argo Workflows for ingestion orchestration, with full Helm chart configuration reference.

# OpenShift (ROSA) Deployment

This guide covers deploying Collate on **AWS ROSA (Red Hat OpenShift Service on AWS)**. ROSA differs from standard EKS in three key ways: Security Context Constraints (SCC) replace Pod Security Admission, OpenShift Routes replace Ingress, and ROSA includes a built-in OIDC provider for IRSA.

<Note>
  The Collate Helm chart supports any OpenShift 4.14+ cluster — not just ROSA. The AWS-specific sections (IRSA, ECR, S3, RDS) use ROSA as the reference example. If you are running self-managed OpenShift on-premises or on another cloud, skip the AWS prerequisite sections and substitute your own infrastructure (registry, object storage, database, secrets management). The OpenShift-specific chart configuration — SCCs, Routes, security contexts, and `emptyDir` volume mounts — applies regardless of where the cluster runs.
</Note>

***

## Architecture

Collate on ROSA requires four components, each with OpenShift-specific adaptations:

1. **Collate Server** — runs as an OpenShift Deployment under the `restricted-v2` SCC
2. **Database** — MySQL 8.0.42+ or PostgreSQL 17.6+; RDS in the same VPC is recommended
3. **Search Engine** — Amazon OpenSearch Service (recommended) or in-cluster OpenSearch. ElasticSearch is not supported in Collate BYOC because Collate AI relies on OpenSearch's vector capabilities for Semantic and Hybrid Search.
4. **Argo Workflows** — orchestrates ingestion pipeline pods; requires `anyuid` SCC for its system components

ROSA-specific AWS integrations:

* **IRSA via ROSA OIDC** — pods assume IAM roles using the cluster's built-in OIDC provider (no manual setup required)
* **OpenShift Routes** — replace Kubernetes Ingress; TLS is terminated at the OpenShift router

***

## Sizing Requirements

### Node requirements

ROSA Hosted Control Plane (HCP) is recommended. Minimum 2 worker nodes, each with:

* 4 vCPUs
* 16 GiB Memory
* 128 GiB Storage

### Software requirements

| Component      | Minimum Version |
| -------------- | --------------- |
| ROSA           | 4.14+           |
| Kubernetes     | 1.27+           |
| Helm           | 3.x             |
| Argo Workflows | 3.5.4           |
| MySQL          | 8.0.42          |
| PostgreSQL     | 17.6            |
| OpenSearch     | 3.4             |

### Minimum Hardware requirements

| Component              | vCPU | Memory  | Storage | Notes                      |
| ---------------------- | ---- | ------- | ------- | -------------------------- |
| Collate Server         | 2    | 4–8 GiB | —       | Minimum 2 pods recommended |
| RDS                    | 2    | 8 GiB   | 100 GiB |                            |
| OpenSearch             | 2    | 8 GiB   | 128 GiB |                            |
| Argo Workflows runners | 2    | 8 GiB   | —       |                            |

Recommended AWS instance types: `m6i.xlarge` for worker nodes, `db.t4g.medium` for RDS, `r6g.large.search` for OpenSearch.

<Note>
  These are minimum requirements. Please reach out to support for your custom requirements.
</Note>

***

## Deployment Steps

<CardGroup cols={3}>
  <Card title="Prerequisites" icon="list-check" href="/how-to-guides/deployment/byoc/kubernetes/openshift/prerequisites">
    Set up the ROSA OIDC provider reference, S3 bucket, and required AWS resources before deploying.
  </Card>

  <Card title="Deploy Argo Workflows" icon="diagram-project" href="/how-to-guides/deployment/byoc/kubernetes/openshift/argo-workflows">
    Create IAM roles for Argo, configure SCCs, and install Argo Workflows with the OpenShift-compatible values.
  </Card>

  <Card title="Deploy Collate" icon="rocket" href="/how-to-guides/deployment/byoc/kubernetes/openshift/collate">
    Create the Collate IAM role, configure ECR credentials, and install Collate with the openmetadata Helm chart.
  </Card>
</CardGroup>