diff --git a/.github/workflows/k8s-prepare.yml b/.github/workflows/k8s-prepare.yml index c8b203f..3363ba1 100644 --- a/.github/workflows/k8s-prepare.yml +++ b/.github/workflows/k8s-prepare.yml @@ -50,7 +50,7 @@ jobs: ## build PR description body echo echo "Builing PR title+body content..." - diff_size=$(du -k '/tmp/kube.diff' | cut -f1) + diff_size=$(wc -c /tmp/kube.diff | awk '{print $1}') pr_head_describe="$(git describe --always --tag)" pr_title="Deploy ${BRANCH_RELEASE} ${pr_head_describe}" diff --git a/_/ClusterRole/cert-manager-cainjector.yaml b/_/ClusterRole/cert-manager-cainjector.yaml index cc4b2d1..4e7fec6 100644 --- a/_/ClusterRole/cert-manager-cainjector.yaml +++ b/_/ClusterRole/cert-manager-cainjector.yaml @@ -46,6 +46,7 @@ rules: - list - watch - update + - patch - apiGroups: - apiregistration.k8s.io resources: @@ -55,6 +56,7 @@ rules: - list - watch - update + - patch - apiGroups: - apiextensions.k8s.io resources: @@ -64,3 +66,4 @@ rules: - list - watch - update + - patch diff --git a/_/ClusterRole/cert-manager-cluster-view.yaml b/_/ClusterRole/cert-manager-cluster-view.yaml new file mode 100644 index 0000000..becba24 --- /dev/null +++ b/_/ClusterRole/cert-manager-cluster-view.yaml @@ -0,0 +1,22 @@ +apiVersion: rbac.authorization.k8s.io/v1 +kind: ClusterRole +metadata: + labels: + app: cert-manager + app.kubernetes.io/component: controller + app.kubernetes.io/instance: cert-manager + app.kubernetes.io/managed-by: Helm + app.kubernetes.io/name: cert-manager + app.kubernetes.io/version: v1.10.1 + helm.sh/chart: cert-manager-v1.10.1 + rbac.authorization.k8s.io/aggregate-to-cluster-reader: 'true' + name: cert-manager-cluster-view +rules: + - apiGroups: + - cert-manager.io + resources: + - clusterissuers + verbs: + - get + - list + - watch diff --git a/_/ClusterRole/cert-manager-view.yaml b/_/ClusterRole/cert-manager-view.yaml index f95ddee..257e1ea 100644 --- a/_/ClusterRole/cert-manager-view.yaml +++ b/_/ClusterRole/cert-manager-view.yaml @@ -10,6 +10,7 @@ metadata: app.kubernetes.io/version: v1.10.1 helm.sh/chart: cert-manager-v1.10.1 rbac.authorization.k8s.io/aggregate-to-admin: 'true' + rbac.authorization.k8s.io/aggregate-to-cluster-reader: 'true' rbac.authorization.k8s.io/aggregate-to-edit: 'true' rbac.authorization.k8s.io/aggregate-to-view: 'true' name: cert-manager-view diff --git a/_/CustomResourceDefinition/certificaterequests.cert-manager.io.yaml b/_/CustomResourceDefinition/certificaterequests.cert-manager.io.yaml index b185d15..cc33413 100644 --- a/_/CustomResourceDefinition/certificaterequests.cert-manager.io.yaml +++ b/_/CustomResourceDefinition/certificaterequests.cert-manager.io.yaml @@ -57,7 +57,7 @@ spec: description: >- A CertificateRequest is used to request a signed certificate from one of the configured issuers. - All fields within the CertificateRequest's `spec` are immutable after creation. A CertificateRequest will either succeed or fail, as denoted by its `status.state` field. + All fields within the CertificateRequest's `spec` are immutable after creation. A CertificateRequest will either succeed or fail, as denoted by its `Ready` status condition and its `status.failureTime` field. A CertificateRequest is a one-shot resource, meaning it represents a single point in time request for a certificate and cannot be re-used. properties: apiVersion: @@ -79,12 +79,16 @@ spec: metadata: type: object spec: - description: Desired state of the CertificateRequest resource. + description: >- + Specification of the desired state of the CertificateRequest + resource. + https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status properties: duration: description: >- - The requested 'duration' (i.e. lifetime) of the Certificate. - This option may be ignored/overridden by some issuer types. + Requested 'duration' (i.e. lifetime) of the Certificate. + Note that the issuer may choose to ignore the requested + duration, just like any other requested attribute. type: string extra: additionalProperties: @@ -107,22 +111,19 @@ spec: x-kubernetes-list-type: atomic isCA: description: >- - IsCA will request to mark the certificate as valid for - certificate signing when submitting to the issuer. This will - automatically add the `cert sign` usage to the list of - `usages`. + Requested basic constraints isCA value. Note that the issuer + may choose to ignore the requested isCA value, just like any + other requested attribute. + NOTE: If the CSR in the `Request` field has a BasicConstraints extension, it must have the same isCA value as specified here. + If true, this will automatically add the `cert sign` usage to the list of requested `usages`. type: boolean issuerRef: description: >- - IssuerRef is a reference to the issuer for this - CertificateRequest. If the `kind` field is not set, or set - to `Issuer`, an Issuer resource with the given name in the - same namespace as the CertificateRequest will be used. If - the `kind` field is set to `ClusterIssuer`, a ClusterIssuer - with the provided name will be used. The `name` field in - this stanza is required at all times. The group field refers - to the API group of the issuer which defaults to - `cert-manager.io` if empty. + Reference to the issuer responsible for issuing the + certificate. If the issuer is namespace-scoped, it must be + in the same namespace as the Certificate. If the issuer is + cluster-scoped, it can be used from any namespace. + The `name` field of the reference must always be specified. properties: group: description: Group of the resource being referred to. @@ -138,8 +139,9 @@ spec: type: object request: description: >- - The PEM-encoded x509 certificate signing request to be - submitted to the CA for signing. + The PEM-encoded X.509 certificate signing request to be + submitted to the issuer for signing. + If the CSR has a BasicConstraints extension, its isCA attribute must match the `isCA` value of this CertificateRequest. If the CSR has a KeyUsage extension, its key usages must match the key usages in the `usages` field of this CertificateRequest. If the CSR has a ExtKeyUsage extension, its extended key usages must match the extended key usages in the `usages` field of this CertificateRequest. format: byte type: string uid: @@ -149,11 +151,10 @@ spec: creation and immutable. type: string usages: - description: >- - Usages is the set of x509 usages that are requested for the - certificate. If usages are set they SHOULD be encoded inside - the CSR spec Defaults to `digital signature` and `key - encipherment` if not specified. + description: |- + Requested key usages and extended key usages. + NOTE: If the CSR in the `Request` field has uses the KeyUsage or ExtKeyUsage extension, these extensions must have the same values as specified here without any additional values. + If unset, defaults to `digital signature` and `key encipherment`. items: description: >- KeyUsage specifies valid usage contexts for keys. See: @@ -199,11 +200,12 @@ spec: status: description: >- Status of the CertificateRequest. This is set and managed - automatically. + automatically. Read-only. More info: + https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status properties: ca: description: >- - The PEM encoded x509 certificate of the signer, also known + The PEM encoded X.509 certificate of the signer, also known as the CA (Certificate Authority). This is set on a best-effort basis by different issuers. If not set, the CA is assumed to be unknown/not available. @@ -211,7 +213,7 @@ spec: type: string certificate: description: >- - The PEM encoded x509 certificate resulting from the + The PEM encoded X.509 certificate resulting from the certificate signing request. If not set, the CertificateRequest has either not been completed or has failed. More information on failure can be found by checking @@ -221,8 +223,8 @@ spec: conditions: description: >- List of status conditions to indicate the status of a - CertificateRequest. Known condition types are `Ready` and - `InvalidRequest`. + CertificateRequest. Known condition types are `Ready`, + `InvalidRequest`, `Approved` and `Denied`. items: description: >- CertificateRequestCondition contains condition information @@ -274,8 +276,6 @@ spec: format: date-time type: string type: object - required: - - spec type: object served: true storage: true diff --git a/_/CustomResourceDefinition/certificates.cert-manager.io.yaml b/_/CustomResourceDefinition/certificates.cert-manager.io.yaml index 6511af8..4369ce2 100644 --- a/_/CustomResourceDefinition/certificates.cert-manager.io.yaml +++ b/_/CustomResourceDefinition/certificates.cert-manager.io.yaml @@ -51,7 +51,7 @@ spec: openAPIV3Schema: description: >- A Certificate resource should be created to ensure an up to date and - signed x509 certificate is stored in the Kubernetes Secret resource + signed X.509 certificate is stored in the Kubernetes Secret resource named in `spec.secretName`. The stored certificate will be renewed before it expires (as configured by `spec.renewBefore`). properties: @@ -74,16 +74,16 @@ spec: metadata: type: object spec: - description: Desired state of the Certificate resource. + description: >- + Specification of the desired state of the Certificate resource. + https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status properties: additionalOutputFormats: description: >- - AdditionalOutputFormats defines extra output formats of the - private key and signed certificate chain to be written to - this Certificate's target Secret. This is an Alpha Feature - and is only enabled with the - `--feature-gates=AdditionalCertificateOutputFormats=true` - option on both the controller and webhook components. + Defines extra output formats of the private key and signed + certificate chain to be written to this Certificate's target + Secret. + This is an Alpha Feature and is only enabled with the `--feature-gates=AdditionalCertificateOutputFormats=true` option set on both the controller and webhook components. items: description: >- CertificateAdditionalOutputFormat defines an additional @@ -105,65 +105,58 @@ spec: type: array commonName: description: >- - CommonName is a common name to be used on the Certificate. - The CommonName should have a length of 64 characters or - fewer to avoid generating invalid CSRs. This value is - ignored by TLS clients when any subject alt name is set. - This is x509 behaviour: - https://tools.ietf.org/html/rfc6125#section-6.4.4 + Requested common name X509 certificate subject attribute. + More info: + https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.6 + NOTE: TLS clients will ignore this value when any subject + alternative name is set (see + https://tools.ietf.org/html/rfc6125#section-6.4.4). + Should have a length of 64 characters or fewer to avoid generating invalid CSRs. Cannot be set if the `literalSubject` field is set. type: string dnsNames: - description: >- - DNSNames is a list of DNS subjectAltNames to be set on the - Certificate. + description: Requested DNS subject alternative names. items: type: string type: array duration: description: >- - The requested 'duration' (i.e. lifetime) of the Certificate. - This option may be ignored/overridden by some issuer types. - If unset this defaults to 90 days. Certificate will be - renewed either 2/3 through its duration or `renewBefore` - period before its expiry, whichever is later. Minimum - accepted duration is 1 hour. Value must be in units accepted - by Go time.ParseDuration - https://golang.org/pkg/time/#ParseDuration + Requested 'duration' (i.e. lifetime) of the Certificate. + Note that the issuer may choose to ignore the requested + duration, just like any other requested attribute. + If unset, this defaults to 90 days. Minimum accepted duration is 1 hour. Value must be in units accepted by Go time.ParseDuration https://golang.org/pkg/time/#ParseDuration. type: string emailAddresses: - description: >- - EmailAddresses is a list of email subjectAltNames to be set - on the Certificate. + description: Requested email subject alternative names. items: type: string type: array encodeUsagesInRequest: description: >- - EncodeUsagesInRequest controls whether key usages should be - present in the CertificateRequest + Whether the KeyUsage and ExtKeyUsage extensions should be + set in the encoded CSR. + This option defaults to true, and should only be disabled if the target issuer does not support CSRs with these X509 KeyUsage/ ExtKeyUsage extensions. type: boolean ipAddresses: - description: >- - IPAddresses is a list of IP address subjectAltNames to be - set on the Certificate. + description: Requested IP address subject alternative names. items: type: string type: array isCA: description: >- - IsCA will mark this Certificate as valid for certificate - signing. This will automatically add the `cert sign` usage - to the list of `usages`. + Requested basic constraints isCA value. The isCA value is + used to set the `isCA` field on the created + CertificateRequest resources. Note that the issuer may + choose to ignore the requested isCA value, just like any + other requested attribute. + If true, this will automatically add the `cert sign` usage to the list of requested `usages`. type: boolean issuerRef: description: >- - IssuerRef is a reference to the issuer for this certificate. - If the `kind` field is not set, or set to `Issuer`, an - Issuer resource with the given name in the same namespace as - the Certificate will be used. If the `kind` field is set to - `ClusterIssuer`, a ClusterIssuer with the provided name will - be used. The `name` field in this stanza is required at all - times. + Reference to the issuer responsible for issuing the + certificate. If the issuer is namespace-scoped, it must be + in the same namespace as the Certificate. If the issuer is + cluster-scoped, it can be used from any namespace. + The `name` field of the reference must always be specified. properties: group: description: Group of the resource being referred to. @@ -179,8 +172,8 @@ spec: type: object keystores: description: >- - Keystores configures additional keystore output formats - stored in the `secretName` Secret resource. + Additional keystore output formats to be stored in the + Certificate's Secret. properties: jks: description: >- @@ -193,12 +186,12 @@ spec: Certificate. If true, a file named `keystore.jks` will be created in the target Secret resource, encrypted using the password stored in - `passwordSecretRef`. The keystore file will only be - updated upon re-issuance. A file named - `truststore.jks` will also be created in the target - Secret resource, encrypted using the password stored - in `passwordSecretRef` containing the issuing - Certificate Authority + `passwordSecretRef`. The keystore file will be + updated immediately. If the issuer provided a CA + certificate, a file named `truststore.jks` will also + be created in the target Secret resource, encrypted + using the password stored in `passwordSecretRef` + containing the issuing Certificate Authority type: boolean passwordSecretRef: description: >- @@ -237,12 +230,12 @@ spec: Certificate. If true, a file named `keystore.p12` will be created in the target Secret resource, encrypted using the password stored in - `passwordSecretRef`. The keystore file will only be - updated upon re-issuance. A file named - `truststore.p12` will also be created in the target - Secret resource, encrypted using the password stored - in `passwordSecretRef` containing the issuing - Certificate Authority + `passwordSecretRef`. The keystore file will be + updated immediately. If the issuer provided a CA + certificate, a file named `truststore.p12` will also + be created in the target Secret resource, encrypted + using the password stored in `passwordSecretRef` + containing the issuing Certificate Authority type: boolean passwordSecretRef: description: >- @@ -273,32 +266,28 @@ spec: type: object literalSubject: description: >- - LiteralSubject is an LDAP formatted string that represents - the [X.509 Subject - field](https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.6). - Use this *instead* of the Subject field if you need to - ensure the correct ordering of the RDN sequence, such as - when issuing certs for LDAP authentication. See - https://github.com/cert-manager/cert-manager/issues/3203, - https://github.com/cert-manager/cert-manager/issues/4424. - This field is alpha level and is only supported by - cert-manager installations where LiteralCertificateSubject - feature gate is enabled on both cert-manager controller and - webhook. + Requested X.509 certificate subject, represented using the + LDAP "String Representation of a Distinguished Name" [1]. + Important: the LDAP string format also specifies the order + of the attributes in the subject, this is important when + issuing certs for LDAP authentication. Example: + `CN=foo,DC=corp,DC=example,DC=com` More info [1]: + https://datatracker.ietf.org/doc/html/rfc4514 More info: + https://github.com/cert-manager/cert-manager/issues/3203 + More info: + https://github.com/cert-manager/cert-manager/issues/4424 + Cannot be set if the `subject` or `commonName` field is set. This is an Alpha Feature and is only enabled with the `--feature-gates=LiteralCertificateSubject=true` option set on both the controller and webhook components. type: string privateKey: - description: Options to control private keys used for the Certificate. + description: >- + Private key options. These include the key algorithm and + size, the used encoding and the rotation policy. properties: algorithm: description: >- Algorithm is the private key algorithm of the - corresponding private key for this certificate. If - provided, allowed values are either `RSA`,`Ed25519` or - `ECDSA` If `algorithm` is specified and `size` is not - provided, key size of 256 will be used for `ECDSA` key - algorithm and key size of 2048 will be used for `RSA` - key algorithm. key size is ignored when using the - `Ed25519` key algorithm. + corresponding private key for this certificate. + If provided, allowed values are either `RSA`, `ECDSA` or `Ed25519`. If `algorithm` is specified and `size` is not provided, key size of 2048 will be used for `RSA` key algorithm and key size of 256 will be used for `ECDSA` key algorithm. key size is ignored when using the `Ed25519` key algorithm. enum: - RSA - ECDSA @@ -307,10 +296,8 @@ spec: encoding: description: >- The private key cryptography standards (PKCS) encoding - for this certificate's private key to be encoded in. If - provided, allowed values are `PKCS1` and `PKCS8` - standing for PKCS#1 and PKCS#8, respectively. Defaults - to `PKCS1` if not specified. + for this certificate's private key to be encoded in. + If provided, allowed values are `PKCS1` and `PKCS8` standing for PKCS#1 and PKCS#8, respectively. Defaults to `PKCS1` if not specified. enum: - PKCS1 - PKCS8 @@ -318,15 +305,8 @@ spec: rotationPolicy: description: >- RotationPolicy controls how private keys should be - regenerated when a re-issuance is being processed. If - set to Never, a private key will only be generated if - one does not already exist in the target - `spec.secretName`. If one does exists but it does not - have the correct algorithm or size, a warning will be - raised to await user intervention. If set to Always, a - private key matching the specified requirements will be - generated whenever a re-issuance occurs. Default is - 'Never' for backward compatibility. + regenerated when a re-issuance is being processed. + If set to `Never`, a private key will only be generated if one does not already exist in the target `spec.secretName`. If one does exists but it does not have the correct algorithm or size, a warning will be raised to await user intervention. If set to `Always`, a private key matching the specified requirements will be generated whenever a re-issuance occurs. Default is `Never` for backward compatibility. enum: - Never - Always @@ -334,51 +314,48 @@ spec: size: description: >- Size is the key bit size of the corresponding private - key for this certificate. If `algorithm` is set to - `RSA`, valid values are `2048`, `4096` or `8192`, and - will default to `2048` if not specified. If `algorithm` - is set to `ECDSA`, valid values are `256`, `384` or - `521`, and will default to `256` if not specified. If - `algorithm` is set to `Ed25519`, Size is ignored. No - other values are allowed. + key for this certificate. + If `algorithm` is set to `RSA`, valid values are `2048`, `4096` or `8192`, and will default to `2048` if not specified. If `algorithm` is set to `ECDSA`, valid values are `256`, `384` or `521`, and will default to `256` if not specified. If `algorithm` is set to `Ed25519`, Size is ignored. No other values are allowed. type: integer type: object renewBefore: description: >- How long before the currently issued certificate's expiry - cert-manager should renew the certificate. The default is - 2/3 of the issued certificate's duration. Minimum accepted - value is 5 minutes. Value must be in units accepted by Go - time.ParseDuration - https://golang.org/pkg/time/#ParseDuration + cert-manager should renew the certificate. For example, if a + certificate is valid for 60 minutes, and `renewBefore=10m`, + cert-manager will begin to attempt to renew the certificate + 50 minutes after it was issued (i.e. when there are 10 + minutes remaining until the certificate is no longer + valid). + NOTE: The actual lifetime of the issued certificate is used to determine the renewal time. If an issuer returns a certificate with a different lifetime than the one requested, cert-manager will use the lifetime of the issued certificate. + If unset, this defaults to 1/3 of the issued certificate's lifetime. Minimum accepted value is 5 minutes. Value must be in units accepted by Go time.ParseDuration https://golang.org/pkg/time/#ParseDuration. type: string revisionHistoryLimit: description: >- - revisionHistoryLimit is the maximum number of - CertificateRequest revisions that are maintained in the - Certificate's history. Each revision represents a single - `CertificateRequest` created by this Certificate, either - when it was created, renewed, or Spec was changed. Revisions - will be removed by oldest first if the number of revisions - exceeds this number. If set, revisionHistoryLimit must be a - value of `1` or greater. If unset (`nil`), revisions will - not be garbage collected. Default value is `nil`. + The maximum number of CertificateRequest revisions that are + maintained in the Certificate's history. Each revision + represents a single `CertificateRequest` created by this + Certificate, either when it was created, renewed, or Spec + was changed. Revisions will be removed by oldest first if + the number of revisions exceeds this number. + If set, revisionHistoryLimit must be a value of `1` or greater. If unset (`nil`), revisions will not be garbage collected. Default value is `nil`. format: int32 type: integer secretName: description: >- - SecretName is the name of the secret resource that will be - automatically created and managed by this Certificate - resource. It will be populated with a private key and - certificate, signed by the denoted issuer. + Name of the Secret resource that will be automatically + created and managed by this Certificate resource. It will be + populated with a private key and certificate, signed by the + denoted issuer. The Secret resource lives in the same + namespace as the Certificate resource. type: string secretTemplate: description: >- - SecretTemplate defines annotations and labels to be copied - to the Certificate's Secret. Labels and annotations on the - Secret will be changed as they appear on the SecretTemplate - when added or removed. SecretTemplate annotations are added - in conjunction with, and cannot overwrite, the base set of + Defines annotations and labels to be copied to the + Certificate's Secret. Labels and annotations on the Secret + will be changed as they appear on the SecretTemplate when + added or removed. SecretTemplate annotations are added in + conjunction with, and cannot overwrite, the base set of annotations cert-manager sets on the Certificate's Secret. properties: annotations: @@ -398,8 +375,10 @@ spec: type: object subject: description: >- - Full X509 name specification - (https://golang.org/pkg/crypto/x509/pkix/#Name). + Requested set of X509 certificate subject attributes. More + info: + https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.6 + The common name attribute is specified separately in the `commonName` field. Cannot be set if the `literalSubject` field is set. properties: countries: description: Countries to be used on the Certificate. @@ -441,17 +420,18 @@ spec: type: array type: object uris: - description: >- - URIs is a list of URI subjectAltNames to be set on the - Certificate. + description: Requested URI subject alternative names. items: type: string type: array usages: description: >- - Usages is the set of x509 usages that are requested for the - certificate. Defaults to `digital signature` and `key - encipherment` if not specified. + Requested key usages and extended key usages. These usages + are used to set the `usages` field on the created + CertificateRequest resources. If `encodeUsagesInRequest` is + unset or set to `true`, the usages will additionally be + encoded in the `request` field which contains the CSR blob. + If unset, defaults to `digital signature` and `key encipherment`. items: description: >- KeyUsage specifies valid usage contexts for keys. See: @@ -491,7 +471,8 @@ spec: status: description: >- Status of the Certificate. This is set and managed - automatically. + automatically. Read-only. More info: + https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status properties: conditions: description: >- @@ -562,11 +543,12 @@ spec: type: integer lastFailureTime: description: >- - LastFailureTime is the time as recorded by the Certificate - controller of the most recent failure to complete a - CertificateRequest for this Certificate resource. If set, - cert-manager will not re-request another Certificate until 1 - hour has elapsed from this time. + LastFailureTime is set only if the lastest issuance for this + Certificate failed and contains the time of the failure. If + an issuance has failed, the delay till the next issuance + will be calculated using formula time.Hour * 2 ^ + (failedIssuanceAttempts - 1). If the latest issuance has + succeeded this field will be unset. format: date-time type: string nextPrivateKeySecretName: @@ -587,7 +569,7 @@ spec: notBefore: description: >- The time after which the certificate stored in the secret - named by this resource in spec.secretName is valid. + named by this resource in `spec.secretName` is valid. format: date-time type: string renewalTime: @@ -604,8 +586,6 @@ spec: Persisting the value on the CertificateRequest resource allows the certificates controller to know whether a request is part of an old issuance or if it is part of the ongoing revision's issuance by checking if the revision value in the annotation is greater than this field. type: integer type: object - required: - - spec type: object served: true storage: true diff --git a/_/CustomResourceDefinition/challenges.acme.cert-manager.io.yaml b/_/CustomResourceDefinition/challenges.acme.cert-manager.io.yaml index 0191291..b845fd1 100644 --- a/_/CustomResourceDefinition/challenges.acme.cert-manager.io.yaml +++ b/_/CustomResourceDefinition/challenges.acme.cert-manager.io.yaml @@ -646,22 +646,27 @@ spec: which parentRefs should be used when creating the HTTPRoute. Usually, the parentRef references a Gateway. See: - https://gateway-api.sigs.k8s.io/v1alpha2/api-types/httproute/#attaching-to-gateways + https://gateway-api.sigs.k8s.io/api-types/httproute/#attaching-to-gateways items: description: >- ParentReference identifies an API object (usually a Gateway) that can be considered a - parent of this resource (usually a route). The - only kind of parent resource with "Core" - support is Gateway. This API may be extended - in the future to support additional kinds of - parent resources, such as HTTPRoute. + parent of this resource (usually a route). + There are two kinds of parent resources with + "Core" support: + * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) + This API may be extended in the future to support additional kinds of parent resources. The API object must be valid in the cluster; the Group and Kind must be registered in the cluster for this reference to be valid. properties: group: default: gateway.networking.k8s.io - description: |- - Group is the group of the referent. + description: >- + Group is the group of the referent. When + unspecified, "gateway.networking.k8s.io" + is inferred. To set the core API group + (such as for a "Service" kind referent), + Group must be explicitly set to "" (empty + string). Support: Core maxLength: 253 pattern: >- @@ -671,8 +676,9 @@ spec: default: Gateway description: |- Kind is kind of the referent. - Support: Core (Gateway) - Support: Custom (Other Resources) + There are two kinds of parent resources with "Core" support: + * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) + Support for other resources is Implementation-Specific. maxLength: 63 minLength: 1 pattern: '^[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?$' @@ -687,9 +693,11 @@ spec: namespace: description: >- Namespace is the namespace of the - referent. When unspecified (or empty - string), this refers to the local - namespace of the Route. + referent. When unspecified, this refers to + the local namespace of the Route. + Note that there are specific rules for ParentRefs which cross namespace boundaries. Cross-namespace references are only valid if they are explicitly allowed by something in the namespace they are referring to. For example: Gateway has the AllowedRoutes field, and ReferenceGrant provides a generic way to enable any other kind of cross-namespace reference. + ParentRefs from a Route to a Service in the same namespace are "producer" routes, which apply default routing rules to inbound connections from any namespace to the Service. + ParentRefs from a Route to a Service in a different namespace are "consumer" routes, and these routing rules are only applied to outbound connections originating from the same namespace as the Route, for which the intended destination of the connections are a Service targeted as a ParentRef of the Route. Support: Core maxLength: 63 minLength: 1 @@ -701,6 +709,7 @@ spec: targets. It can be interpreted differently based on the type of parent resource. When the parent resource is a Gateway, this targets all listeners listening on the specified port that also support this kind of Route(and select this Route). It's not recommended to set `Port` unless the networking behaviors specified in a Route must apply to a specific port as opposed to a listener(s) whose port(s) may be changed. When both Port and SectionName are specified, the name and port of the selected listener must match both specified values. + When the parent resource is a Service, this targets a specific port in the Service spec. When both Port (experimental) and SectionName are specified, the name and port of the selected port must match both specified values. Implementations MAY choose to support other parent resources. Implementations supporting other types of parent resources MUST clearly document how/if Port is interpreted. For the purpose of status, an attachment is considered successful as long as the parent resource accepts it partially. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Extended @@ -715,7 +724,7 @@ spec: within the target resource. In the following resources, SectionName is interpreted as the following: - * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. + * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. * Service: Port Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. Note that attaching Routes to Services as Parents is part of experimental Mesh support and is not supported for any other purpose. Implementations MAY choose to support attaching Routes to other resources. If that is the case, they MUST clearly document how SectionName is interpreted. When unspecified (empty string), this will reference the entire resource. For the purpose of status, an attachment is considered successful if at least one section in the parent resource accepts it. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Core @@ -746,10 +755,21 @@ spec: properties: class: description: >- - The ingress class to use when creating Ingress - resources to solve ACME challenges that use this - challenge solver. Only one of 'class' or 'name' - may be specified. + This field configures the annotation + `kubernetes.io/ingress.class` when creating + Ingress resources to solve ACME challenges that + use this challenge solver. Only one of `class`, + `name` or `ingressClassName` may be specified. + type: string + ingressClassName: + description: >- + This field configures the field + `ingressClassName` on the created Ingress + resources used to solve ACME challenges that use + this challenge solver. This is the recommended + way of configuring the ingress class. Only one + of `class`, `name` or `ingressClassName` may be + specified. type: string ingressTemplate: description: >- @@ -790,7 +810,8 @@ spec: typically used in conjunction with ingress controllers like ingress-gce, which maintains a 1:1 mapping between external IPs and ingress - resources. + resources. Only one of `class`, `name` or + `ingressClassName` may be specified. type: string podTemplate: description: >- @@ -825,11 +846,10 @@ spec: spec: description: >- PodSpec defines overrides for the HTTP01 - challenge solver pod. Only the - 'priorityClassName', 'nodeSelector', - 'affinity', 'serviceAccountName' and - 'tolerations' fields are supported - currently. All other fields will be ignored. + challenge solver pod. Check + ACMEChallengeSolverHTTP01IngressPodSpec to + find out currently supported fields. All + other fields will be ignored. properties: affinity: description: >- @@ -1854,6 +1874,25 @@ spec: type: array type: object type: object + imagePullSecrets: + description: 'If specified, the pod''s imagePullSecrets' + items: + description: >- + LocalObjectReference contains enough + information to let you locate the + referenced object inside the same + namespace. + properties: + name: + description: >- + Name of the referent. More info: + https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names + TODO: Add other useful fields. + apiVersion, kind, uid? + type: string + type: object + x-kubernetes-map-type: atomic + type: array nodeSelector: additionalProperties: type: string diff --git a/_/CustomResourceDefinition/clusterissuers.cert-manager.io.yaml b/_/CustomResourceDefinition/clusterissuers.cert-manager.io.yaml index e819129..7a6673a 100644 --- a/_/CustomResourceDefinition/clusterissuers.cert-manager.io.yaml +++ b/_/CustomResourceDefinition/clusterissuers.cert-manager.io.yaml @@ -72,6 +72,17 @@ spec: ACME configures this issuer to communicate with a RFC8555 (ACME) server to obtain signed x509 certificates. properties: + caBundle: + description: >- + Base64-encoded bundle of PEM CAs which can be used to + validate the certificate chain presented by the ACME + server. Mutually exclusive with SkipTLSVerify; prefer + using CABundle to prevent various kinds of security + vulnerabilities. If CABundle and SkipTLSVerify are + unset, the system certificate bundle inside the + container is used to validate the TLS connection. + format: byte + type: string disableAccountKeyGeneration: description: >- Enables or disables generating a new ACME account key. @@ -199,13 +210,15 @@ spec: type: string skipTLSVerify: description: >- - Enables or disables validation of the ACME server TLS - certificate. If true, requests to the ACME server will - not have their TLS certificate validated (i.e. insecure - connections will be allowed). Only enable this option in - development environments. The cert-manager system - installed roots will be used to verify connections to - the ACME server if this is false. Defaults to false. + INSECURE: Enables or disables validation of the ACME + server TLS certificate. If true, requests to the ACME + server will not have the TLS certificate chain + validated. Mutually exclusive with CABundle; prefer + using CABundle to prevent various kinds of security + vulnerabilities. Only enable this option in development + environments. If CABundle and SkipTLSVerify are unset, + the system certificate bundle inside the container is + used to validate the TLS connection. Defaults to false. type: boolean solvers: description: >- @@ -773,23 +786,28 @@ spec: parentRefs should be used when creating the HTTPRoute. Usually, the parentRef references a Gateway. See: - https://gateway-api.sigs.k8s.io/v1alpha2/api-types/httproute/#attaching-to-gateways + https://gateway-api.sigs.k8s.io/api-types/httproute/#attaching-to-gateways items: description: >- ParentReference identifies an API object (usually a Gateway) that can be considered a parent of this resource - (usually a route). The only kind of - parent resource with "Core" support is - Gateway. This API may be extended in the - future to support additional kinds of - parent resources, such as HTTPRoute. + (usually a route). There are two kinds + of parent resources with "Core" + support: + * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) + This API may be extended in the future to support additional kinds of parent resources. The API object must be valid in the cluster; the Group and Kind must be registered in the cluster for this reference to be valid. properties: group: default: gateway.networking.k8s.io - description: |- - Group is the group of the referent. + description: >- + Group is the group of the referent. When + unspecified, "gateway.networking.k8s.io" + is inferred. To set the core API group + (such as for a "Service" kind referent), + Group must be explicitly set to "" + (empty string). Support: Core maxLength: 253 pattern: >- @@ -799,8 +817,9 @@ spec: default: Gateway description: |- Kind is kind of the referent. - Support: Core (Gateway) - Support: Custom (Other Resources) + There are two kinds of parent resources with "Core" support: + * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) + Support for other resources is Implementation-Specific. maxLength: 63 minLength: 1 pattern: '^[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?$' @@ -815,9 +834,11 @@ spec: namespace: description: >- Namespace is the namespace of the - referent. When unspecified (or empty - string), this refers to the local - namespace of the Route. + referent. When unspecified, this refers + to the local namespace of the Route. + Note that there are specific rules for ParentRefs which cross namespace boundaries. Cross-namespace references are only valid if they are explicitly allowed by something in the namespace they are referring to. For example: Gateway has the AllowedRoutes field, and ReferenceGrant provides a generic way to enable any other kind of cross-namespace reference. + ParentRefs from a Route to a Service in the same namespace are "producer" routes, which apply default routing rules to inbound connections from any namespace to the Service. + ParentRefs from a Route to a Service in a different namespace are "consumer" routes, and these routing rules are only applied to outbound connections originating from the same namespace as the Route, for which the intended destination of the connections are a Service targeted as a ParentRef of the Route. Support: Core maxLength: 63 minLength: 1 @@ -830,6 +851,7 @@ spec: differently based on the type of parent resource. When the parent resource is a Gateway, this targets all listeners listening on the specified port that also support this kind of Route(and select this Route). It's not recommended to set `Port` unless the networking behaviors specified in a Route must apply to a specific port as opposed to a listener(s) whose port(s) may be changed. When both Port and SectionName are specified, the name and port of the selected listener must match both specified values. + When the parent resource is a Service, this targets a specific port in the Service spec. When both Port (experimental) and SectionName are specified, the name and port of the selected port must match both specified values. Implementations MAY choose to support other parent resources. Implementations supporting other types of parent resources MUST clearly document how/if Port is interpreted. For the purpose of status, an attachment is considered successful as long as the parent resource accepts it partially. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Extended @@ -844,7 +866,7 @@ spec: within the target resource. In the following resources, SectionName is interpreted as the following: - * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. + * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. * Service: Port Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. Note that attaching Routes to Services as Parents is part of experimental Mesh support and is not supported for any other purpose. Implementations MAY choose to support attaching Routes to other resources. If that is the case, they MUST clearly document how SectionName is interpreted. When unspecified (empty string), this will reference the entire resource. For the purpose of status, an attachment is considered successful if at least one section in the parent resource accepts it. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Core @@ -877,10 +899,22 @@ spec: properties: class: description: >- - The ingress class to use when creating - Ingress resources to solve ACME challenges - that use this challenge solver. Only one - of 'class' or 'name' may be specified. + This field configures the annotation + `kubernetes.io/ingress.class` when + creating Ingress resources to solve ACME + challenges that use this challenge solver. + Only one of `class`, `name` or + `ingressClassName` may be specified. + type: string + ingressClassName: + description: >- + This field configures the field + `ingressClassName` on the created Ingress + resources used to solve ACME challenges + that use this challenge solver. This is + the recommended way of configuring the + ingress class. Only one of `class`, `name` + or `ingressClassName` may be specified. type: string ingressTemplate: description: >- @@ -922,7 +956,8 @@ spec: conjunction with ingress controllers like ingress-gce, which maintains a 1:1 mapping between external IPs and ingress - resources. + resources. Only one of `class`, `name` or + `ingressClassName` may be specified. type: string podTemplate: description: >- @@ -957,12 +992,10 @@ spec: spec: description: >- PodSpec defines overrides for the HTTP01 - challenge solver pod. Only the - 'priorityClassName', 'nodeSelector', - 'affinity', 'serviceAccountName' and - 'tolerations' fields are supported - currently. All other fields will be - ignored. + challenge solver pod. Check + ACMEChallengeSolverHTTP01IngressPodSpec + to find out currently supported fields. + All other fields will be ignored. properties: affinity: description: >- @@ -1987,6 +2020,25 @@ spec: type: array type: object type: object + imagePullSecrets: + description: 'If specified, the pod''s imagePullSecrets' + items: + description: >- + LocalObjectReference contains enough + information to let you locate the + referenced object inside the same + namespace. + properties: + name: + description: >- + Name of the referent. More info: + https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names + TODO: Add other useful fields. + apiVersion, kind, uid? + type: string + type: object + x-kubernetes-map-type: atomic + type: array nodeSelector: additionalProperties: type: string @@ -2282,9 +2334,26 @@ spec: required: - name type: object + serviceAccountRef: + description: >- + A reference to a service account that will be + used to request a bound token (also known as + "projected token"). Compared to using + "secretRef", using this field means that you + don't rely on statically bound tokens. To use + this field, you must configure an RBAC rule to + let cert-manager request a token. + properties: + name: + description: >- + Name of the ServiceAccount used to request a + token. + type: string + required: + - name + type: object required: - role - - secretRef type: object tokenSecretRef: description: >- @@ -2310,27 +2379,26 @@ spec: type: object caBundle: description: >- - PEM-encoded CA bundle (base64-encoded) used to validate - Vault server certificate. Only used if the Server URL is - using HTTPS protocol. This parameter is ignored for - plain HTTP protocol connection. If not set the system - root certificates are used to validate the TLS - connection. Mutually exclusive with CABundleSecretRef. - If neither CABundle nor CABundleSecretRef are defined, - the cert-manager controller system root certificates are - used to validate the TLS connection. + Base64-encoded bundle of PEM CAs which will be used to + validate the certificate chain presented by Vault. Only + used if using HTTPS to connect to Vault and ignored for + HTTP connections. Mutually exclusive with + CABundleSecretRef. If neither CABundle nor + CABundleSecretRef are defined, the certificate bundle in + the cert-manager controller container is used to + validate the TLS connection. format: byte type: string caBundleSecretRef: description: >- - CABundleSecretRef is a reference to a Secret which - contains the CABundle which will be used when connecting - to Vault when using HTTPS. Mutually exclusive with - CABundle. If neither CABundleSecretRef nor CABundle are - defined, the cert-manager controller system root - certificates are used to validate the TLS connection. If - no key for the Secret is specified, cert-manager will - default to 'ca.crt'. + Reference to a Secret containing a bundle of PEM-encoded + CAs to use when verifying the certificate chain + presented by Vault when using HTTPS. Mutually exclusive + with CABundle. If neither CABundle nor CABundleSecretRef + are defined, the certificate bundle in the cert-manager + controller container is used to validate the TLS + connection. If no key for the Secret is specified, + cert-manager will default to 'ca.crt'. properties: key: description: >- @@ -2415,13 +2483,12 @@ spec: properties: caBundle: description: >- - CABundle is a PEM encoded TLS certificate to use to - verify connections to the TPP instance. If - specified, system roots will not be used and the - issuing CA for the TPP instance must be verifiable - using the provided root. If not specified, the - connection will be verified using the cert-manager - system root certificates. + Base64-encoded bundle of PEM CAs which will be used + to validate the certificate chain presented by the + TPP server. Only used if using HTTPS; ignored for + HTTP. If undefined, the certificate bundle in the + cert-manager controller container is used to + validate the chain. format: byte type: string credentialsRef: @@ -2472,6 +2539,13 @@ spec: if the Issuer is configured to use an ACME server to issue certificates. properties: + lastPrivateKeyHash: + description: >- + LastPrivateKeyHash is a hash of the private key + associated with the latest registered ACME account, in + order to track changes made to registered account + associated with the Issuer + type: string lastRegisteredEmail: description: >- LastRegisteredEmail is the email associated with the diff --git a/_/CustomResourceDefinition/issuers.cert-manager.io.yaml b/_/CustomResourceDefinition/issuers.cert-manager.io.yaml index 2f7a93e..b104e7f 100644 --- a/_/CustomResourceDefinition/issuers.cert-manager.io.yaml +++ b/_/CustomResourceDefinition/issuers.cert-manager.io.yaml @@ -71,6 +71,17 @@ spec: ACME configures this issuer to communicate with a RFC8555 (ACME) server to obtain signed x509 certificates. properties: + caBundle: + description: >- + Base64-encoded bundle of PEM CAs which can be used to + validate the certificate chain presented by the ACME + server. Mutually exclusive with SkipTLSVerify; prefer + using CABundle to prevent various kinds of security + vulnerabilities. If CABundle and SkipTLSVerify are + unset, the system certificate bundle inside the + container is used to validate the TLS connection. + format: byte + type: string disableAccountKeyGeneration: description: >- Enables or disables generating a new ACME account key. @@ -198,13 +209,15 @@ spec: type: string skipTLSVerify: description: >- - Enables or disables validation of the ACME server TLS - certificate. If true, requests to the ACME server will - not have their TLS certificate validated (i.e. insecure - connections will be allowed). Only enable this option in - development environments. The cert-manager system - installed roots will be used to verify connections to - the ACME server if this is false. Defaults to false. + INSECURE: Enables or disables validation of the ACME + server TLS certificate. If true, requests to the ACME + server will not have the TLS certificate chain + validated. Mutually exclusive with CABundle; prefer + using CABundle to prevent various kinds of security + vulnerabilities. Only enable this option in development + environments. If CABundle and SkipTLSVerify are unset, + the system certificate bundle inside the container is + used to validate the TLS connection. Defaults to false. type: boolean solvers: description: >- @@ -772,23 +785,28 @@ spec: parentRefs should be used when creating the HTTPRoute. Usually, the parentRef references a Gateway. See: - https://gateway-api.sigs.k8s.io/v1alpha2/api-types/httproute/#attaching-to-gateways + https://gateway-api.sigs.k8s.io/api-types/httproute/#attaching-to-gateways items: description: >- ParentReference identifies an API object (usually a Gateway) that can be considered a parent of this resource - (usually a route). The only kind of - parent resource with "Core" support is - Gateway. This API may be extended in the - future to support additional kinds of - parent resources, such as HTTPRoute. + (usually a route). There are two kinds + of parent resources with "Core" + support: + * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) + This API may be extended in the future to support additional kinds of parent resources. The API object must be valid in the cluster; the Group and Kind must be registered in the cluster for this reference to be valid. properties: group: default: gateway.networking.k8s.io - description: |- - Group is the group of the referent. + description: >- + Group is the group of the referent. When + unspecified, "gateway.networking.k8s.io" + is inferred. To set the core API group + (such as for a "Service" kind referent), + Group must be explicitly set to "" + (empty string). Support: Core maxLength: 253 pattern: >- @@ -798,8 +816,9 @@ spec: default: Gateway description: |- Kind is kind of the referent. - Support: Core (Gateway) - Support: Custom (Other Resources) + There are two kinds of parent resources with "Core" support: + * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) + Support for other resources is Implementation-Specific. maxLength: 63 minLength: 1 pattern: '^[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?$' @@ -814,9 +833,11 @@ spec: namespace: description: >- Namespace is the namespace of the - referent. When unspecified (or empty - string), this refers to the local - namespace of the Route. + referent. When unspecified, this refers + to the local namespace of the Route. + Note that there are specific rules for ParentRefs which cross namespace boundaries. Cross-namespace references are only valid if they are explicitly allowed by something in the namespace they are referring to. For example: Gateway has the AllowedRoutes field, and ReferenceGrant provides a generic way to enable any other kind of cross-namespace reference. + ParentRefs from a Route to a Service in the same namespace are "producer" routes, which apply default routing rules to inbound connections from any namespace to the Service. + ParentRefs from a Route to a Service in a different namespace are "consumer" routes, and these routing rules are only applied to outbound connections originating from the same namespace as the Route, for which the intended destination of the connections are a Service targeted as a ParentRef of the Route. Support: Core maxLength: 63 minLength: 1 @@ -829,6 +850,7 @@ spec: differently based on the type of parent resource. When the parent resource is a Gateway, this targets all listeners listening on the specified port that also support this kind of Route(and select this Route). It's not recommended to set `Port` unless the networking behaviors specified in a Route must apply to a specific port as opposed to a listener(s) whose port(s) may be changed. When both Port and SectionName are specified, the name and port of the selected listener must match both specified values. + When the parent resource is a Service, this targets a specific port in the Service spec. When both Port (experimental) and SectionName are specified, the name and port of the selected port must match both specified values. Implementations MAY choose to support other parent resources. Implementations supporting other types of parent resources MUST clearly document how/if Port is interpreted. For the purpose of status, an attachment is considered successful as long as the parent resource accepts it partially. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Extended @@ -843,7 +865,7 @@ spec: within the target resource. In the following resources, SectionName is interpreted as the following: - * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. + * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. * Service: Port Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. Note that attaching Routes to Services as Parents is part of experimental Mesh support and is not supported for any other purpose. Implementations MAY choose to support attaching Routes to other resources. If that is the case, they MUST clearly document how SectionName is interpreted. When unspecified (empty string), this will reference the entire resource. For the purpose of status, an attachment is considered successful if at least one section in the parent resource accepts it. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Core @@ -876,10 +898,22 @@ spec: properties: class: description: >- - The ingress class to use when creating - Ingress resources to solve ACME challenges - that use this challenge solver. Only one - of 'class' or 'name' may be specified. + This field configures the annotation + `kubernetes.io/ingress.class` when + creating Ingress resources to solve ACME + challenges that use this challenge solver. + Only one of `class`, `name` or + `ingressClassName` may be specified. + type: string + ingressClassName: + description: >- + This field configures the field + `ingressClassName` on the created Ingress + resources used to solve ACME challenges + that use this challenge solver. This is + the recommended way of configuring the + ingress class. Only one of `class`, `name` + or `ingressClassName` may be specified. type: string ingressTemplate: description: >- @@ -921,7 +955,8 @@ spec: conjunction with ingress controllers like ingress-gce, which maintains a 1:1 mapping between external IPs and ingress - resources. + resources. Only one of `class`, `name` or + `ingressClassName` may be specified. type: string podTemplate: description: >- @@ -956,12 +991,10 @@ spec: spec: description: >- PodSpec defines overrides for the HTTP01 - challenge solver pod. Only the - 'priorityClassName', 'nodeSelector', - 'affinity', 'serviceAccountName' and - 'tolerations' fields are supported - currently. All other fields will be - ignored. + challenge solver pod. Check + ACMEChallengeSolverHTTP01IngressPodSpec + to find out currently supported fields. + All other fields will be ignored. properties: affinity: description: >- @@ -1986,6 +2019,25 @@ spec: type: array type: object type: object + imagePullSecrets: + description: 'If specified, the pod''s imagePullSecrets' + items: + description: >- + LocalObjectReference contains enough + information to let you locate the + referenced object inside the same + namespace. + properties: + name: + description: >- + Name of the referent. More info: + https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names + TODO: Add other useful fields. + apiVersion, kind, uid? + type: string + type: object + x-kubernetes-map-type: atomic + type: array nodeSelector: additionalProperties: type: string @@ -2281,9 +2333,26 @@ spec: required: - name type: object + serviceAccountRef: + description: >- + A reference to a service account that will be + used to request a bound token (also known as + "projected token"). Compared to using + "secretRef", using this field means that you + don't rely on statically bound tokens. To use + this field, you must configure an RBAC rule to + let cert-manager request a token. + properties: + name: + description: >- + Name of the ServiceAccount used to request a + token. + type: string + required: + - name + type: object required: - role - - secretRef type: object tokenSecretRef: description: >- @@ -2309,27 +2378,26 @@ spec: type: object caBundle: description: >- - PEM-encoded CA bundle (base64-encoded) used to validate - Vault server certificate. Only used if the Server URL is - using HTTPS protocol. This parameter is ignored for - plain HTTP protocol connection. If not set the system - root certificates are used to validate the TLS - connection. Mutually exclusive with CABundleSecretRef. - If neither CABundle nor CABundleSecretRef are defined, - the cert-manager controller system root certificates are - used to validate the TLS connection. + Base64-encoded bundle of PEM CAs which will be used to + validate the certificate chain presented by Vault. Only + used if using HTTPS to connect to Vault and ignored for + HTTP connections. Mutually exclusive with + CABundleSecretRef. If neither CABundle nor + CABundleSecretRef are defined, the certificate bundle in + the cert-manager controller container is used to + validate the TLS connection. format: byte type: string caBundleSecretRef: description: >- - CABundleSecretRef is a reference to a Secret which - contains the CABundle which will be used when connecting - to Vault when using HTTPS. Mutually exclusive with - CABundle. If neither CABundleSecretRef nor CABundle are - defined, the cert-manager controller system root - certificates are used to validate the TLS connection. If - no key for the Secret is specified, cert-manager will - default to 'ca.crt'. + Reference to a Secret containing a bundle of PEM-encoded + CAs to use when verifying the certificate chain + presented by Vault when using HTTPS. Mutually exclusive + with CABundle. If neither CABundle nor CABundleSecretRef + are defined, the certificate bundle in the cert-manager + controller container is used to validate the TLS + connection. If no key for the Secret is specified, + cert-manager will default to 'ca.crt'. properties: key: description: >- @@ -2414,13 +2482,12 @@ spec: properties: caBundle: description: >- - CABundle is a PEM encoded TLS certificate to use to - verify connections to the TPP instance. If - specified, system roots will not be used and the - issuing CA for the TPP instance must be verifiable - using the provided root. If not specified, the - connection will be verified using the cert-manager - system root certificates. + Base64-encoded bundle of PEM CAs which will be used + to validate the certificate chain presented by the + TPP server. Only used if using HTTPS; ignored for + HTTP. If undefined, the certificate bundle in the + cert-manager controller container is used to + validate the chain. format: byte type: string credentialsRef: @@ -2469,6 +2536,13 @@ spec: if the Issuer is configured to use an ACME server to issue certificates. properties: + lastPrivateKeyHash: + description: >- + LastPrivateKeyHash is a hash of the private key + associated with the latest registered ACME account, in + order to track changes made to registered account + associated with the Issuer + type: string lastRegisteredEmail: description: >- LastRegisteredEmail is the email associated with the diff --git a/_/ValidatingWebhookConfiguration/cert-manager-webhook.yaml b/_/ValidatingWebhookConfiguration/cert-manager-webhook.yaml index 5109748..75c7391 100644 --- a/_/ValidatingWebhookConfiguration/cert-manager-webhook.yaml +++ b/_/ValidatingWebhookConfiguration/cert-manager-webhook.yaml @@ -29,10 +29,6 @@ webhooks: operator: NotIn values: - 'true' - - key: name - operator: NotIn - values: - - cert-manager rules: - apiGroups: - cert-manager.io diff --git a/cert-manager/ConfigMap/cert-manager-webhook.yaml b/cert-manager/ConfigMap/cert-manager-webhook.yaml index b1d0ec0..cec4cf9 100644 --- a/cert-manager/ConfigMap/cert-manager-webhook.yaml +++ b/cert-manager/ConfigMap/cert-manager-webhook.yaml @@ -6,6 +6,9 @@ metadata: app: webhook app.kubernetes.io/component: webhook app.kubernetes.io/instance: cert-manager + app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: webhook + app.kubernetes.io/version: v1.10.1 + helm.sh/chart: cert-manager-v1.10.1 name: cert-manager-webhook namespace: cert-manager diff --git a/cert-manager/ConfigMap/cert-manager.yaml b/cert-manager/ConfigMap/cert-manager.yaml new file mode 100644 index 0000000..465c5f8 --- /dev/null +++ b/cert-manager/ConfigMap/cert-manager.yaml @@ -0,0 +1,14 @@ +apiVersion: v1 +data: null +kind: ConfigMap +metadata: + labels: + app: cert-manager + app.kubernetes.io/component: controller + app.kubernetes.io/instance: cert-manager + app.kubernetes.io/managed-by: Helm + app.kubernetes.io/name: cert-manager + app.kubernetes.io/version: v1.10.1 + helm.sh/chart: cert-manager-v1.10.1 + name: cert-manager + namespace: cert-manager diff --git a/cert-manager/Deployment/cert-manager-cainjector.yaml b/cert-manager/Deployment/cert-manager-cainjector.yaml index 64c86f1..7b38270 100644 --- a/cert-manager/Deployment/cert-manager-cainjector.yaml +++ b/cert-manager/Deployment/cert-manager-cainjector.yaml @@ -46,6 +46,7 @@ spec: capabilities: drop: - ALL + enableServiceLinks: false nodeSelector: kubernetes.io/os: linux securityContext: diff --git a/cert-manager/Deployment/cert-manager-webhook.yaml b/cert-manager/Deployment/cert-manager-webhook.yaml index 3b8322d..71a6183 100644 --- a/cert-manager/Deployment/cert-manager-webhook.yaml +++ b/cert-manager/Deployment/cert-manager-webhook.yaml @@ -79,6 +79,7 @@ spec: capabilities: drop: - ALL + enableServiceLinks: false nodeSelector: kubernetes.io/os: linux securityContext: diff --git a/cert-manager/Deployment/cert-manager.yaml b/cert-manager/Deployment/cert-manager.yaml index 1167ae5..592fc82 100644 --- a/cert-manager/Deployment/cert-manager.yaml +++ b/cert-manager/Deployment/cert-manager.yaml @@ -38,6 +38,9 @@ spec: - '--v=2' - '--cluster-resource-namespace=$(POD_NAMESPACE)' - '--leader-election-namespace=kube-system' + - >- + --acme-http01-solver-image=quay.io/jetstack/cert-manager-acmesolver:v1.10.1 + - '--max-concurrent-challenges=60' env: - name: POD_NAMESPACE valueFrom: @@ -50,6 +53,9 @@ spec: - containerPort: 9402 name: http-metrics protocol: TCP + - containerPort: 9403 + name: http-healthz + protocol: TCP resources: requests: cpu: 10m @@ -59,6 +65,7 @@ spec: capabilities: drop: - ALL + enableServiceLinks: false nodeSelector: kubernetes.io/os: linux securityContext: diff --git a/hairpin-proxy/Deployment/hairpin-proxy-controller.yaml b/hairpin-proxy/Deployment/hairpin-proxy-controller.yaml index af95178..052768a 100644 --- a/hairpin-proxy/Deployment/hairpin-proxy-controller.yaml +++ b/hairpin-proxy/Deployment/hairpin-proxy-controller.yaml @@ -16,7 +16,12 @@ spec: app: hairpin-proxy-controller spec: containers: - - image: 'compumike/hairpin-proxy-controller:0.2.1' + - env: + - name: COREDNS_CONFIGMAP_NAME + value: coredns-custom + - name: COREDNS_IMPORT_CONFIG + value: 'true' + image: 'ghcr.io/jarvusinnovations/hairpin-proxy/controller:0.3.0' name: main resources: limits: diff --git a/hairpin-proxy/Deployment/hairpin-proxy-haproxy.yaml b/hairpin-proxy/Deployment/hairpin-proxy-haproxy.yaml index 2ee7315..b93af99 100644 --- a/hairpin-proxy/Deployment/hairpin-proxy-haproxy.yaml +++ b/hairpin-proxy/Deployment/hairpin-proxy-haproxy.yaml @@ -16,7 +16,7 @@ spec: app: hairpin-proxy-haproxy spec: containers: - - image: 'compumike/hairpin-proxy-haproxy:0.2.1' + - image: 'ghcr.io/jarvusinnovations/hairpin-proxy/haproxy:0.3.0' name: main resources: limits: diff --git a/kube-system/ConfigMap/coredns-custom.yaml b/kube-system/ConfigMap/coredns-custom.yaml new file mode 100644 index 0000000..e50b593 --- /dev/null +++ b/kube-system/ConfigMap/coredns-custom.yaml @@ -0,0 +1,7 @@ +apiVersion: v1 +data: + hairpinproxy.include: '' +kind: ConfigMap +metadata: + name: coredns-custom + namespace: kube-system diff --git a/kube-system/Role/hairpin-proxy-controller-r.yaml b/kube-system/Role/hairpin-proxy-controller-r.yaml index 1b3ba29..e0e52ad 100644 --- a/kube-system/Role/hairpin-proxy-controller-r.yaml +++ b/kube-system/Role/hairpin-proxy-controller-r.yaml @@ -8,6 +8,8 @@ rules: - '' resourceNames: - coredns + - coredns-base + - coredns-custom resources: - configmaps verbs: