cert-manager/deploy/crds
ulrich giraud b9c9231305 vault issuer: specify that the caBundle must be base64-encoded
Signed-off-by: Ulrich GIRAUD <ulrich.giraud@pole-emploi.fr>
Signed-off-by: Maël Valais <mael@vls.dev>
2021-07-02 20:54:03 +02:00
..
BUILD.bazel Fix CRD targets 2020-12-01 16:43:16 +01:00
crd-certificaterequests.yaml controller-gen can now update CRDs like before 2021-05-11 17:29:06 +02:00
crd-certificates.yaml Merge pull request #4079 from annerajb/support-ed25519 2021-06-15 16:17:53 +01:00
crd-challenges.yaml Use controller-runtime v0.9.0-beta.0 2021-05-17 08:11:19 -07:00
crd-clusterissuers.yaml vault issuer: specify that the caBundle must be base64-encoded 2021-07-02 20:54:03 +02:00
crd-issuers.yaml vault issuer: specify that the caBundle must be base64-encoded 2021-07-02 20:54:03 +02:00
crd-orders.yaml controller-gen can now update CRDs like before 2021-05-11 17:29:06 +02:00
README.md Remove the legacy release 2020-12-01 16:17:07 +01:00

CRDs source directory

Warning

: if you are an end-user, you do NOT need to use the files in this directory. These files are for development purposes only.

This directory contains 'source code' used to build our CustomResourceDefinition resources in a way that can be consumed by all our different deployment methods.

This package exposes a number of different Bazel targets:

  • templates: the Helm templates for the CRD manifests
  • crds: the templated CRD manifests (after running helm template)
  • crd.templated: for each CRD type, the one CRD after running helm template
  • templated_files: a filegroup containing all of the individual templated CRD files

Most users should never utilise the files in this directory directly. Instead, Bazel build targets in other packages (i.e. //deploy/manifests, //deploy/charts etc) will be configured to automatically consume the appropriate artifact listed above.