You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// podNamespace checks whether the controller is running in a Pod vs.
@@ -159,6 +162,7 @@ func init() {
159
162
flags.StringVar(&cfg.cachePath, "cache-path", "/var/cache", "The local directory path used for filesystem based caching")
160
163
flags.StringVar(&cfg.systemNamespace, "system-namespace", "", "Configures the namespace that gets used to deploy system resources.")
161
164
flags.StringVar(&cfg.globalPullSecret, "global-pull-secret", "", "The <namespace>/<name> of the global pull secret that is going to be used to pull bundle images.")
165
+
flags.StringVar(&cfg.certificateProvider, "certificate-provider", certificateProviderCertManager, "The certificate provider to use for webhook support. Options: 'cert-manager' (default) or 'openshift-serviceca'.")
Copy file name to clipboardExpand all lines: docs/draft/howto/enable-webhook-support.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
## Installation of Bundles containing Webhooks
2
2
3
3
!!! note
4
-
Webhook support is enabled by default. The controller uses the `WebhookProviderCertManager`
5
-
feature-gate unless you override it. To switch to the OpenShift Service CA provider,
6
-
start the controller with `--feature-gates=WebhookProviderCertManager=false`.
4
+
Webhook support is enabled by default. The controller uses the `cert-manager`
5
+
certificate provider unless you override it. To switch to the OpenShift Service CA provider,
6
+
start the controller with `--certificate-provider=openshift-serviceca`.
7
7
8
8
OLMv1 supports the installation of bundles containing webhooks by default.
9
9
Webhooks, or more concretely Admission Webhooks, are part of Kuberntes' [Dynamic Admission Control](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/)
10
10
feature. Webhooks run as services called by the kube-apiservice in due course of processing a resource related request. They can be used to validate resources, ensure reasonable default values,
11
11
are set, or aid in the migration to new CustomResourceDefinition schema. The communication with the webhook service is secured by TLS. In OLMv1, the TLS certificate is managed by a
12
-
certificate provider. Currently, two certificate providers are supported: CertManager and Openshift-ServiceCA. The certificate provider to use given by the feature-gate:
12
+
certificate provider. Currently, two certificate providers are supported: CertManager and Openshift-ServiceCA. The controller selects the provider via the `--certificate-provider` flag:
13
13
14
-
-`WebhookProviderCertManager` for [CertManager](https://cert-manager.io/)
15
-
-`WebhookProviderOpenshiftServiceCA` for [Openshift-ServiceCA](https://github.com/openshift/service-ca-operator)
14
+
-`cert-manager` for [CertManager](https://cert-manager.io/) (default)
15
+
-`openshift-serviceca` for [Openshift-ServiceCA](https://github.com/openshift/service-ca-operator)
16
16
17
-
As CertManager is already installed with OLMv1, we suggest using `WebhookProviderCertManager`.
17
+
As CertManager is already installed with OLMv1, we suggest staying with the default `cert-manager` provider.
0 commit comments