LGTM stack
10 articles in The Mesh Series by Arshad Badar Khan cover LGTM stack.
Filter with other topics-
What Regulated Enterprises Can't Ignore
You're moving your web apps to Kubernetes. The kind of apps that ran happily on Windows servers for years. Back there, authentication was almost free. They sat inside the domain, Windows-integrated auth did the quiet work, LDAP…
-
If you can’t prove it, it didn’t happen — audit logging in the mesh
Your service mesh is already logging every request. Method, path, status code — for free.
-
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
-
Tracing identity through a request
You turned on distributed tracing. Grafana draws the pretty waterfall. You feel covered.
Distributed tracingLGTM stackCompliance evidenceIstioOpenTelemetry
-
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
-
Continuous posture and drift — proving the control is still holding
Your admission controller said yes to the policy six months ago. Is the policy still there?
Drift & posturePolicy as codeCompliance evidenceGitOpsLGTM stack
-
One detection pipeline, four confession clocks — incident reporting across DORA, NIS2, CERT-In and DPDP
In Article 37 a red team walked through an allow rule that was too wide, and the mesh logged every step of it. The debrief is going well. Then someone from legal asks the question that ends the good mood: when did we become aware?
-
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
-
Building a Kubernetes operator in C# — Kubernetes has no opinion about Go
The platform team reviews the Article 43 design and says, kindly, that operators are written in Go. Kubebuilder, controller‑runtime, the Operator SDK, the language the API server itself is written in. They are not wrong about the…