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
<1> Specify the catalog's image in the `spec.source.image` field.
31
-
<2> Specify the interval for polling the remote registry for newer image digests. The default value is `24h`. Valid units include seconds (`s`), minutes (`m`), and hours (`h`). To disable polling, set a zero value, such as `0s`.
31
+
<1> The catalog is automatically labeled with the value of the `metadata.name` field when it is applied to the cluster. For more information about labels and catalog selection, see "Catalog content resolution".
32
+
<2> Optional: Specify the priority of the catalog in relation to the other catalogs on the cluster. For more information, see "Catalog selection by priority".
33
+
<3> Specify the interval in minutes for polling the remote registry for newer image digests. To disable polling, do not set the field.
34
+
<4> Specify the catalog image in the `spec.source.image.ref` field.
32
35
33
36
. Add the catalog to your cluster by running the following command:
Copy file name to clipboardExpand all lines: modules/olmv1-installing-an-operator.adoc
+67-50Lines changed: 67 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,28 +17,47 @@ You can install an extension from a catalog by creating a custom resource (CR) a
17
17
18
18
. Create a CR, similar to the following example:
19
19
+
20
+
[source,yaml]
21
+
----
22
+
apiVersion: olm.operatorframework.io/v1
23
+
kind: ClusterExtension
24
+
metadata:
25
+
name: <clusterextension_name>
26
+
spec:
27
+
namespace: <installed_namespace> <1>
28
+
serviceAccount:
29
+
name: <service_account_installer_name> <2>
30
+
source:
31
+
sourceType: Catalog
32
+
catalog:
33
+
packageName: <package_name>
34
+
channels:
35
+
- <channel_name> <3>
36
+
version: <version_or_version_range> <4>
37
+
----
38
+
<1> Specifies the namespace where you want the bundle installed, such as `pipelines` or `my-extension`. Extensions are still cluster-scoped and might contain resources that are installed in different namespaces.
39
+
<2> Specifies the name of the service account you created to install, update, and manage your extension.
40
+
<3> Optional: Specifies channel names as an array, such as `pipelines-1.14` or `latest`.
41
+
<4> Optional: Specifies the version or version range, such as `1.14.0`, `1.14.x`, or `>=1.16`, 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".
42
+
20
43
.Example `pipelines-operator.yaml` CR
21
44
[source,yaml]
22
45
----
23
-
apiVersion: olm.operatorframework.io/v1alpha1
46
+
apiVersion: olm.operatorframework.io/v1
24
47
kind: ClusterExtension
25
48
metadata:
26
49
name: pipelines-operator
27
50
spec:
28
-
packageName: openshift-pipelines-operator-rh
29
-
installNamespace: <namespace>
51
+
namespace: pipelines
30
52
serviceAccount:
31
-
name: <service_account>
32
-
channel: <channel>
33
-
version: "<version>"
53
+
name: pipelines-installer
54
+
source:
55
+
sourceType: Catalog
56
+
catalog:
57
+
packageName: openshift-pipelines-operator-rh
58
+
version: "1.14.x"
34
59
----
35
-
+
36
-
where:
37
-
+
38
-
`<namespace>`:: Specifies the namespace where you want the bundle installed, such as `pipelines` or `my-extension`. Extensions are still cluster-scoped and might contain resources that are installed in different namespaces.
39
-
`<service_account>`:: Specifies the name of the service account you created to install, update, and manage your extension.
40
-
`<channel>`:: Optional: Specifies the channel, such as `pipelines-1.11` or `latest`, for the package you want to install or update.
41
-
`<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".
60
+
42
61
43
62
. Apply the CR to the cluster by running the following command:
message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec"
96
-
observedGeneration: 1
97
-
reason: Success
98
-
status: "True"
99
-
type: Resolved
100
-
- lastTransitionTime: "2024-06-10T17:51:11Z"
101
-
message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec"
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.
157
176
`installedBundle.name`:: Displays the name of the bundle installed.
158
177
`installedBundle.version`:: Displays the version of the bundle installed.
159
-
`resolvedBundle.name`:: Displays the name of the resolved bundle.
160
-
`resolvedBundle.version`:: Displays the version of the resolved bundle.
0 commit comments