Record controller exemption denial and prepared RBAC recovery #55
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!55
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/rke2-delivery-progress"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Update the dated RKE2 status pages for the promoted diagnostic release and the identified exemption-readiness permission failure. Explain that uds.dev names a Kubernetes API group rather than a development environment. Keep failed delivery distinct from successful controller acceptance.
Describe the prepared namespace-scoped exemption list/watch correction and its application through existing reviewed bootstrap delivery. Preserve named writes and Secret restrictions. Record temporary authorization, signed bootstrap delivery, routine validation, authorization retirement and controller retry as pending work. The existing controller runtime bundle remains reusable.
Validation: npm run check, npm run build, diff checks and the Gitleaks 8.30.1 hook passed. Documentation only; no deployment, apply or live Role change is performed.
Reviewed the four changed documentation files at
c6e465a3ca. The record identifies the 5015 denial as namespaceduds.dev/exemptionslist access (not a dev-environment issue), distinguishes the failed controller delivery from acceptance, limits the proposed correction to namespace-scoped list/watch while preserving named writes and Secret restrictions, and retains reviewed Terraform authorization, signed bootstrap Role delivery, routine validation, retirement, and controller retry as pending. No deployment manifests or policy are changed by this PR. Source approval only: current source-security and site checks are pending; this does not approve deployment or merge. Forgejo did not expose patch hunks, and I did not independently validate the historical private run or live-cluster claims.CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.