Data & streaming

MirrorMaker 2

DR-only

Cross-cluster Kafka replication — runs on DR, pulls from DC.

Quick facts

Topology
Kafka Connect distributed, 2 pods
Direction
DC → DR
Managed by
Strimzi KafkaMirrorMaker2 CR on DR

What it is

MM2 runs only on DR by design — it pulls from DC's bootstrap and writes into the local DR Kafka. This is the carrier for the Redis WAL pattern (ADR-0018): app writes go to DC Redis, are journaled to DC Kafka, replicated by MM2 to DR Kafka, then applied to DR Redis by redis-applier.

Architecture

Add diagrams or topology notes here — how this component sits relative to DC/DR, what replicates, and what speaks to it. Mermaid blocks render as plain text today; embed images under /assets/ when needed.

Configuration

Add chart values overrides, important env vars, OIDC client config, secret references. Link to the source files in infra/gitops-rke2 rather than copying YAML wholesale — the repo is the source of truth.

Operations

Add runbook notes: backup, restore, common troubleshooting, dashboards, on-call cheatsheet entries.

Failover

Add DC/DR cutover/cutback notes: edge HAProxy backend name, healthcheck path, measured cutover/cutback times, smoke-test commands.

References