Garm implements the Kubernetes authorization webhook interface to provide access control on your K8s resources with Athenz RBAC policy. It allows flexible resource mapping from K8s resources to Athenz ones, mutli-tenancy, and black/white list.
By default, Garm replies the native Kubernetes authentication for authorization. However, it also supports the Kubernetes authentication webhook. Using the authentication hook requires Athenz to be able to sign tokens for users.
Requires go 1.18 or later.
- K8s webhook request (SubjectAccessReview) (Webhook Mode - Kubernetes)
- the K8s API server wants to know if the user is allowed to do the requested action
- Athenz RBAC request (Athenz)
- Athenz server contains the user authorization information for access control
- ask Athenz server is the user action is allowed based on pre-configured policy
Garm convert the K8s request to Athenz request based on the mapping rules in config.yaml (example).
P.S. It is just a sample deployment solution above. Garm can work on any environment as long as it can access both the API server and the Athenz server.
$ docker pull docker.io/athenz/garm- Releases