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
Copy file name to clipboardExpand all lines: docs/api-reference/olmv1-api-reference.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -254,7 +254,7 @@ _Appears in:_
254
254
| Field | Description | Default | Validation |
255
255
| --- | --- | --- | --- |
256
256
|`configType`_[ClusterExtensionConfigType](#clusterextensionconfigtype)_| configType is a required reference to the type of configuration source.<br /><br />Allowed values are "Inline"<br /><br />When this field is set to "Inline", the cluster extension configuration is defined inline within the<br />ClusterExtension resource. || Enum: [Inline] <br />Required: \{\} <br /> |
257
-
|`inline`_[JSON](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#json-v1-apiextensions-k8s-io)_| inline contains JSON or YAML values specified directly in the<br />ClusterExtension.<br /><br />inline must be set if configType is 'Inline'. || Type: object <br /> |
257
+
|`inline`_[JSON](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#json-v1-apiextensions-k8s-io)_| inline contains JSON or YAML values specified directly in the<br />ClusterExtension.<br /><br />inline must be set if configType is 'Inline'.<br />inline accepts arbitrary JSON/YAML objects.<br />inline is validation at runtime against the schema provided by the bundle if a schema is provided.|| Type: object <br /> |
258
258
259
259
260
260
#### ClusterExtensionConfigType
@@ -343,7 +343,7 @@ _Appears in:_
343
343
|`serviceAccount`_[ServiceAccountReference](#serviceaccountreference)_| serviceAccount is a reference to a ServiceAccount used to perform all interactions<br />with the cluster that are required to manage the extension.<br />The ServiceAccount must be configured with the necessary permissions to perform these interactions.<br />The ServiceAccount must exist in the namespace referenced in the spec.<br />serviceAccount is required. || Required: \{\} <br /> |
344
344
|`source`_[SourceConfig](#sourceconfig)_| source is a required field which selects the installation source of content<br />for this ClusterExtension. Selection is performed by setting the sourceType.<br /><br />Catalog is currently the only implemented sourceType, and setting the<br />sourcetype to "Catalog" requires the catalog field to also be defined.<br /><br />Below is a minimal example of a source definition (in yaml):<br /><br />source:<br /> sourceType: Catalog<br /> catalog:<br /> packageName: example-package || Required: \{\} <br /> |
345
345
|`install`_[ClusterExtensionInstallConfig](#clusterextensioninstallconfig)_| install is an optional field used to configure the installation options<br />for the ClusterExtension such as the pre-flight check configuration. |||
346
-
|`config`_[ClusterExtensionConfig](#clusterextensionconfig)_| config contains optional configuration values applied during rendering of the<br />ClusterExtension's manifests. Values can be specified inline.<br /><br />config is optional. When not specified, the default configuration of the resolved bundle will be used.<br /><br /><opcon:experimental>|||
346
+
|`config`_[ClusterExtensionConfig](#clusterextensionconfig)_| config is an optional field used to specify bundle specific configuration<br />used to configure the bundle. Configuration is bundle specific and a bundle may provide<br />a configuration schema. When not specified, the default configuration of the resolved bundle will be used.<br /><br />config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide<br />a configuration schema the final manifests will be derived on a best-effort basis. More information on how<br />to configure the bundle should be found in its end-user documentation.<br /><br /><opcon:experimental>|||
Copy file name to clipboardExpand all lines: docs/draft/howto/enable-webhook-support.md
+7-10Lines changed: 7 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,11 @@
1
1
## Installation of Bundles containing Webhooks
2
2
3
3
!!! note
4
-
This feature is still in *alpha*. Either the `WebhookProviderCertManager`, or the `WebhookProviderOpenshiftServiceCA`, feature-gate
5
-
must be enabled to make use of it. See the instructions below on how to enable the feature-gate.
4
+
OLMv1 supports the installation of bundles containing webhooks by default.
5
+
By default, OLM v1 uses the community Cert Manager package for admission webhook via the feature-gate flag `WebhookProviderCertManager`. To use the OpenShift Service CA provider, set the `--feature-gates=WebhookProviderOpenshiftServiceCA=true` flag at startup.
6
6
7
-
OLMv1 currently does not support the installation of bundles containing webhooks. The webhook support feature enables this capability.
8
-
Webhooks, or more concretely Admission Webhooks, are part of Kuberntes' [Dynamic Admission Control](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/)
9
-
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,
7
+
Admission webhooks are part of the Kubernetes suite of [Dynamic Admission Control](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/)
8
+
plugins. 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,
10
9
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
11
10
certificate provider. Currently, two certificate providers are supported: CertManager and Openshift-ServiceCA. The certificate provider to use given by the feature-gate:
12
11
@@ -15,14 +14,12 @@ certificate provider. Currently, two certificate providers are supported: CertMa
15
14
16
15
As CertManager is already installed with OLMv1, we suggest using `WebhookProviderCertManager`.
17
16
18
-
### Run OLM v1with Experimental Features Enabled
17
+
### Run OLM v1 with Webhook Support
19
18
20
-
```terminal title=Enable Experimental Features in a New Kind Cluster
21
-
make run-experimental
19
+
```terminal title=Start the controller with webhook support
20
+
make run
22
21
```
23
22
24
-
This will enable only the `WebhookProviderCertManager` feature-gate, which works with cert-manager.
Copy file name to clipboardExpand all lines: docs/draft/tutorials/explore-available-content-metas-endpoint.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ Then you can query the catalog by using `curl` commands and the `jq` CLI tool to
92
92
```
93
93
94
94
!!! important
95
-
Currently, OLM 1.0 does not support the installation of extensions that use webhooks or that target a single or specified set of namespaces.
95
+
OLM 1.0 supports installing extensions that define webhooks. Targeting a single or specified set of namespaces requires enabling the `SingleOwnNamespaceInstallSupport` feature-gate.
96
96
97
97
3. Return list of packages which support `AllNamespaces` install mode, do not use webhooks, and where the channel head version uses `olm.csv.metadata` format:
Copy file name to clipboardExpand all lines: docs/tutorials/explore-available-content.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ Then you can query the catalog by using `curl` commands and the `jq` CLI tool to
92
92
```
93
93
94
94
!!! important
95
-
Currently, OLM 1.0 does not support the installation of extensions that use webhooks or that target a single or specified set of namespaces.
95
+
OLM 1.0 supports installing extensions that define webhooks. Targeting a single or specified set of namespaces requires enabling the `SingleOwnNamespaceInstallSupport` feature-gate.
96
96
97
97
3. Return list of packages that support `AllNamespaces` install mode and do not use webhooks:
![openshift-merge-bot[bot]](https://avatars.githubusercontent.com/in/412865?v=4&size=40){kind=avatar}
0 commit comments