-
Secrets and certificates — for the ones you couldn't eliminate
Eighteen articles deleting secrets. But "fewer" isn't "none." Some secrets must exist — a third-party API key, a legacy DB password, a signing key you own. For those, and for certificates, there's an order of preference most teams…
Secrets & certificatesKubernetesWorkload identityGitOpsNetwork policy
-
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
-
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
-
Sidecar to ambient — what gets cheaper, what just moves house
"Sidecarless mesh, zero downtime" is a half-truth — and the missing half is exactly the one a regulated cluster cares about.
Ambient meshService meshMicrosoft Entra IDmTLSAuthorizationPolicy
-
Disaster recovery for a regulated mesh — recovering the proof, not just the app
A regional outage takes your primary cluster offline at 03:10. By 03:40 the platform team has a cluster in the paired region, Argo CD has reconciled the application manifests, and the dashboards are green. At 09:00 the ICT risk…
Compliance evidenceIstioDisaster recoveryGitOpsWorkload identity
-
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…