weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
76eef68730
cert-manager/deploy/crds
History
Maël Valais 76eef68730 serviceAccountRef: the vault issuer can now use bound SA tokens 
Previously, the Vault issuer was only able to use a Secret in order to
use the "Kubernetes authentication" method. The downside to this service
account Secret token is that it has the default JWT iss
"kubernetes/serviceaccount" (along with the fact that the token is not
bound to a particular pod and has no expiry).

With the new serviceAccountRef, cert-manager now requests the token on
behalf of the pod in order to authenticate with Vault.

Signed-off-by: Maël Valais <mael@vls.dev>
2023-02-06 18:28:49 +01: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 Bump sigs.k8s.io deps 2022-12-21 09:47:41 -08:00
crd-clusterissuers.yaml serviceAccountRef: the vault issuer can now use bound SA tokens 2023-02-06 18:28:49 +01:00
crd-issuers.yaml serviceAccountRef: the vault issuer can now use bound SA tokens 2023-02-06 18:28:49 +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

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.