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
{olmv1-first} supports installing Operators and extensions scoped to the cluster. You can install an Operator or extension from a catalog by creating a custom resource (CR) and applying it to the cluster.
10
+
{olmv1-first} supports installing cluster extensions, including {olmv0} Operators via the `registry+v1` bundle format, that are scoped to the cluster. You can install an extension from a catalog by creating a custom resource (CR) and applying it to the cluster.
11
11
12
12
[IMPORTANT]
13
13
====
14
-
Currently, {olmv1} supports the installation Operators and extensions that meet the following criteria:
14
+
Currently, {olmv1} supports the installation of extensions that meet the following criteria:
15
15
16
-
* The Operator or extension must use the `AllNamespaces` install mode.
17
-
* The Operator or extension must not use webhooks.
16
+
* The extension must use the `AllNamespaces` install mode.
17
+
* The extension must not use webhooks.
18
18
19
-
Operators and extensions that use webhooks or that target a single or specified set of namespaces cannot be installed.
19
+
Cluster extensions that use webhooks or that target a single or specified set of namespaces cannot be installed.
. If you want to install your extension into a new namespace, run the following command:
109
+
+
110
+
[source,terminal]
111
+
----
112
+
$ oc adm new-project <new_namespace>
113
+
----
98
114
99
115
. Create a CR, similar to the following example:
100
116
+
@@ -107,14 +123,16 @@ metadata:
107
123
name: pipelines-operator
108
124
spec:
109
125
packageName: openshift-pipelines-operator-rh
126
+
installNamespace: <namespace>
110
127
channel: <channel>
111
128
version: "<version>"
112
129
----
113
130
+
114
131
where:
115
132
+
116
-
<channel>:: Optional: Specifies the channel, such as `pipelines-1.11` or `latest`, for the package you want to install or update.
117
-
<version>:: Optional: Specifies the version or version range, such as `1.11.1`, `1.12.x`, or `>=1.12.1`, of the package you want to install or update. For more information, see "Example custom resources (CRs) that specify a target version" and "Support for version ranges".
133
+
`<namespace>`:: Specifies the namespace where you want the bundle installed, such as `openshift-operators` or `my-extension`. Extensions are still cluster-scoped and might contain resources that are installed in different namespaces.
134
+
`<channel>`:: Optional: Specifies the channel, such as `pipelines-1.11` or `latest`, for the package you want to install or update.
135
+
`<version>`:: Optional: Specifies the version or version range, such as `1.11.1`, `1.12.x`, or `>=1.12.1`, of the package you want to install or update. For more information, see "Example custom resources (CRs) that specify a target version" and "Support for version ranges".
message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec"
190
+
observedGeneration: 1
191
+
reason: Success
192
+
status: "True"
193
+
type: Resolved
194
+
- lastTransitionTime: "2024-06-10T17:51:11Z"
195
+
message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec"
message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280"
174
-
observedGeneration: 1
175
-
reason: Success
176
-
status: "True"
177
-
type: Resolved
178
-
- lastTransitionTime: "2024-01-30T20:06:31Z"
179
-
message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280"
`spec.channel`:: Displays the channel defined in the CR of the extension.
237
+
`spec.version`:: Displays the version or version range defined in the CR of the extension.
238
+
`status.conditions`:: Displays information about the status and health of the extension.
239
+
`type: Deprecated`:: Displays whether one or more of following are deprecated:
240
+
+
241
+
--
242
+
`type: PackageDeprecated`:: Displays whether the resolved package is deprecated.
243
+
`type: ChannelDeprecated`:: Displays whether the resolved channel is deprecated.
244
+
`type: BundleDeprecated`:: Displays whether the resolved bundle is deprecated.
245
+
--
246
+
+
247
+
The value of `False` in the `status` field indicates that the `reason: Deprecated` condition is not deprecated. The value of `True` in the `status` field indicates that the `reason: Deprecated` condition is deprecated.
248
+
`installedBundle.name`:: Displays the name of the bundle installed.
249
+
`installedBundle.version`:: Displays the version of the bundle installed.
250
+
`resolvedBundle.name`:: Displays the name of the resolved bundle.
251
+
`resolvedBundle.version`:: Displays the verson of the resolved bundle.
187
252
====
188
253
189
254
. Get information about your bundle deployment by running the following command:
0 commit comments