Document how to configure cert-manager via OLM #983
Conversation
Signed-off-by: Richard Wall <richard.wall@jetstack.io>
|
Skipping CI for Draft Pull Request. |
jetstack-bot
added
do-not-merge/work-in-progress
✅ Deploy Preview for cert-manager-website ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: Richard Wall <richard.wall@jetstack.io>
Signed-off-by: Richard Wall <richard.wall@jetstack.io>
…urce Signed-off-by: Richard Wall <richard.wall@jetstack.io>
jetstack-bot
added
size/L
Signed-off-by: Richard Wall <richard.wall@jetstack.io>
wallrj
changed the title
jetstack-bot
removed
the
do-not-merge/work-in-progress
Signed-off-by: Richard Wall <richard.wall@jetstack.io>
| > 🔰 Refer to the [Subscription API documentation](https://pkg.go.dev/github.com/operator-framework/api@v0.14.0/pkg/operators/v1alpha1#Subscription). | ||
|
|
||
| Here are some examples of configuration that can be achieved by modifying the Subscription resource. | ||
| In each case we assume that you are starting with the following [default Subscription from OperatorHub.io]((https://operatorhub.io/install/cert-manager.yaml)): |
There was a problem hiding this comment.
| In each case we assume that you are starting with the following [default Subscription from OperatorHub.io]((https://operatorhub.io/install/cert-manager.yaml)): | |
| In each case we assume that you are starting with the following [default Subscription from OperatorHub.io](https://operatorhub.io/install/cert-manager.yaml): |
| @@ -91,9 +91,146 @@ in accordance with [OLM's Recommended Channel Naming][]. | |||
| If you have any issues with your installation, please refer to the | |||
| [FAQ](../faq/README.md). | |||
|
|
|||
| ## Configuration | |||
|
|
|||
| The configuration options are quite limited when you install cert-manager using OLM. | |||
There was a problem hiding this comment.
Just out of curiosity: are the options limited because of limitations with OLM or is it limitation we have imposed?
There was a problem hiding this comment.
The current version of OLM has limited support for modifying the deployment, as documented in this PR.
For example, it does not provide an easy way for the OLM package author to allow the container command line flags to be overridden.
But on the other hand, if all the cert-manager components could be configured using a config file in a configmap and if all the existing command line options could also be declared inthose config files, that particular problem would be solved.
There are some other limitations such as not being able to customize the resource requests of individual Deployments in the OLM package:
The current API seems to be designed around there only being a single Deployment in each package, but cert-manager has three.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jahrlin, wallrj The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I've tried to document the OLM configuration options that are available today and mention some of the limitations.
Part of: