Skip to content

Hold every Kyverno dependency below 1.20 until the policy migration lands #6169

Open

Description

@devantler

🤖 Generated by the Agentic Engineer

Evidence

The Renovate Dependency Dashboard (#313) lists four pending Kyverno 1.20.0 updates that the existing hold below 1.20 does not cover: the three Kyverno images the platform's own Kyverno builds start from (background controller, CLI, reports controller) and the github.com/kyverno/kyverno Go module. The hold names only the Kyverno chart and the CI policy CLI release, so once these updates pass the release-age cooldown Renovate will open them as ordinary updates.

Problem

Taking Kyverno 1.20 in only some places would mix a 1.20 binary into a 1.19 deployment, and 1.20 removes the policy APIs this platform still uses (#4994). These updates cannot pass CI as they stand and would add red, unmergeable bot PRs to the queue.

Proposed direction

Extend the 1.20 hold to every Kyverno 1.x dependency (the three image names and the Go module), with the same removal condition as the existing hold, and extend the cap check so it fails if any of them is missing from the hold.

Acceptance criteria

  • Renovate proposes no Kyverno 1.20 image or module update while the chart and CLI holds are in force.
  • The cap check fails when any Kyverno dependency is left out of the hold.

Size

S

Activity

  1. added theissue type on Nov 13, 2026
  2. moved this to 📥 Backlog in 🌊 Project Boardon Nov 13, 2026
  3. coderabbitai commented on Nov 13, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #5759 - refactor(policy): move the tenant network guard to ValidatingPolicy [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions