Kubernetes operators
5 articles in The Mesh Series by Arshad Badar Khan cover Kubernetes operators.
Filter with other topics-
Upgrading Istio without a control‑failure event — the traffic shift that is not a mutation
Istio 1.31.1 fixes GHSA‑qm8v‑g4f9‑qhjx: a BackendTLSPolicy that quietly reverts to plaintext when its CA reference fails to resolve. The control that encrypts was, under one specific failure, not encrypting. You read the advisory…
-
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
-
Designing the ComplianceProfile operator — compliance is a reconcile loop with a different noun
You have a PeerAuthentication that says STRICT. You have a Gatekeeper constraint that says every namespace must carry a default‑deny AuthorizationPolicy . You have Envoy access logs with SPIFFE identities, signed evidence packs…
Kubernetes operatorsCompliance evidencePolicy as code.NET & C#Supply-chain signing
-
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…
-
Shipping continuous evidence as a product — a report is something you send; evidence is something an auditor comes and takes
The ComplianceProfile status says Satisfied. It is signed. It is in the cluster. An external auditor from the FMA's appointed firm arrives, and the first thing she does is decline the dashboard, decline the kubectl session, and…
Compliance evidenceSupply-chain signing.NET & C#Kubernetes operatorsMicrosoft Entra ID