com.coralogix.zio.k8s.model.certificates.v1beta1

human readable message with details about the request state

brief reason for the request state

Status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be "False" or "Unknown". Defaults to "True". If unset, should be treated as "True".

type of the condition. Known conditions include "Approved", "Denied", and "Failed".

Extra information about the requesting user. See user.Info interface for details.

Group information about the requesting user. See user.Info interface for details.

Base64-encoded PKCS#10 CSR data

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 client certificate, it is assigned "kubernetes.io/kube-apiserver-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.

UID information about the requesting user. See user.Info interface for details.

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", "client auth", "code signing", "email protection", "s/mime", "ipsec end system", "ipsec tunnel", "ipsec user", "timestamping", "ocsp signing", "microsoft sgc", "netscape sgc"

Information about the requesting user. See user.Info interface for details.

If request was approved, the controller will place the issued certificate here.

Conditions applied to the request, such as approval or denial.