cert-manager/deploy/crds
Ashley Davis eccde015ac
add CRD generation to makefile, replacing bazel
- includes a run of make update-crds which causes some trivial changes
- updates version of YQ to latest
- makes hack/update-crds.sh just call make
- makes hack/verify-crds.sh just call make
- moves functionality of hack/verify-crds.sh to hack/check-crds.sh,
  using the makefile for generating alternative CRDs for comparison
- removes the bazel test associated with CRDs

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
2022-06-27 13:25:18 +01:00
..
BUILD.bazel change startupapicheck to helm post-install hook 2021-07-30 16:04:55 +02:00
crd-certificaterequests.yaml add CRD generation to makefile, replacing bazel 2022-06-27 13:25:18 +01:00
crd-certificates.yaml add CRD generation to makefile, replacing bazel 2022-06-27 13:25:18 +01:00
crd-challenges.yaml Change label description for HTTP-01 Gateway API solver and fix tests 2022-03-30 12:52:34 +01:00
crd-clusterissuers.yaml Change label description for HTTP-01 Gateway API solver and fix tests 2022-03-30 12:52:34 +01:00
crd-issuers.yaml Remove leftover cainjector annotations from our CRDs 2022-05-09 17:24:30 +01:00
crd-orders.yaml Remove leftover cainjector annotations from our CRDs 2022-05-09 17:24:30 +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.