… This is where Policy as Code becomes powerful: by applying policies, we can not only enforce these standards but also observe, measure, and understand their impact across the platform. apiVersion: apps/v1 kind: Deployment metadata: name: good-app namespace: default spec: replicas: 2 selector: match… …
… Every policy change is traceable. Every deployment decision is auditable. At that point, sovereignty stops being a process and becomes a platform capability. …
… Looking further ahead, the enforcement locus model could evolve into a multi-agent pipeline—where lightweight browser-based agents handle review-time feedback, and deeper reasoning agents operate asynchronously to analyze policy trends across PRs, flag systemic drift, and proactively suggest policy… …
… The work that actually matters—drift detection, coordinated updates, and disaster recovery automation—happens in the wiring. That’s where your platform either survives its second year or just becomes a collection of tools you stop trusting.
… The SDK and collector could then implement the same policy differently based on their capabilities. Andy expects additional SDKs to support OpAMP, expanding remote management capabilities to more languages and platforms. …
… That makes the boundary a property of the architecture, not a policy we hope the application respects. …
… Rich policy integration : Combine L7 routing with Cilium Network Policies and Hubble observability. …
… Key platform updates: Kubernetes Support: Officially validated for Kubernetes 1.34+. …
Posted on May 13, 2026 by Erick Bourgeois, Director & Head of Kubernetes Platform Engineering, RBC Capital Markets CNCF projects highlighted in this post As we shared in our earlier post on FluxCD , RBC Capital Markets has been on a deliberate journey to modernize our Kubernetes platform. …
… AI governance itself is thinner: prompt inspection, agent discovery, tool-call policy. …