History

Ashley Davis 32d716654a Add a makefile flow for building artifacts Includes targets for: - all "server" binaries, for all arches - all containers for all server binaries for all arches - all client binaries (kubectl plugin / cmctl) for all arches - the cert-manager helm chart + signature - the cert-manager static manifests + CRDs - tools which bazel would download, with checksum verification - (commented out) a signed SHA256SUM file for client binaries Upgrades from the bazel flow include that: - we use OS-specific base images rather than just using amd64 everywhere - we easily add support for signing artifacts at build time - we add ".exe" to the end of windows executables - we add a zip file for windows executables, for easier consumption - we concatenate YAML files more robustly - staging a full release should be much faster - hopefully, it's easier to change things! - licenses are trimmed down to reduce bloat in images (the license bundle was 1.4MB in size alone) Changes from the bazel flow include: - containers no longer have a symlink to the binary at an unusual path, but instead just have the binary at a more predictable path (e.g. /app/cmd/webhook/webhook instead of /app/cmd/webhook/webhook.runfiles/com_github_jetstack_cert_manager/cmd/webhook/webhook_/webhook) Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>		2021-12-15 09:54:15 +00:00
..
01-namespace.yaml	fix namespace yaml file format	2019-10-11 15:45:10 +02:00
BUILD.bazel	change startupapicheck to helm post-install hook	2021-07-30 16:04:55 +02:00
helm-values.yaml
namespace.yaml	Add a makefile flow for building artifacts	2021-12-15 09:54:15 +00:00
README.md	Remove the legacy release	2020-12-01 16:17:07 +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 Bazel.

To build the manifests, run:

$ bazel build //deploy/manifests:cert-manager.yaml

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