CertificateAuthority is the Schema for the CertificateAuthoritys API. A CertificateAuthority represents an individual Certificate Authority.
Type
CRD
Group
privateca.gcp.upbound.io
Version
v1beta1
apiVersion: privateca.gcp.upbound.io/v1beta1
kind: CertificateAuthority
CertificateAuthoritySpec defines the desired state of CertificateAuthority
No description provided.
The config used to create a self-signed X.509 certificate or CSR. Structure is documented below.
Specifies some of the values in a certificate that are related to the subject. Structure is documented below.
Contains distinguished name fields such as the location and organization. Structure is documented below.
The subject alternative name fields. Structure is documented below.
Contains only valid, fully-qualified host names.
Contains only valid RFC 2822 E-mail addresses.
Contains only valid 32-bit IPv4 addresses or RFC 4291 IPv6 addresses.
Contains only valid RFC 3986 URIs.
Describes how some of the technical X.509 fields in a certificate should be populated. Structure is documented below.
Specifies an X.509 extension, which may be used in different parts of X.509 objects like certificates, CSRs, and CRLs. Structure is documented below.
Describes values that are relevant in a CA certificate. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Describes Online Certificate Status Protocol (OCSP) endpoint addresses that appear in the "Authority Information Access" extension in the certificate.
Describes values that are relevant in a CA certificate. Structure is documented below.
Indicates the intended use for keys that correspond to a certificate. Structure is documented below.
Describes high-level ways in which a key may be used. Structure is documented below.
Describes high-level ways in which a key may be used. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Describes the X.509 name constraints extension. Structure is documented below.
Contains excluded DNS names. Any DNS name that can be constructed by simply adding zero or more labels to the left-hand side of the name satisfies the name constraint. For example, example.com, www.example.com, www.sub.example.com would satisfy example.com while example1.com does not.
Contains the excluded email addresses. The value can be a particular email address, a hostname to indicate all email addresses on that host or a domain with a leading period (e.g. .example.com) to indicate all email addresses in that domain.
Contains the excluded IP ranges. For IPv4 addresses, the ranges are expressed using CIDR notation as specified in RFC 4632. For IPv6 addresses, the ranges are expressed in similar encoding as IPv4 addresses.
Contains the excluded URIs that apply to the host part of the name. The value can be a hostname or a domain with a leading period (like .example.com)
Contains permitted DNS names. Any DNS name that can be constructed by simply adding zero or more labels to the left-hand side of the name satisfies the name constraint. For example, example.com, www.example.com, www.sub.example.com would satisfy example.com while example1.com does not.
Contains the permitted email addresses. The value can be a particular email address, a hostname to indicate all email addresses on that host or a domain with a leading period (e.g. .example.com) to indicate all email addresses in that domain.
Contains the permitted IP ranges. For IPv4 addresses, the ranges are expressed using CIDR notation as specified in RFC 4632. For IPv6 addresses, the ranges are expressed in similar encoding as IPv4 addresses.
Contains the permitted URIs that apply to the host part of the name. The value can be a hostname or a domain with a leading period (like .example.com)
Describes the X.509 certificate policy object identifiers, per https://tools.ietf.org/html/rfc5280#section-4.2.1.4. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Used when issuing certificates for this CertificateAuthority. If this CertificateAuthority is a self-signed CertificateAuthority, this key is also used to sign the self-signed CA certificate. Otherwise, it is used to sign a CSR. Structure is documented below.
Reference to a CAPool to populate pool.
Policies for referencing.
Selector for a CAPool to populate pool.
Policies for selection.
If this is a subordinate CertificateAuthority, this field will be set with the subordinate configuration, which describes its issuers. Structure is documented below.
Reference to a CertificateAuthority in privateca to populate certificateAuthority.
Policies for referencing.
Selector for a CertificateAuthority in privateca to populate certificateAuthority.
Policies for selection.
Contains the PEM certificate chain for the issuers of this CertificateAuthority, but not pem certificate for this CA itself. Structure is documented below.
Expected to be in leaf-to-root order according to RFC 5246.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
The config used to create a self-signed X.509 certificate or CSR. Structure is documented below.
Specifies some of the values in a certificate that are related to the subject. Structure is documented below.
Contains distinguished name fields such as the location and organization. Structure is documented below.
The subject alternative name fields. Structure is documented below.
Contains only valid, fully-qualified host names.
Contains only valid RFC 2822 E-mail addresses.
Contains only valid 32-bit IPv4 addresses or RFC 4291 IPv6 addresses.
Contains only valid RFC 3986 URIs.
Describes how some of the technical X.509 fields in a certificate should be populated. Structure is documented below.
Specifies an X.509 extension, which may be used in different parts of X.509 objects like certificates, CSRs, and CRLs. Structure is documented below.
Describes values that are relevant in a CA certificate. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Describes Online Certificate Status Protocol (OCSP) endpoint addresses that appear in the "Authority Information Access" extension in the certificate.
Describes values that are relevant in a CA certificate. Structure is documented below.
Indicates the intended use for keys that correspond to a certificate. Structure is documented below.
Describes high-level ways in which a key may be used. Structure is documented below.
Describes high-level ways in which a key may be used. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Describes the X.509 name constraints extension. Structure is documented below.
Contains excluded DNS names. Any DNS name that can be constructed by simply adding zero or more labels to the left-hand side of the name satisfies the name constraint. For example, example.com, www.example.com, www.sub.example.com would satisfy example.com while example1.com does not.
Contains the excluded email addresses. The value can be a particular email address, a hostname to indicate all email addresses on that host or a domain with a leading period (e.g. .example.com) to indicate all email addresses in that domain.
Contains the excluded IP ranges. For IPv4 addresses, the ranges are expressed using CIDR notation as specified in RFC 4632. For IPv6 addresses, the ranges are expressed in similar encoding as IPv4 addresses.
Contains the excluded URIs that apply to the host part of the name. The value can be a hostname or a domain with a leading period (like .example.com)
Contains permitted DNS names. Any DNS name that can be constructed by simply adding zero or more labels to the left-hand side of the name satisfies the name constraint. For example, example.com, www.example.com, www.sub.example.com would satisfy example.com while example1.com does not.
Contains the permitted email addresses. The value can be a particular email address, a hostname to indicate all email addresses on that host or a domain with a leading period (e.g. .example.com) to indicate all email addresses in that domain.
Contains the permitted IP ranges. For IPv4 addresses, the ranges are expressed using CIDR notation as specified in RFC 4632. For IPv6 addresses, the ranges are expressed in similar encoding as IPv4 addresses.
Contains the permitted URIs that apply to the host part of the name. The value can be a hostname or a domain with a leading period (like .example.com)
Describes the X.509 certificate policy object identifiers, per https://tools.ietf.org/html/rfc5280#section-4.2.1.4. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Used when issuing certificates for this CertificateAuthority. If this CertificateAuthority is a self-signed CertificateAuthority, this key is also used to sign the self-signed CA certificate. Otherwise, it is used to sign a CSR. Structure is documented below.
If this is a subordinate CertificateAuthority, this field will be set with the subordinate configuration, which describes its issuers. Structure is documented below.
Reference to a CertificateAuthority in privateca to populate certificateAuthority.
Policies for referencing.
Selector for a CertificateAuthority in privateca to populate certificateAuthority.
Policies for selection.
Contains the PEM certificate chain for the issuers of this CertificateAuthority, but not pem certificate for this CA itself. Structure is documented below.
Expected to be in leaf-to-root order according to RFC 5246.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
CertificateAuthorityStatus defines the observed state of CertificateAuthority.
No description provided.
URLs for accessing content published by this CA, such as the CA certificate and CRLs. Structure is documented below.
(Output) The URL where this CertificateAuthority's CRLs are published. This will only be set for CAs that have been activated.
The config used to create a self-signed X.509 certificate or CSR. Structure is documented below.
Specifies some of the values in a certificate that are related to the subject. Structure is documented below.
Contains distinguished name fields such as the location and organization. Structure is documented below.
The subject alternative name fields. Structure is documented below.
Contains only valid, fully-qualified host names.
Contains only valid RFC 2822 E-mail addresses.
Contains only valid 32-bit IPv4 addresses or RFC 4291 IPv6 addresses.
Contains only valid RFC 3986 URIs.
Describes how some of the technical X.509 fields in a certificate should be populated. Structure is documented below.
Specifies an X.509 extension, which may be used in different parts of X.509 objects like certificates, CSRs, and CRLs. Structure is documented below.
Describes values that are relevant in a CA certificate. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Describes Online Certificate Status Protocol (OCSP) endpoint addresses that appear in the "Authority Information Access" extension in the certificate.
Describes values that are relevant in a CA certificate. Structure is documented below.
Indicates the intended use for keys that correspond to a certificate. Structure is documented below.
Describes high-level ways in which a key may be used. Structure is documented below.
Describes high-level ways in which a key may be used. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Describes the X.509 name constraints extension. Structure is documented below.
Contains excluded DNS names. Any DNS name that can be constructed by simply adding zero or more labels to the left-hand side of the name satisfies the name constraint. For example, example.com, www.example.com, www.sub.example.com would satisfy example.com while example1.com does not.
Contains the excluded email addresses. The value can be a particular email address, a hostname to indicate all email addresses on that host or a domain with a leading period (e.g. .example.com) to indicate all email addresses in that domain.
Contains the excluded IP ranges. For IPv4 addresses, the ranges are expressed using CIDR notation as specified in RFC 4632. For IPv6 addresses, the ranges are expressed in similar encoding as IPv4 addresses.
Contains the excluded URIs that apply to the host part of the name. The value can be a hostname or a domain with a leading period (like .example.com)
Contains permitted DNS names. Any DNS name that can be constructed by simply adding zero or more labels to the left-hand side of the name satisfies the name constraint. For example, example.com, www.example.com, www.sub.example.com would satisfy example.com while example1.com does not.
Contains the permitted email addresses. The value can be a particular email address, a hostname to indicate all email addresses on that host or a domain with a leading period (e.g. .example.com) to indicate all email addresses in that domain.
Contains the permitted IP ranges. For IPv4 addresses, the ranges are expressed using CIDR notation as specified in RFC 4632. For IPv6 addresses, the ranges are expressed in similar encoding as IPv4 addresses.
Contains the permitted URIs that apply to the host part of the name. The value can be a hostname or a domain with a leading period (like .example.com)
Describes the X.509 certificate policy object identifiers, per https://tools.ietf.org/html/rfc5280#section-4.2.1.4. Structure is documented below.
An ObjectId specifies an object identifier (OID). These provide context and describe types in ASN.1 messages.
Used when issuing certificates for this CertificateAuthority. If this CertificateAuthority is a self-signed CertificateAuthority, this key is also used to sign the self-signed CA certificate. Otherwise, it is used to sign a CSR. Structure is documented below.
This CertificateAuthority's certificate chain, including the current CertificateAuthority's certificate. Ordered such that the root issuer is the final element (consistent with RFC 5246). For a self-signed CA, this will only list the current CertificateAuthority's certificate.
If this is a subordinate CertificateAuthority, this field will be set with the subordinate configuration, which describes its issuers. Structure is documented below.
Contains the PEM certificate chain for the issuers of this CertificateAuthority, but not pem certificate for this CA itself. Structure is documented below.
Expected to be in leaf-to-root order according to RFC 5246.
Conditions of the resource.
certificate-${Rand.RFC1123Subdomain}
apiVersion: privateca.gcp.upbound.io/v1beta1
kind: CertificateAuthority
metadata:
annotations:
meta.upbound.io/example-id: privateca/v1beta1/certificate
upjet.upbound.io/manual-intervention: All CAs in the CA Pool must be removed or
be past their recovery period before the pool can be deleted
labels:
testing.upbound.io/example-name: certificate
name: certificate-${Rand.RFC1123Subdomain}
spec:
forProvider:
config:
- subjectConfig:
- subject:
- commonName: my-certificate-authority
organization: Upbound
subjectAltName:
- dnsNames:
- upbound.io
x509Config:
- caOptions:
- isCa: true
keyUsage:
- baseKeyUsage:
- certSign: true
crlSign: true
extendedKeyUsage:
- serverAuth: true
deletionProtection: false
ignoreActiveCertificatesOnDeletion: false
keySpec:
- algorithm: RSA_PKCS1_4096_SHA256
location: us-central1
poolSelector:
matchLabels:
testing.upbound.io/example-name: certificate
certificate-authority-${Rand.RFC1123Subdomain}
apiVersion: privateca.gcp.upbound.io/v1beta1
kind: CertificateAuthority
metadata:
annotations:
meta.upbound.io/example-id: privateca/v1beta1/certificateauthority
upjet.upbound.io/manual-intervention: All CAs in the CA Pool must be removed or
be past their recovery period before the pool can be deleted
labels:
testing.upbound.io/example-name: certificate-authority
name: certificate-authority-${Rand.RFC1123Subdomain}
spec:
forProvider:
config:
- subjectConfig:
- subject:
- commonName: my-certificate-authority
organization: Upbound
subjectAltName:
- dnsNames:
- upbound.io
x509Config:
- caOptions:
- isCa: true
maxIssuerPathLength: 10
keyUsage:
- baseKeyUsage:
- certSign: true
contentCommitment: true
crlSign: true
dataEncipherment: true
decipherOnly: true
digitalSignature: true
keyAgreement: true
keyEncipherment: false
extendedKeyUsage:
- clientAuth: false
codeSigning: true
emailProtection: true
serverAuth: true
timeStamping: true
deletionProtection: false
keySpec:
- algorithm: RSA_PKCS1_4096_SHA256
lifetime: 86400s
location: us-central1
poolSelector:
matchLabels:
testing.upbound.io/example-name: certificate-authority
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.