Yugabytedb K8S Submariner

Connect two Kubernetes clusters with Submariner (broker, gateway, Lighthouse service discovery) and deploy one independent YugabyteDB universe per cluster with the yugabyte Helm chart, so the universes can be joined with xCluster replication (source -> target / DR). Covers kind cluster configs with non-overlapping CIDRs, subctl deploy-broker / join (clusterid, cable driver, NAT-T, gateway labelling), Helm values (multicluster.createServiceExports, kubernetesClusterId, masterAddresses, totalMasters), svc.clusterset.local DNS checks, subctl verify/diagnose, and yb-admin xCluster setup. Use when the user mentions Submariner or Lighthouse with YugabyteDB, subctl with yb-masters / yb-tservers, xCluster between Kubernetes clusters without a shared CNI mesh, or clusterset.local addresses with Submariner. For Cilium Cluster Mesh use yugabytedb-k8s-cilium. Does NOT cover the YugabyteDB Kubernetes Operator or YBA-managed DR (use yb-k8s-operator), or a single universe stretched across clusters.

srinivasa-vasu Updated

File contents

srinivasa-vasu/agent-skills commit 3193e3f170

Frequently asked questions

npx get-skill add srinivasa-vasu/yugabytedb-k8s-submariner