OpsCanary
Back to daily brief
kubernetesPractitioner

Securing Kubernetes with GitOps: Argo CD and Kyverno in Action

5 min read CNCF BlogApr 2, 2026
Share
PractitionerHands-on experience recommended

Kubernetes security is paramount, especially as your infrastructure scales. GitOps with Argo CD and Kyverno allows you to enforce policies as code, ensuring that only compliant resources are created in your cluster. This approach not only simplifies security management but also integrates seamlessly into your CI/CD pipeline, reducing the risk of human error.

Kyverno operates at the admission controller level, intercepting resource requests before they reach your cluster. You can define rules in standard Kubernetes YAML to validate, block, audit, mutate, or even generate resources. Once your policies are committed to Git, Argo CD automatically syncs them to the cluster, ensuring that all resources comply with your defined rules. For example, you might have a directory structure like infra-services/kyverno.yaml and infra-services/kyverno-policies.yaml, which contain your application manifests and custom policy YAMLs.

In production, it's crucial to have Argo CD already installed with a root app watching your infra-services/ directory. This setup allows for efficient policy management and enforcement. Be aware that while Kyverno is powerful, it requires careful configuration to avoid unintentional resource creation or blocking. Always test your policies in a staging environment before deploying them to production to ensure they behave as expected.

Key takeaways

  • Define rules in standard Kubernetes YAML to enforce compliance.
  • Use Argo CD to automatically sync your policies to the cluster.
  • Leverage Kyverno's ability to block, audit, or mutate resources based on your defined rules.
  • Organize your policy files effectively in your Git repository for better management.
  • Test policies in a staging environment before production deployment.

Why it matters

Implementing GitOps with Argo CD and Kyverno significantly reduces the risk of misconfigurations in your Kubernetes clusters, leading to a more secure and reliable production environment.

Code examples

YAML
1global-infra/
2  infra-services/  #contains Application manifests for Kyverno + policies
3    kyverno.yaml
4    kyverno-policies.yaml
5  kyverno/              # kyverno child app points here
6    Chart.yaml
7    values.yaml
8  kyverno-policies/     # kyverno-policies child app points here
9    Chart.yaml
10    values.yaml
11    templates/          # your custom policy YAMLs live here
YAML
Inside
infra-services/
, create
kyverno.yaml
. This defines the

When NOT to use this

The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.

Want the complete reference?

Read official docs

Test what you just learned

Quiz questions written from this article

Take the quiz →

Get the daily digest

One email. 5 articles. Every morning.

No spam. Unsubscribe anytime.