This removes all .bazel and .bzl files, and a bunch of scripts relating to bazel, now that it's been entirely replaced. There are still a few places where traces could be removed, but this removes the brunt of the bazel stuff that remains. Signed-off-by: Ashley Davis <ashley.davis@jetstack.io> |
||
|---|---|---|
| .. | ||
| 01-namespace.yaml | ||
| helm-values.yaml | ||
| namespace.yaml | ||
| 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.