You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Move the runner-pool retirement fence to ValidatingPolicy #6208
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).
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.
Activity
devantler commentedon Nov 13, 2026
Closing as a duplicate of #5834, which tracks the same
restrict-arc-retirementmigration 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 theValidatingPolicydenial format. Further slices are filed under #5834.