History

Joshua Mathianas e33e28c4fd add backwards compatability for using existing common name or organization if x509name ones are not set add ability to specify more subject attributes for csr Signed-off-by: Joshua Mathianas <mathianasj@gmail.com>		2020-01-16 07:50:26 -05:00
..
00-crds.yaml	add backwards compatability for using existing common name or organization if x509name ones are not set	2020-01-16 07:50:26 -05:00
01-namespace.yaml	fix namespace yaml file format	2019-10-11 15:45:10 +02:00
BUILD.bazel	Use schemapatch to generate openapi schemas	2019-10-25 14:44:02 +01:00
helm-values.yaml	Remove deploy-gen scripts	2019-05-03 11:16:25 +01:00
README.md	Update README text in manifests directory	2019-05-03 12:19:24 +01:00

README.md

Deployment files

This directory previously contained the Kubernetes manifests needed to deploy cert-manager.

For full information on deploying cert-manager, see the getting started guide.

Where are the manifests now?

From v0.8 onwards, the 'static deployment manifests' are generated automatically from the official helm chart.

When a new release of cert-manager is cut, these manifests will be automatically generated and published as an asset attached to the GitHub release.

How can I generate my own manifests?

If you want to build a copy of your own manifests for testing purposes, you can do so using the 'release' tool in this repository.

To build the manifests, run:

$ bazel run //hack/release -- \
    --manifests \
    --app-version={image tag} \
    --docker-repo=quay.io/myuser

This will generate static deployment manifests that are configured to use the specified image repository and tag, making it easy for you to test and distribute sample manifests.