Validated Patterns

Architecture

This page describes component schematics, connectivity overview diagrams, and TLS/CA handling for each install variant. For hub-to-managed network paths and ports, see Connectivity.

Architecture diagrams

Each install variant has a full hub/spoke schematic exported as PNG from draw.io source. PNG and draw.io files live in static/images/ramendr-starter-kit/.

DiagramVariantPNGdraw.io source

ramendr-architecture-odf

odf

ramendr-architecture-odf.png

ramendr-architecture-odf.drawio

ramendr-architecture-drpartner-s4

drpartner-s4

ramendr-architecture-drpartner-s4.png

ramendr-architecture-drpartner-s4.drawio

ramendr-architecture-drpartner-minimal

drpartner-minimal

ramendr-architecture-drpartner-minimal.png

ramendr-architecture-drpartner-minimal.drawio

hub-managed-connectivity

All variants

hub-managed-connectivity-odf.png (and per-variant tabs)

hub-managed-connectivity.drawio

odf schematic

Full hub/spoke schematic. DRPolicies live on the hub with the RamenDR Hub Operator and become volume replications and volume group replications on the managed clusters. The hub operator orchestrates the RamenDR Cluster Operators, which manage those replications plus OpenShift Data Foundation and OpenShift ADP (Kubernetes object backups), along with Submariner and Edge GitOps VMs.

RamenDR architecture for the odf variant
Figure 1. RamenDR Starter Kit architecture (odf)

drpartner-s4 schematic

Hub S4 Object store for OpenShift ADP Kubernetes object backups. Partner CSI on the managed clusters provides VM data replication. DRPolicies live on the hub and become volume replications and volume group replications on the managed clusters. The RamenDR Hub Operator orchestrates the cluster operators. The pattern does not create DRPC or VMs.

RamenDR architecture for the drpartner-s4 variant
Figure 2. RamenDR Starter Kit architecture (drpartner-s4)

drpartner-minimal schematic

Red Hat Advanced Cluster Management (RHACM) and partner operators only. S3-compatible storage for OpenShift ADP is bring-your-own; this variant does not deploy S4. DRPolicies live on the hub and become volume replications and volume group replications on the managed clusters. The pattern does not create DR CRs.

RamenDR architecture for the drpartner-minimal variant
Figure 3. RamenDR Starter Kit architecture (drpartner-minimal)

TLS and CA (current implementation)

Certificate handling is delivered by external charts deployed via Argo CD, not local policy YAML in the pattern repository.

ChartRole

vp-manage-proxy-cluster-ca

Differential CA bundle for cluster API/ingress CAs (all variants)

opp-policy-chart

s3CaInjector injects caCertificates on Ramen s3StoreProfiles (odf, drpartner-s4)

Chart overrides live in the pattern repository:

Manual CA and cluster helpers live under scripts/ in the pattern repository. Verify resource names against the live cluster before using examples that reference RHACM policy names.