![]() Automatic merge from submit-queue Include all user.Info data in CSR object In order to use authorization checks to auto-approve CSRs in the future, we need all the info from the user.Info interface. This mirrors the API fields in the TokenReview API used to return user info, and in the SubjectAccessReview API we use to check authorization. ```release-note The CertificateSigningRequest API added the `extra` field to persist all information about the requesting user. This mirrors the fields in the SubjectAccessReview API used to check authorization. ``` |
||
---|---|---|
.. | ||
apps/v1beta1 | ||
authentication.k8s.io | ||
authorization.k8s.io | ||
autoscaling | ||
batch | ||
certificates.k8s.io/v1beta1 | ||
extensions/v1beta1 | ||
policy/v1beta1 | ||
rbac.authorization.k8s.io | ||
storage.k8s.io/v1beta1 | ||
v1 | ||
labels-annotations-taints.md | ||
README.md |
API Reference
Use the following reference docs to understand the kubernetes REST API for various API group versions:
- v1: operations, model definitions
- extensions/v1beta1: operations, model definitions
- batch/v1: operations, model definitions
- autoscaling/v1: operations, model definitions