pub struct PodCertificateRequestSpec {
pub max_expiration_seconds: Option<i32>,
pub node_name: String,
pub node_uid: String,
pub pkix_public_key: ByteString,
pub pod_name: String,
pub pod_uid: String,
pub proof_of_possession: ByteString,
pub service_account_name: String,
pub service_account_uid: String,
pub signer_name: String,
}
Expand description
PodCertificateRequestSpec describes the certificate request. All fields are immutable after creation.
Fields§
§max_expiration_seconds: Option<i32>
maxExpirationSeconds is the maximum lifetime permitted for the certificate.
If omitted, kube-apiserver will set it to 86400(24 hours). kube-apiserver will reject values shorter than 3600 (1 hour). The maximum allowable value is 7862400 (91 days).
The signer implementation is then free to issue a certificate with any lifetime shorter than MaxExpirationSeconds, but no shorter than 3600 seconds (1 hour). This constraint is enforced by kube-apiserver. kubernetes.io
signers will never issue certificates with a lifetime longer than 24 hours.
node_name: String
nodeName is the name of the node the pod is assigned to.
node_uid: String
nodeUID is the UID of the node the pod is assigned to.
pkix_public_key: ByteString
pkixPublicKey is the PKIX-serialized public key the signer will issue the certificate to.
The key must be one of RSA3072, RSA4096, ECDSAP256, ECDSAP384, ECDSAP521, or ED25519. Note that this list may be expanded in the future.
Signer implementations do not need to support all key types supported by kube-apiserver and kubelet. If a signer does not support the key type used for a given PodCertificateRequest, it must deny the request by setting a status.conditions entry with a type of “Denied” and a reason of “UnsupportedKeyType”. It may also suggest a key type that it does support in the message field.
pod_name: String
podName is the name of the pod into which the certificate will be mounted.
pod_uid: String
podUID is the UID of the pod into which the certificate will be mounted.
proof_of_possession: ByteString
proofOfPossession proves that the requesting kubelet holds the private key corresponding to pkixPublicKey.
It is contructed by signing the ASCII bytes of the pod’s UID using pkixPublicKey
.
kube-apiserver validates the proof of possession during creation of the PodCertificateRequest.
If the key is an RSA key, then the signature is over the ASCII bytes of the pod UID, using RSASSA-PSS from RFC 8017 (as implemented by the golang function crypto/rsa.SignPSS with nil options).
If the key is an ECDSA key, then the signature is as described by [SEC 1, Version 2.0](https://www.secg.org/sec1-v2.pdf) (as implemented by the golang library function crypto/ecdsa.SignASN1)
If the key is an ED25519 key, the the signature is as described by the [ED25519 Specification](https://ed25519.cr.yp.to/) (as implemented by the golang library crypto/ed25519.Sign).
service_account_name: String
serviceAccountName is the name of the service account the pod is running as.
service_account_uid: String
serviceAccountUID is the UID of the service account the pod is running as.
signer_name: String
signerName indicates the requested signer.
All signer names beginning with kubernetes.io
are reserved for use by the Kubernetes project. There is currently one well-known signer documented by the Kubernetes project, kubernetes.io/kube-apiserver-client-pod
, which will issue client certificates understood by kube-apiserver. It is currently unimplemented.
Trait Implementations§
Source§impl Clone for PodCertificateRequestSpec
impl Clone for PodCertificateRequestSpec
Source§fn clone(&self) -> PodCertificateRequestSpec
fn clone(&self) -> PodCertificateRequestSpec
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for PodCertificateRequestSpec
impl Debug for PodCertificateRequestSpec
Source§impl DeepMerge for PodCertificateRequestSpec
impl DeepMerge for PodCertificateRequestSpec
Source§fn merge_from(&mut self, other: Self)
fn merge_from(&mut self, other: Self)
other
into self
.