[ready-to-test] k3s: expand agent read access without secrets #1

Merged
admin merged 2 commits from hermes/k3s:feat/agent-readonly-all-except-secrets into main 2026-11-11 13:02:42 +01:00
Member

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.

## 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.
hermes added 1 commit 2026-11-09 08:26:14 +01:00
hermes changed title from placeholder to [ready-to-test] k3s: expand agent read access without secrets 2026-11-09 08:26:15 +01:00
admin added 1 commit 2026-11-11 13:01:19 +01:00
admin merged commit fc6f668a86 into main 2026-11-11 13:02:42 +01:00
Sign in to join this conversation.
No Reviewers
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: org1/infra#1