Home / Companies / Harness / Blog / Post Details
Content Deep Dive

Policy as Code in 2026: OPA, Kyverno, Cedar and What’s Next | Harness Blog

Blog post from Harness

Post Details
Company
Date Published
Author
Abhijit Pujare
Word Count
1,247
Company Posts That Month
43
Language
English
Hacker News Points
-
Post removed?
No
Summary

Policy as Code (PaC) has become central to automated security and compliance governance by making rules version-controlled, testable, machine-readable artifacts separate from application logic, but policy authoring complexity remains a major adoption challenge. Open Policy Agent (OPA) is the leading general-purpose framework because it can govern infrastructure, CI/CD pipelines, Kubernetes, and other systems using Rego, though its declarative syntax, evolving data schemas, and specialized knowledge requirements create a “Rego Tax” for platform teams. In Kubernetes, Kyverno has gained adoption by using familiar YAML-based policies, while Kubernetes’ native Common Expression Language support increasingly handles simple validations and pushes external engines toward more complex functions. For application authorization, AWS Cedar emphasizes typed schemas, performance, and formal verification, while its Dogwood extension adds temporal reasoning intended to govern sequences of AI agent actions; however, Cedar remains more limited than OPA for broad infrastructure use. The article predicts that organizations will increasingly use multiple policy engines for different contexts and presents Harness’s natural-language-to-Rego generation, testing tools, and policy libraries as ways to reduce the effort of implementing OPA-based governance.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 8 4,346 397 100 +24%
AI Agents 3 5,555 1,398 270 -7%
Developer Experience 1 639 273 90 +30%
Real-time 1 4,804 1,074 238 +4%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.