Skip to content

Commit

Permalink
Add note about installCRDs to release notes
Browse files Browse the repository at this point in the history
Signed-off-by: James Munnelly <james@munnelly.eu>
  • Loading branch information
munnerz committed May 6, 2020
1 parent 2c8a677 commit abe6a3c
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions content/en/docs/release-notes/release-notes-0.15.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ type: "docs"
The `v0.15` release has a few focus areas:

* Experimental new Certificate controller design
* New `installCRDs` option in the Helm chart
* Support for Red Hat's [Operator Lifecycle Manager](https://github.com/operator-framework/operator-lifecycle-manager) for easier deployment in OpenShift environments
* Improved deployment process for webhook component
* General Availability of JKS and PKCS#12 keystore support
Expand Down Expand Up @@ -55,6 +56,18 @@ and edit the `args` to include `--feature-gates=ExperimentalCertificateControlle
- --feature-gates=ExperimentalCertificateControllers=true
```

## Helm chart `installCRDs` option

It's been a long-standing feature request to bundle our CRD resources as part
of our Helm chart, to make it easier for users installing with Helm to manage
the lifecycle of the CRDs we create.

To facilitate this, and to help resolve common deployment issues, we have added
a new `installCRDs` option to the Helm chart which will mean the CRD resources
will be managed by your regular Helm installation.

This feature is **disabled** by default, and can be enabled either in your
`values.yaml` file or as a flag with `helm install --set installCRDs=true`.

## Support for OpenShift's Operator Lifecycle Manager

Expand Down

0 comments on commit abe6a3c

Please sign in to comment.