2.6 KiB
2.6 KiB
V1beta1CertificateSigningRequestSpec
This information is immutable after the request is created. Only the Request and Usages fields can be set on creation, other fields are derived by Kubernetes and cannot be modified by users.
Properties
| Name | Type | Description | Notes |
|---|---|---|---|
| extra | dict(str, list[str]) | Extra information about the requesting user. See user.Info interface for details. | [optional] |
| groups | list[str] | Group information about the requesting user. See user.Info interface for details. | [optional] |
| request | str | Base64-encoded PKCS#10 CSR data | |
| signer_name | str | Requested signer for the request. It is a qualified name in the form: `scope-hostname.io/name`. If empty, it will be defaulted: 1. If it's a kubelet kubernetes.client certificate, it is assigned "kubernetes.io/kube-apiserver-kubernetes.client-kubelet". 2. If it's a kubelet serving certificate, it is assigned "kubernetes.io/kubelet-serving". 3. Otherwise, it is assigned "kubernetes.io/legacy-unknown". Distribution of trust for signers happens out of band. You can select on this field using `spec.signerName`. | [optional] |
| uid | str | UID information about the requesting user. See user.Info interface for details. | [optional] |
| usages | list[str] | allowedUsages specifies a set of usage contexts the key will be valid for. See: https://tools.ietf.org/html/rfc5280#section-4.2.1.3 https://tools.ietf.org/html/rfc5280#section-4.2.1.12 Valid values are: "signing", "digital signature", "content commitment", "key encipherment", "key agreement", "data encipherment", "cert sign", "crl sign", "encipher only", "decipher only", "any", "server auth", "kubernetes.client auth", "code signing", "email protection", "s/mime", "ipsec end system", "ipsec tunnel", "ipsec user", "timestamping", "ocsp signing", "microsoft sgc", "netscape sgc" | [optional] |
| username | str | Information about the requesting user. See user.Info interface for details. | [optional] |