weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
a4aea9e30f
cert-manager/deploy/crds
History
Bill Waldrep d4911ebfaa
Add optional flag to specify jks keystore alias. 
Previously the JKS keystore alias was hardcoded to "certificate".
This change adds an optional configuration point to allow users
to specify a custom keystore alias. If the flag is omitted we
will default to the previous behavior.

Signed-off-by: Bill Waldrep <bwaldrep@palantir.com>
2024-03-04 13:23:09 -05:00
..
crd-certificaterequests.yaml run 'make update-crds' 2024-02-22 13:26:29 +01:00
crd-certificates.yaml Add optional flag to specify jks keystore alias. 2024-03-04 13:23:09 -05:00
crd-challenges.yaml run 'make update-crds' 2024-02-22 13:26:29 +01:00
crd-clusterissuers.yaml run 'make update-crds' 2024-02-22 13:26:29 +01:00
crd-issuers.yaml run 'make update-crds' 2024-02-22 13:26:29 +01:00
crd-orders.yaml run 'make update-crds' 2024-02-22 13:26:29 +01:00
README.md Remove the legacy release 2020-12-01 16:17:07 +01:00

README.md

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.