Found on the first real use of the restricted identity (verifying #253 post-merge): assessing the VeleroBackupFailed issue #251 requires reading backups.velero.io — the latest apps-daily backup is PartiallyFailed (data-mover pod unschedulable, unbound PVC) even though the alert itself cleared — and the ClusterRole had neither velero.io nor postgresql.cnpg.io.
Also documents the name-collision gotcha for agents: bare get backup in the velero namespace resolves to CNPG's backups first; use backups.velero.io.
Everything else from #253 verified working with the restricted identity: pods/logs/sts/externalsecrets/proxy APIs readable, secrets 403, all writes denied (auth can-i "" "" → no).
Found on the first real use of the restricted identity (verifying #253 post-merge): assessing the VeleroBackupFailed issue #251 requires reading backups.velero.io — the latest apps-daily backup is PartiallyFailed (data-mover pod unschedulable, unbound PVC) even though the alert itself cleared — and the ClusterRole had neither velero.io nor postgresql.cnpg.io.
Also documents the name-collision gotcha for agents: bare `get backup` in the velero namespace resolves to CNPG's backups first; use `backups.velero.io`.
Everything else from #253 verified working with the restricted identity: pods/logs/sts/externalsecrets/proxy APIs readable, secrets 403, all writes denied (auth can-i \"*\" \"*\" → no).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei
Found on the first real use of the restricted identity: assessing the
VeleroBackupFailed issue (#251) needs backups.velero.io (latest
apps-daily run is PartiallyFailed — data-mover pod unschedulable on an
unbound PVC), and the ClusterRole had neither velero.io nor CNPG.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found on the first real use of the restricted identity (verifying #253 post-merge): assessing the VeleroBackupFailed issue #251 requires reading backups.velero.io — the latest apps-daily backup is PartiallyFailed (data-mover pod unschedulable, unbound PVC) even though the alert itself cleared — and the ClusterRole had neither velero.io nor postgresql.cnpg.io.
Also documents the name-collision gotcha for agents: bare
get backupin the velero namespace resolves to CNPG's backups first; usebackups.velero.io.Everything else from #253 verified working with the restricted identity: pods/logs/sts/externalsecrets/proxy APIs readable, secrets 403, all writes denied (auth can-i "" "" → no).
🤖 Generated with Claude Code
https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei