---
title: "Discussion on \"Testing Kyverno Attestation Policies: The Bug That Shipped Twice, and What I Built to Stop a Third\" | Hashnode"
description: "Discussion on \"Testing Kyverno Attestation Policies: The Bug That Shipped Twice, and What I Built to Stop a Third\". Learn how a wrong JMESPath key path let a broken Kyverno attestation policy pass review twice, and the fixture-based tests that catch it now."
url: "https://hashnode.com/posts/testing-kyverno-attestation-policies-the-bug-that-shipped-twice-and-what-i-built-to-stop-a-third/6a61fd22440c89bf6d1b60c0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Testing Kyverno Attestation Policies: The Bug That Shipped Twice, and What I Built to Stop a Third](https://juanmakau.hashnode.dev/testing-kyverno-attestation-policies-the-bug-that-shipped-twice-and-what-i-built-to-stop-a-third?utm_source=hashnode&utm_medium=feed)

Learn how a wrong JMESPath key path let a broken Kyverno attestation policy pass review twice, and the fixture-based tests that catch it now.

Jul 23 · 7 min read · juanmakau.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#devsecops](https://hashnode.com/tag/devsecops)
-   [#kyverno](https://hashnode.com/tag/kyverno)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#testing](https://hashnode.com/tag/testing)

## Written by

[Juan Makau](https://hashnode.com/@makau)

@makau · Nairobi, Kenya

  
[View profile](https://hashnode.com/@makau)

Securing the path from code to cluster.

Senior DevOps Engineer based in Nairobi, focused on DevSecOps and software supply chain security across AWS and GCP. I write about the real bugs I hit building Kubernetes policy enforcement, CI/CD pipelines, and infrastructure as code — not textbook examples.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.