fix(binjovi): permit exact Bytey legacy ownership reads #327
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/binjovi-service-observation-access"
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?
The Bytey handoff worker cannot prove that a legacy rule is absent: Kubernetes returns403 because the existing provider-authority grant does not include Bytey. Add a separate get-only Role for bytey-main, bytey-trunk and retained bytey-tags, bound only to binjovi/binjovi. Keep the grant after adoption so a recreated legacy owner stops writes.
Validation: live authorization check returned no before the fix; new source regression contract fails before and passes after; the complete Binjovi source guard and Kustomize render pass. The pending adoption keeps the remote policy retained until this read grant is active.