yugabytedb-k8s-ciliumlisted
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