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.
## 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.
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.
Summary
Expand the
agent-gateway/agent-readonlyservice account from the built-inviewrole to a dedicated read-only role.Access policy
get,list, andwatchfor the core cluster resources and all currently served non-core API groups.secretsresource.Verification
org1/k3s:main:2bbac8467a9297e7056956328f576978142f3b24git diff --check: passedk3s_rencher/infrastructure/agent-gateway/rbac.yamlThe existing binding name is preserved so Flux applies the role change in place.
Kustomize inclusion
The root
k3s_rencher/kustomization.yamlalready includesinfrastructure/agent-gateway. Its nested Kustomization includesrbac.yaml, so the new ClusterRole is applied transitively while preserving theagent-gatewaynamespace transformation. A duplicate direct root entry would cause duplicate resource processing.placeholderto [ready-to-test] k3s: expand agent read access without secrets