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. ```
Kubernetes Documentation: releases.k8s.io/HEAD
-
The User's guide is for anyone who wants to run programs and services on an existing Kubernetes cluster.
-
The Cluster Admin's guide is for anyone setting up a Kubernetes cluster or administering it.
-
The Developer guide is for anyone wanting to write programs that access the Kubernetes API, write plugins or extensions, or modify the core code of Kubernetes.
-
The Kubectl Command Line Interface is a detailed reference on the
kubectlCLI. -
The API object documentation is a detailed description of all fields found in core API objects.
-
An overview of the Design of Kubernetes
-
There are example files and walkthroughs in the examples folder.
-
If something went wrong, see the troubleshooting guide for how to debug. You should also check the known issues for the release you're using.
-
To report a security issue, see Reporting a Security Issue.