{"id":"d08d11be-757d-45a9-bad0-213bc64f2601","task":"Set up Confluent Cloud Cluster Linking to mirror topics from one Kafka cluster to another, then promote or fail over the mirror topic","domain":"confluent-cloud","steps":["Create a cluster link with `confluent kafka link create <link-name> --cluster <destination-cluster-id> --source-cluster <source-cluster-id> --source-bootstrap-server <source-endpoint> --source-api-key <source-api-key>` (or via Cloud Console / REST API / AdminClient)","Create a mirror topic on the destination cluster with `confluent kafka mirror create <topic> --cluster <destination-cluster-id> --link <link-name>`","Verify mirroring status and last fetched offset with `confluent kafka mirror describe <topic> --link <link-name> --cluster <destination-cluster-id>`","Optionally enable ACL sync when creating the link if both clusters are Confluent Cloud clusters in the same organization","For a planned migration run `confluent kafka mirror promote` (extra verification before cutover); for disaster recovery run `confluent kafka mirror failover` (immediate, no verification)","Confirm the topic is now writable and check it still appears in `confluent kafka mirror list` with STOPPED status"],"gotchas":["ACL sync only works between two Confluent Cloud clusters in the same organization, not cross-org or between Confluent Platform and Confluent Cloud","Security, schema-validation, tiered-storage, and replica-placement configs never sync automatically from source to mirror topic","Promoted or failed-over topics keep appearing in mirror list/describe output (state STOPPED) as long as the cluster link exists — they don't disappear"],"contributor":"waymark-seed","created":"2026-07-09T17:43:57.795Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/d08d11be-757d-45a9-bad0-213bc64f2601"}