← ClaudeAtlas

yugabytedb-k8s-ciliumlisted

Set up a Cilium Cluster Mesh with Multi-Cluster Services (MCS-API) between two Kubernetes clusters 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, cilium install with clustermesh.mcsapi, clustermesh enable/connect, Helm values (multicluster.createServiceExports, kubernetesClusterId, masterAddresses, totalMasters), svc.clusterset.local DNS checks, and yb-admin xCluster setup. Use when the user mentions Cilium Cluster Mesh with YugabyteDB, xCluster on Kubernetes across clusters, cross-cluster YugabyteDB on kind, ServiceExport/ServiceImport for yb-masters or yb-tservers, or clusterset.local addresses for YugabyteDB. Does NOT cover the YugabyteDB Kubernetes Operator or YBA-managed DR (use yb-k8s-operator), or a single universe stretched across clusters.
srinivasa-vasu/agent-skills · ★ 3 · DevOps & Infrastructure · score 60
Install: claude install-skill srinivasa-vasu/agent-skills
# YugabyteDB xCluster over a Cilium Cluster Mesh Two Kubernetes clusters (`c1` = source, `c2` = target), joined by Cilium Cluster Mesh with MCS-API. Each cluster runs its **own** universe. The mesh lets the target's tservers reach the source's masters and tservers directly, which xCluster needs: target tservers pull changes straight from source tservers, so every source pod address must be resolvable and routable from the target. ``` kind-c1 (Cilium id 1, pods 10.10/16) kind-c2 (Cilium id 2, pods 10.20/16) yb-master-0.c1.yb-masters.<ns>.svc.clusterset.local <— MCS-API —> yb-master-0.c2... yb-tserver-0.c1.yb-tservers.<ns>.svc.clusterset.local yb-tserver-0.c2... source universe ───────── xCluster ─────────> target universe ``` Bundled files (paths relative to this skill): | File | Purpose | |---|---| | `assets/kind-c1.yaml`, `assets/kind-c2.yaml` | kind clusters, no default CNI, unique pod/service CIDRs | | `scripts/mesh-up.sh` | Creates both clusters, installs Cilium, enables and connects the mesh (idempotent) | | `assets/values-c1.yaml`, `assets/values-c2.yaml` | yugabyte Helm values for each universe | | `scripts/check-mcs-dns.sh` | Checks cross-cluster DNS and TCP to every master/tserver | | `references/troubleshooting.md` | Symptoms → causes | Verified with yugabyte chart 2026.1.2, Cilium 1.20.3 (cilium-cli 0.20.x), kind 0.33. Before using with other versions, run `helm show values` and check that the keys still exist. ## In