fc6f668a863d460aecb9b1470032ef0e2fd1268e
## Summary Expand the `agent-gateway/agent-readonly` service account from the built-in `view` role to a dedicated read-only role. ## Access policy - Adds `get`, `list`, and `watch` for the core cluster resources and all currently served non-core API groups. - Adds read-only non-resource access for API discovery, health, OpenAPI, and version endpoints. - Does not grant access to the Kubernetes `secrets` resource. - Does not grant write verbs, exec, port-forward, proxy, or token creation permissions. ## Verification - Current target `org1/k3s:main`: `2bbac8467a9297e7056956328f576978142f3b24` - `git diff --check`: passed - Changed file: `k3s_rencher/infrastructure/agent-gateway/rbac.yaml` The existing binding name is preserved so Flux applies the role change in place. ## Kustomize inclusion The root `k3s_rencher/kustomization.yaml` already includes `infrastructure/agent-gateway`. Its nested Kustomization includes `rbac.yaml`, so the new ClusterRole is applied transitively while preserving the `agent-gateway` namespace transformation. A duplicate direct root entry would cause duplicate resource processing. --------- Co-authored-by: admin <rudolfss13@gmail.com> Reviewed-on: org1/k3s#1 Co-authored-by: Alex Rudenk <rudolfss13+hermes@gmail.com>
Description
No description provided
11 MiB
Languages
Python
46.4%
Jinja
32.6%
Shell
14.4%
Dockerfile
6.6%