Policy as code
9 articles in The Mesh Series by Arshad Badar Khan cover Policy as code.
Filter with other topics-
Network policy and mesh policy — belt and suspenders
Your mesh AuthorizationPolicy has a blind spot: a pod without a sidecar. A DaemonSet, a node agent, a debug pod — it can open a raw socket to your ledger and the mesh never gets a vote, because the request never hit a proxy.
Network policyAuthorizationPolicyPolicy as codeSPIFFECompliance evidence
-
The policy you wrote isn’t the policy you enforce
You wrote a default-deny policy. You reviewed it. You merged it. And nothing in your cluster stops someone from deploying a workload that ignores it.
Policy as codeKubernetesAuthorizationPolicyNetwork policyCompliance evidence
-
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
-
Mapping controls to frameworks — PCI-DSS 4.0 on the mesh
"Our service mesh makes us PCI compliant." If a vendor says that, end the meeting.
PCI DSSAuthorizationPolicyCompliance evidenceDrift & posturemTLS
-
GitOps for the mesh — when the pull request becomes the change record
In a regulated shop, a merged pull request IS the change-management record. Author, reviewer, diff, timestamp — maker-checker, enforced by branch protection, mapped straight onto PCI 6.5 and ISO A.8.32.
GitOpsMicrosoft Entra IDCompliance evidenceAuthorizationPolicyDrift & posture
-
NIS2 and the Austrian NISG 2026 — when the platform is the compliance measure and the board is on the hook
Last time you mapped DORA onto the cluster and drew one box with a dashed border: governance, owned by the management body, living in GRC rather than YAML. You treated that box as somebody else's problem.
-
DORA third-party risk and the Register of Information — observed, not declared
In Article 22 you switched the mesh's outbound traffic policy to REGISTRY_ONLY and wrote a ServiceEntry for every external host a workload is allowed to reach. You called it egress control. It was also something else: the only…
Egress controlThird-party riskDORARed teaming & TLPTCompliance evidence
-
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…