April 2018
Intermediate to advanced
468 pages
14h 34m
English
The authorization webhook is very similar to the authentication webhook. It just requires a configuration file that is in the same format as the authentication webhook configuration file. There is no authorization caching because unlike authentication, the same user may make lots of requests to different API endpoints with different parameters and authorization decisions may be different, so caching is not a viable option.
You configure the webhook by passing the following command-line arguments to the API server:
When a request passes authentication, Kubernetes will send a SubjectAccessReview JSON ...
Read now
Unlock full access