io.kubernetes.client.proto

Interface V1Certificates.CertificateSigningRequestStatusOrBuilder

All Superinterfaces:

com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder

All Known Implementing Classes:

V1Certificates.CertificateSigningRequestStatus, V1Certificates.CertificateSigningRequestStatus.Builder

Enclosing class:

V1Certificates

public static interface V1Certificates.CertificateSigningRequestStatusOrBuilder
extends com.google.protobuf.MessageOrBuilder

Method Summary

Modifier and Type	Method and Description
com.google.protobuf.ByteString	getCertificate() certificate is populated with an issued certificate by the signer after an Approved condition is present.
V1Certificates.CertificateSigningRequestCondition	getConditions(int index) conditions applied to the request.
int	getConditionsCount() conditions applied to the request.
List<V1Certificates.CertificateSigningRequestCondition>	getConditionsList() conditions applied to the request.
V1Certificates.CertificateSigningRequestConditionOrBuilder	getConditionsOrBuilder(int index) conditions applied to the request.
List<? extends V1Certificates.CertificateSigningRequestConditionOrBuilder>	getConditionsOrBuilderList() conditions applied to the request.
boolean	hasCertificate() certificate is populated with an issued certificate by the signer after an Approved condition is present.

Methods inherited from interface com.google.protobuf.MessageOrBuilder

findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

isInitialized

Method Detail

getConditionsList

List<V1Certificates.CertificateSigningRequestCondition> getConditionsList()

 conditions applied to the request. Known conditions are "Approved", "Denied", and "Failed".
 +listType=map
 +listMapKey=type
 +optional
 

repeated .k8s.io.api.certificates.v1.CertificateSigningRequestCondition conditions = 1;

getConditions

V1Certificates.CertificateSigningRequestCondition getConditions(int index)

 conditions applied to the request. Known conditions are "Approved", "Denied", and "Failed".
 +listType=map
 +listMapKey=type
 +optional
 

repeated .k8s.io.api.certificates.v1.CertificateSigningRequestCondition conditions = 1;

getConditionsCount

int getConditionsCount()

 conditions applied to the request. Known conditions are "Approved", "Denied", and "Failed".
 +listType=map
 +listMapKey=type
 +optional
 

repeated .k8s.io.api.certificates.v1.CertificateSigningRequestCondition conditions = 1;

getConditionsOrBuilderList

List<? extends V1Certificates.CertificateSigningRequestConditionOrBuilder> getConditionsOrBuilderList()

 conditions applied to the request. Known conditions are "Approved", "Denied", and "Failed".
 +listType=map
 +listMapKey=type
 +optional
 

repeated .k8s.io.api.certificates.v1.CertificateSigningRequestCondition conditions = 1;

getConditionsOrBuilder

V1Certificates.CertificateSigningRequestConditionOrBuilder getConditionsOrBuilder(int index)

 conditions applied to the request. Known conditions are "Approved", "Denied", and "Failed".
 +listType=map
 +listMapKey=type
 +optional
 

repeated .k8s.io.api.certificates.v1.CertificateSigningRequestCondition conditions = 1;

hasCertificate

boolean hasCertificate()

 certificate is populated with an issued certificate by the signer after an Approved condition is present.
 This field is set via the /status subresource. Once populated, this field is immutable.
 If the certificate signing request is denied, a condition of type "Denied" is added and this field remains empty.
 If the signer cannot issue the certificate, a condition of type "Failed" is added and this field remains empty.
 Validation requirements:
  1. certificate must contain one or more PEM blocks.
  2. All PEM blocks must have the "CERTIFICATE" label, contain no headers, and the encoded data
   must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280.
  3. Non-PEM content may appear before or after the "CERTIFICATE" PEM blocks and is unvalidated,
   to allow for explanatory text as described in section 5.2 of RFC7468.
 If more than one PEM block is present, and the definition of the requested spec.signerName
 does not indicate otherwise, the first block is the issued certificate,
 and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes.
 The certificate is encoded in PEM format.
 When serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of:
     base64(
     -----BEGIN CERTIFICATE-----
     ...
     -----END CERTIFICATE-----
     )
 +listType=atomic
 +optional
 

optional bytes certificate = 2;

getCertificate

com.google.protobuf.ByteString getCertificate()

 certificate is populated with an issued certificate by the signer after an Approved condition is present.
 This field is set via the /status subresource. Once populated, this field is immutable.
 If the certificate signing request is denied, a condition of type "Denied" is added and this field remains empty.
 If the signer cannot issue the certificate, a condition of type "Failed" is added and this field remains empty.
 Validation requirements:
  1. certificate must contain one or more PEM blocks.
  2. All PEM blocks must have the "CERTIFICATE" label, contain no headers, and the encoded data
   must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280.
  3. Non-PEM content may appear before or after the "CERTIFICATE" PEM blocks and is unvalidated,
   to allow for explanatory text as described in section 5.2 of RFC7468.
 If more than one PEM block is present, and the definition of the requested spec.signerName
 does not indicate otherwise, the first block is the issued certificate,
 and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes.
 The certificate is encoded in PEM format.
 When serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of:
     base64(
     -----BEGIN CERTIFICATE-----
     ...
     -----END CERTIFICATE-----
     )
 +listType=atomic
 +optional
 

optional bytes certificate = 2;