Multi-cluster & residency
5 articles in The Mesh Series by Arshad Badar Khan cover Multi-cluster & residency.
Filter with other topics-
The LGTM stack for compliance evidence
Loki, Grafana, Tempo, Mimir. Four letters everyone treats as one observability blob. To a regulator they answer four different questions — and putting the wrong one in the wrong store is how evidence quietly disappears.
LGTM stackCompliance evidenceDistributed tracingMulti-cluster & residencyOpenTelemetry
-
Turning telemetry into signed evidence
You have the logs. That is not the same as having evidence.
Compliance evidenceSupply-chain signingLGTM stackDrift & postureMulti-cluster & residency
-
Regional frameworks — one control surface, four rulebooks
If you run card workloads across Mumbai, Riyadh, and Dubai, you answer to RBI, SAMA, the UAE regulators, and ISO 27001 at once. The instinct is four compliance programs. That's expensive and wrong.
SAMACompliance evidenceCERT-In & DPDPRBIMulti-cluster & residency
-
Multi-cluster mesh for data residency — residency is a topology decision, not a config flag
Article 38 ended on a problem that sounds administrative and is not. Your Indian arm's CERT‑In report is due in six hours. The evidence that proves it — the access‑log lines, the signed aware‑at record, the Loki result set — must…
Multi-cluster & residencyCompliance evidenceSPIFFEAmbient meshIstio
-
What the mesh actually costs — two curves on two axes, and the one the CFO sees
The platform lead has one slide. It says the sidecar costs about 100 millicores and 128 mebibytes per pod, multiply by your pod count, and ambient makes most of that go away. Finance nods. The slide is correct. It is also the…
Ambient meshService meshFinOps & costCompliance evidenceMulti-cluster & residency