cert-manager/deploy/crds
Jonathan Prates 9f36f8984b feat: copy SecretTemplate api to v1alpha2 v1alpha3 and v1beta1
Signed-off-by: jonathansp <jonathansimonprates@gmail.com>
2021-08-03 01:19:11 +01:00
..
BUILD.bazel add comments 2021-07-13 17:58:28 +02:00
crd-certificaterequests.yaml Adds note as to why v1beta1 is still an accepted 2021-07-28 15:49:50 +01:00
crd-certificates.yaml feat: copy SecretTemplate api to v1alpha2 v1alpha3 and v1beta1 2021-08-03 01:19:11 +01:00
crd-challenges.yaml Adds note as to why v1beta1 is still an accepted 2021-07-28 15:49:50 +01:00
crd-clusterissuers.yaml Adds note as to why v1beta1 is still an accepted 2021-07-28 15:49:50 +01:00
crd-issuers.yaml Adds note as to why v1beta1 is still an accepted 2021-07-28 15:49:50 +01:00
crd-orders.yaml Adds note as to why v1beta1 is still an accepted 2021-07-28 15:49:50 +01: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.