Skip to content

Move the runner-pool retirement fence to ValidatingPolicy #6208

Closed as duplicate
Closed as duplicate

Description

@devantler

🤖 Generated by the Agentic Engineer

Evidence and problem

Kyverno 1.20 is planned to remove ClusterPolicy (#4984). Of the twelve validation policies in #4995, ten now run as ValidatingPolicy in production and one (restrict-arc-openbao-listener) is tracked in #5464. The last one, restrict-arc-retirement, has not been started, and #4995 asks for it to get its own slice before work begins.

This policy keeps the retired GitHub Actions runner pool retired: it stops the pool, its scale set, its listener and its credentials from coming back, and protects the retirement record and the namespace. It is larger than the earlier batches because six of its eight rules read the arc-runners Namespace through Kyverno API calls, and it fails closed (failurePolicy: Fail).

It already has Kyverno CLI tests (the tests/restrict-arc-retirement-* fixtures), so the "no tests" note in #4995 is out of date for this policy.

Who it affects

The platform operator: if this policy is lost or weakened in the move, a routine Flux change could quietly re-create the retired runner pool and its credentials.

Hypothesis

If the policy is rewritten as a ValidatingPolicy that reads the Namespace with the new policy kind's own resource lookup, and the existing CLI tests pass against it with unchanged expected results, the ClusterPolicy can be removed with no change in what is allowed or refused.

Acceptance criteria

  • The existing restrict-arc-retirement CLI tests pass against the current ClusterPolicy before any change, and unchanged against the replacement.
  • Each of the eight rules has an equivalent in the replacement, with the same failure action and the same fail-closed behaviour when the Namespace cannot be read.
  • The replacement runs alongside the old policy first and reports ready in production before the old one is removed.
  • After removal, no ClusterPolicy named restrict-arc-retirement remains, read back from production.

Success signal

#4995's list reaches twelve of twelve once this and #5464 are done.

Rough size: medium (one policy, eight rules, existing tests).

Activity

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

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Closing as a duplicate of #5834, which tracks the same restrict-arc-retirement migration and already holds a spike result from 2026-11-03: the move needs the offline engine driver (for refused Namespace reads, a separate previous object and user groups), and the retirement tooling must learn the ValidatingPolicy denial format. Further slices are filed under #5834.

  4. moved this from 📥 Backlog to ✅ Done in 🌊 Project Boardon Nov 13, 2026
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

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions