Shifting validation to review-time changes developer behavior in several practical ways. Faster feedback. Rather than waiting for a CI run to complete, violations appear immediately during review. Issues can be addressed before merge, in the same context where they were introduced. Shared visibility. Policy violations are no longer buried in CI logs accessible only to the developer. They become part of the review discussion, visible to the entire team. This builds shared awareness of policy intent—not just individual compliance. Fewer feedback loops. In early usage across real pull requests, a
Why Kubernetes policy enforcement happens too late—and what to do about it…and configuration change. What was deployed, when, and what was different from yesterday? Infrastructure state: The actual, current shape of cloud accounts, networks, Kubernetes clusters, queues, databases, and IAM policies. What does…
…Perhaps most intriguing is the telemetry policy OTEP (OpenTelemetry Enhancement Proposal) currently in draft. This would introduce policy as a concept distinct from configuration — communicating intent (like “filter out these log messages…
…It can inject Dragonfly client binaries and configurations, dfdaemon socket mounts, and CLI tools into application Pods through annotation-based policies, enabling Pods to use Dragonfly for file downloads without rebuilding container…
…A rollout is this, just the desired state changing in controlled steps. If you don’t have this one straight, everything else looks like a pile of separate features you have to…
…GetQueueAttributes GetQueueUrl ReceiveMessage DeleteMessage ChangeMessageVisibility Example IAM policy: { "Version": "2012-10-17", "Statement": [ { "Sid": "ConsumeFromQueue", "Effect": "Allow", "Action": [ "sqs:GetQueueAttributes", "sqs:GetQueueUrl", "sqs:ReceiveMessage", "sqs:DeleteMessage", "sqs:ChangeMessageVisibility" ], "Resource": "arn:aws:sqs…
Posted on May 15, 2026 by Michael Uzukwu, kgateway and agentgateway Contributor CNCF projects highlighted in this post Every gateway ships with a set of built-in policies. Authentication. Rate limiting. Request…
…does a change of provider mean a rewrite? Workloads are represented as standard Kubernetes resources and run on conformant Kubernetes clusters, whether those clusters are in a public cloud, on premises, or…
…Not every prompt change needs a sign-off, but a model touching customer PII or making autonomous decisions probably does. An audit trail that answers “what changed, and why.” Regulators and security…
…What changes is who the platform serves, what it must do, and how it must be built. That evolution is organized around five pillars: AI-Native Platform — The platform supports AI workloads…
…The common pattern that emerged was agents don’t ask “what else needs to change?” They stop once the immediate issue appears resolved. This is most visible in multi-file changes, where…