cert-manager/deploy/manifests
Josh Soref 8d801fc100 spelling: certificate
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
2020-02-24 16:15:51 -05:00
..
00-crds.yaml spelling: certificate 2020-02-24 16:15:51 -05:00
01-namespace.yaml fix namespace yaml file format 2019-10-11 15:45:10 +02:00
BUILD.bazel Write CRD filter for OpenShift 2020-02-18 10:52:42 +01:00
helm-values.yaml
README.md Add release-tars targets to construct cert-manager release artifacts 2020-01-30 21:02:58 +00:00

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 Bazel.

To build the manifests, run:

$ bazel build //deploy/manifests:cert-manager
# Alternatively, build the openshift variant with:
$ bazel build //deploy/manifests:cert-manager-openshift
# Or the no-webhook variant with:
$ bazel build //deploy/manifests:cert-manager-no-webhook

This will generate the static deployment manifests at bazel-bin/deploy/manifests/cert-manager.yaml.