weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
ffcd374e14
cert-manager/deploy/crds
History
Ashley Davis c5924f54a1
add + use CABundle field for ACME servers in issuers 
Previously it wasn't possible to set a custom CA bundle for an ACME
server, leading users to either patch the cert-manager system CA bundle
manually or else use SkipTLSVerify which is a security issue.

This adds CABundle for ACME, similar to what we have for Vault and
Venafi TPP issuers.

Longer term we'd like to have a more fully featured approach. It would
for example make sense to support loading CA bundles from ConfigMaps or
Secrets (similar to what we do for Vault issuers today), but for now this
change is the simplest change.

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
2022-12-15 16:21:07 +00:00
..
crd-certificaterequests.yaml apply go fmt for go1.19 2022-08-04 09:51:57 +00:00
crd-certificates.yaml Updating CRDs 2022-12-06 18:54:46 +05:30
crd-challenges.yaml Update reference to HTTPRoute docs 2022-12-05 15:04:18 +00:00
crd-clusterissuers.yaml add + use CABundle field for ACME servers in issuers 2022-12-15 16:21:07 +00:00
crd-issuers.yaml add + use CABundle field for ACME servers in issuers 2022-12-15 16:21:07 +00: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

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.