diff --git a/modules/olmv1-adding-a-catalog.adoc b/modules/olmv1-adding-a-catalog.adoc index f5f95c5360..f3feaa9de3 100644 --- a/modules/olmv1-adding-a-catalog.adoc +++ b/modules/olmv1-adding-a-catalog.adoc @@ -89,12 +89,12 @@ Annotations: API Version: catalogd.operatorframework.io/v1alpha1 Kind: Catalog Metadata: - Creation Timestamp: 2024-01-10T16:18:38Z + Creation Timestamp: 2024-06-10T17:34:53Z Finalizers: catalogd.operatorframework.io/delete-server-cache Generation: 1 - Resource Version: 57057 - UID: 128db204-49b3-45ee-bfea-a2e6fc8e34ea + Resource Version: 46075 + UID: 83c0db3c-a553-41da-b279-9b3cddaa117d Spec: Source: Image: @@ -103,7 +103,7 @@ Spec: Type: image Status: <1> Conditions: - Last Transition Time: 2024-01-10T16:18:55Z + Last Transition Time: 2024-06-10T17:35:15Z Message: Reason: UnpackSuccessful <2> Status: True @@ -113,9 +113,9 @@ Status: <1> Phase: Unpacked <3> Resolved Source: Image: - Last Poll Attempt: 2024-01-10T16:18:51Z + Last Poll Attempt: 2024-06-10T17:35:10Z Ref: registry.redhat.io/redhat/redhat-operator-index:v4.16 - Resolved Ref: registry.redhat.io/redhat/redhat-operator-index@sha256:7b536ae19b8e9f74bb521c4a61e5818e036ac1865a932f2157c6c9a766b2eea5 <4> + Resolved Ref: registry.redhat.io/redhat/redhat-operator-index@sha256:f2ccc079b5e490a50db532d1dc38fd659322594dcf3e653d650ead0e862029d9 <4> Type: image Events: ---- diff --git a/modules/olmv1-installing-an-operator.adoc b/modules/olmv1-installing-an-operator.adoc index 3c61ecf11b..13a30ef521 100644 --- a/modules/olmv1-installing-an-operator.adoc +++ b/modules/olmv1-installing-an-operator.adoc @@ -5,18 +5,18 @@ :_mod-docs-content-type: PROCEDURE [id="olmv1-installing-an-operator_{context}"] -= Installing an Operator from a catalog += Installing a cluster extension from a catalog -{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. +{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. [IMPORTANT] ==== -Currently, {olmv1} supports the installation Operators and extensions that meet the following criteria: +Currently, {olmv1} supports the installation of extensions that meet the following criteria: -* The Operator or extension must use the `AllNamespaces` install mode. -* The Operator or extension must not use webhooks. +* The extension must use the `AllNamespaces` install mode. +* The extension must not use webhooks. -Operators and extensions that use webhooks or that target a single or specified set of namespaces cannot be installed. +Cluster extensions that use webhooks or that target a single or specified set of namespaces cannot be installed. ==== .Prerequisite @@ -58,6 +58,7 @@ $ jq -s '.[] | select( .schema == "olm.channel" ) | \ "pipelines-1.11" "pipelines-1.12" "pipelines-1.13" +"pipelines-1.14" ---- ==== @@ -87,14 +88,29 @@ select( .schema == "olm.channel" ) | select( .name == "latest" ) | \ ==== [source,text] ---- -"openshift-pipelines-operator-rh.v1.11.1" "openshift-pipelines-operator-rh.v1.12.0" "openshift-pipelines-operator-rh.v1.12.1" "openshift-pipelines-operator-rh.v1.12.2" "openshift-pipelines-operator-rh.v1.13.0" "openshift-pipelines-operator-rh.v1.13.1" +"openshift-pipelines-operator-rh.v1.11.1" +"openshift-pipelines-operator-rh.v1.12.0" +"openshift-pipelines-operator-rh.v1.12.1" +"openshift-pipelines-operator-rh.v1.12.2" +"openshift-pipelines-operator-rh.v1.13.0" +"openshift-pipelines-operator-rh.v1.14.1" +"openshift-pipelines-operator-rh.v1.14.2" +"openshift-pipelines-operator-rh.v1.14.3" +"openshift-pipelines-operator-rh.v1.14.4" + ---- ==== +. If you want to install your extension into a new namespace, run the following command: ++ +[source,terminal] +---- +$ oc adm new-project +---- . Create a CR, similar to the following example: + @@ -107,14 +123,16 @@ metadata: name: pipelines-operator spec: packageName: openshift-pipelines-operator-rh + installNamespace: channel: version: "" ---- + where: + -:: Optional: Specifies the channel, such as `pipelines-1.11` or `latest`, for the package you want to install or update. -:: 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". +``:: 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. +``:: Optional: Specifies the channel, such as `pipelines-1.11` or `latest`, for the package you want to install or update. +``:: 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". + -- include::snippets/olmv1-multi-catalog-admon.adoc[] @@ -142,48 +160,95 @@ clusterextension.olm.operatorframework.io/pipelines-operator created $ oc get clusterextension pipelines-operator -o yaml ---- + --- -include::snippets/olmv1-version-range-cr-adomn.adoc[] --- -+ .Example output [%collapsible] ==== [source,text] ---- -apiVersion: olm.operatorframework.io/v1alpha1 -kind: ClusterExtension +apiVersion: v1 +items: +- apiVersion: olm.operatorframework.io/v1alpha1 + kind: ClusterExtension + metadata: + annotations: + kubectl.kubernetes.io/last-applied-configuration: | + {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","installNamespace":"openshift-operators","packageName":"openshift-pipelines-operator-rh","pollInterval":"30m"}} + creationTimestamp: "2024-06-10T17:50:51Z" + generation: 1 + name: pipelines-operator + resourceVersion: "53324" + uid: c54237be-cde4-46d4-9b31-d0ec6acc19bf + spec: + channel: latest + installNamespace: openshift-operators + packageName: openshift-pipelines-operator-rh + upgradeConstraintPolicy: Enforce + status: + conditions: + - lastTransitionTime: "2024-06-10T17:50:58Z" + message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec" + observedGeneration: 1 + reason: Success + status: "True" + type: Resolved + - lastTransitionTime: "2024-06-10T17:51:11Z" + message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec" + observedGeneration: 1 + reason: Success + status: "True" + type: Installed + - lastTransitionTime: "2024-06-10T17:50:58Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: Deprecated + - lastTransitionTime: "2024-06-10T17:50:58Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: PackageDeprecated + - lastTransitionTime: "2024-06-10T17:50:58Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: ChannelDeprecated + - lastTransitionTime: "2024-06-10T17:50:58Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: BundleDeprecated + installedBundle: + name: openshift-pipelines-operator-rh.v1.14.4 + version: 1.14.4 + resolvedBundle: + name: openshift-pipelines-operator-rh.v1.14.4 + version: 1.14.4 +kind: List metadata: - annotations: - kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","packageName":"openshift-pipelines-operator-rh","version":"1.11.x"}} - creationTimestamp: "2024-01-30T20:06:09Z" - generation: 1 - name: pipelines-operator - resourceVersion: "44362" - uid: 4272d228-22e1-419e-b9a7-986f982ee588 -spec: - channel: latest - packageName: openshift-pipelines-operator-rh - upgradeConstraintPolicy: Enforce - version: 1.11.x -status: - conditions: - - lastTransitionTime: "2024-01-30T20:06:15Z" - message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280" - observedGeneration: 1 - reason: Success - status: "True" - type: Resolved - - lastTransitionTime: "2024-01-30T20:06:31Z" - message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280" - observedGeneration: 1 - reason: Success - status: "True" - type: Installed - installedBundleResource: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280 - resolvedBundleResource: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280 + resourceVersion: "" ---- +where: + +`spec.channel`:: Displays the channel defined in the CR of the extension. +`spec.version`:: Displays the version or version range defined in the CR of the extension. +`status.conditions`:: Displays information about the status and health of the extension. +`type: Deprecated`:: Displays whether one or more of following are deprecated: ++ +-- +`type: PackageDeprecated`:: Displays whether the resolved package is deprecated. +`type: ChannelDeprecated`:: Displays whether the resolved channel is deprecated. +`type: BundleDeprecated`:: Displays whether the resolved bundle is deprecated. +-- ++ +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. +`installedBundle.name`:: Displays the name of the bundle installed. +`installedBundle.version`:: Displays the version of the bundle installed. +`resolvedBundle.name`:: Displays the name of the resolved bundle. +`resolvedBundle.version`:: Displays the verson of the resolved bundle. ==== . Get information about your bundle deployment by running the following command: @@ -198,11 +263,13 @@ $ oc get bundleDeployment pipelines-operator -o yaml ==== [source,text] ---- -apiVersion: core.rukpak.io/v1alpha1 +apiVersion: core.rukpak.io/v1alpha2 kind: BundleDeployment metadata: - creationTimestamp: "2024-01-30T20:06:15Z" - generation: 2 + creationTimestamp: "2024-06-10T17:50:58Z" + finalizers: + - core.rukpak.io/delete-cached-bundle + generation: 1 name: pipelines-operator ownerReferences: - apiVersion: olm.operatorframework.io/v1alpha1 @@ -210,39 +277,38 @@ metadata: controller: true kind: ClusterExtension name: pipelines-operator - uid: 4272d228-22e1-419e-b9a7-986f982ee588 - resourceVersion: "44464" - uid: 0a0c3525-27e2-4c93-bf57-55920a7707c0 + uid: c54237be-cde4-46d4-9b31-d0ec6acc19bf + resourceVersion: "53414" + uid: 74367cfc-578e-4da0-815f-fe40f3ca5d1c spec: - provisionerClassName: core-rukpak-io-plain - template: - metadata: {} - spec: - provisionerClassName: core-rukpak-io-registry - source: - image: - ref: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280 - type: image + installNamespace: openshift-operators + provisionerClassName: core-rukpak-io-registry + source: + image: + ref: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec + type: image status: - activeBundle: pipelines-operator-29x720cjzx8yiowf13a3j75fil2zs3mfw conditions: - - lastTransitionTime: "2024-01-30T20:06:15Z" - message: Successfully unpacked the pipelines-operator-29x720cjzx8yiowf13a3j75fil2zs3mfw - Bundle + - lastTransitionTime: "2024-06-10T17:51:09Z" + message: Successfully unpacked the image Bundle reason: UnpackSuccessful status: "True" - type: HasValidBundle - - lastTransitionTime: "2024-01-30T20:06:28Z" - message: Instantiated bundle pipelines-operator-29x720cjzx8yiowf13a3j75fil2zs3mfw - successfully + type: Unpacked + - lastTransitionTime: "2024-06-10T17:51:10Z" + message: Instantiated bundle pipelines-operator successfully reason: InstallationSucceeded status: "True" type: Installed - - lastTransitionTime: "2024-01-30T20:06:40Z" + - lastTransitionTime: "2024-06-10T17:51:19Z" message: BundleDeployment is healthy reason: Healthy status: "True" type: Healthy - observedGeneration: 2 + contentURL: https://core.openshift-rukpak.svc/bundles/pipelines-operator.tgz + observedGeneration: 1 + resolvedSource: + image: + ref: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec + type: image ---- ==== diff --git a/modules/olmv1-updating-an-operator.adoc b/modules/olmv1-updating-an-operator.adoc index 0ceecf27e7..7d9302e3ef 100644 --- a/modules/olmv1-updating-an-operator.adoc +++ b/modules/olmv1-updating-an-operator.adoc @@ -5,9 +5,9 @@ :_mod-docs-content-type: PROCEDURE [id="olmv1-updating-an-operator_{context}"] -= Updating an Operator += Updating a cluster extension -You can update your Operator or extension by manually editing the custom resource (CR) and applying the changes. +You can update your cluster extension or Operator by manually editing the custom resource (CR) and applying the changes. .Prerequisites @@ -49,6 +49,7 @@ $ jq -s '.[] | select( .schema == "olm.channel" ) | \ "pipelines-1.11" "pipelines-1.12" "pipelines-1.13" +"pipelines-1.14" ---- ==== @@ -83,7 +84,10 @@ select( .schema == "olm.channel" ) | select( .name == "latest" ) | \ "openshift-pipelines-operator-rh.v1.12.1" "openshift-pipelines-operator-rh.v1.12.2" "openshift-pipelines-operator-rh.v1.13.0" -"openshift-pipelines-operator-rh.v1.13.1" +"openshift-pipelines-operator-rh.v1.14.1" +"openshift-pipelines-operator-rh.v1.14.2" +"openshift-pipelines-operator-rh.v1.14.3" +"openshift-pipelines-operator-rh.v1.14.4" ---- ==== @@ -109,40 +113,65 @@ apiVersion: olm.operatorframework.io/v1alpha1 kind: ClusterExtension metadata: annotations: - kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","packageName":"openshift-pipelines-operator-rh","version":"1.11.1"}} - creationTimestamp: "2024-02-06T17:47:15Z" - generation: 2 + kubectl.kubernetes.io/last-applied-configuration: | + {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","installNamespace":"openshift-operators","packageName":"openshift-pipelines-operator-rh","pollInterval":"30m","version":"\u003c1.12"}} + creationTimestamp: "2024-06-11T15:55:37Z" + generation: 1 name: pipelines-operator - resourceVersion: "84528" - uid: dffe2c89-b9c4-427e-b694-ada0b37fc0a9 + resourceVersion: "69776" + uid: 6a11dff3-bfa3-42b8-9e5f-d8babbd6486f spec: - channel: latest <1> + channel: latest + installNamespace: openshift-operators packageName: openshift-pipelines-operator-rh upgradeConstraintPolicy: Enforce - version: 1.11.1 <2> + version: <1.12 status: conditions: - - lastTransitionTime: "2024-02-06T17:47:21Z" - message: bundledeployment status is unknown - observedGeneration: 2 - reason: InstallationStatusUnknown - status: Unknown + - lastTransitionTime: "2024-06-11T15:56:09Z" + message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280" + observedGeneration: 1 + reason: Success + status: "True" type: Installed - - lastTransitionTime: "2024-02-06T17:50:58Z" + - lastTransitionTime: "2024-06-11T15:55:50Z" message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280" - observedGeneration: 2 + observedGeneration: 1 reason: Success status: "True" type: Resolved - resolvedBundleResource: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:e09d37bb1e754db42324fd18c1cb3e7ce77e7b7fcbf4932d0535391579938280 + - lastTransitionTime: "2024-06-11T15:55:50Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: Deprecated + - lastTransitionTime: "2024-06-11T15:55:50Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: PackageDeprecated + - lastTransitionTime: "2024-06-11T15:55:50Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: ChannelDeprecated + - lastTransitionTime: "2024-06-11T15:55:50Z" + message: "" + observedGeneration: 1 + reason: Deprecated + status: "False" + type: BundleDeprecated + installedBundle: + name: openshift-pipelines-operator-rh.v1.11.1 + version: 1.11.1 + resolvedBundle: + name: openshift-pipelines-operator-rh.v1.11.1 + version: 1.11.1 ---- -<1> Specifies the channel for your Operator or extension. -<2> Specifies the version or version range for your Operator or extension. ==== -+ --- -include::snippets/olmv1-version-range-cr-adomn.adoc[] --- . Edit your CR by using one of the following methods: @@ -157,7 +186,8 @@ metadata: name: pipelines-operator spec: packageName: openshift-pipelines-operator-rh - version: 1.12.1 <1> + installNamespace: + version: "1.12.1" <1> ---- <1> Update the version from `1.11.1` to `1.12.1` @@ -172,6 +202,7 @@ metadata: name: pipelines-operator spec: packageName: openshift-pipelines-operator-rh + installNamespace: version: ">1.11.1, <1.13" <1> ---- <1> Specifies that the desired version range is greater than version `1.11.1` and less than `1.13`. For more information, see "Support for version ranges" and "Version comparison strings". @@ -187,6 +218,7 @@ metadata: name: pipelines-operator spec: packageName: openshift-pipelines-operator-rh + installNamespace: channel: pipelines-1.13 <1> ---- <1> Installs the latest release that can be resolved from the specified channel. Updates to the channel are automatically installed. @@ -202,6 +234,7 @@ metadata: name: pipelines-operator spec: packageName: openshift-pipelines-operator-rh + installNamespace: channel: latest version: "<1.13" ---- @@ -228,7 +261,7 @@ You can patch and apply the changes to your CR from the CLI by running the follo [source,terminal] ---- $ oc patch clusterextension/pipelines-operator -p \ - '{"spec":{"version":"1.12.1"}}' \ + '{"spec":{"version":"<1.13"}}' \ --type=merge ---- @@ -254,87 +287,138 @@ $ oc get clusterextension pipelines-operator -o yaml [source,yaml] ---- apiVersion: olm.operatorframework.io/v1alpha1 -kind: Operator +kind: ClusterExtension metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","packageName":"openshift-pipelines-operator-rh","version":"1.12.1"}} - creationTimestamp: "2024-02-06T19:16:12Z" - generation: 4 + {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","installNamespace":"openshift-operators","packageName":"openshift-pipelines-operator-rh","pollInterval":"30m","version":"\u003c1.13"}} + creationTimestamp: "2024-06-11T18:23:26Z" + generation: 2 name: pipelines-operator - resourceVersion: "58122" - uid: 886bbf73-604f-4484-9f87-af6ce0f86914 + resourceVersion: "66310" + uid: ce0416ba-13ea-4069-a6c8-e5efcbc47537 spec: channel: latest + installNamespace: openshift-operators packageName: openshift-pipelines-operator-rh upgradeConstraintPolicy: Enforce - version: 1.12.1 <1> + version: <1.13 status: conditions: - - lastTransitionTime: "2024-02-06T19:30:57Z" - message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:2f1b8ef0fd741d1d686489475423dabc07c55633a4dfebc45e1d533183179f6a" - observedGeneration: 3 - reason: Success - status: "True" - type: Installed - - lastTransitionTime: "2024-02-06T19:30:57Z" - message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:2f1b8ef0fd741d1d686489475423dabc07c55633a4dfebc45e1d533183179f6a" - observedGeneration: 3 + - lastTransitionTime: "2024-06-11T18:23:33Z" + message: resolved to "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:814742c8a7cc7e2662598e114c35c13993a7b423cfe92548124e43ea5d469f82" + observedGeneration: 2 reason: Success status: "True" type: Resolved - installedBundleResource: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:2f1b8ef0fd741d1d686489475423dabc07c55633a4dfebc45e1d533183179f6a - resolvedBundleResource: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:2f1b8ef0fd741d1d686489475423dabc07c55633a4dfebc45e1d533183179f6a + - lastTransitionTime: "2024-06-11T18:23:52Z" + message: installed from "registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:814742c8a7cc7e2662598e114c35c13993a7b423cfe92548124e43ea5d469f82" + observedGeneration: 2 + reason: Success + status: "True" + type: Installed + - lastTransitionTime: "2024-06-11T18:23:33Z" + message: "" + observedGeneration: 2 + reason: Deprecated + status: "False" + type: Deprecated + - lastTransitionTime: "2024-06-11T18:23:33Z" + message: "" + observedGeneration: 2 + reason: Deprecated + status: "False" + type: PackageDeprecated + - lastTransitionTime: "2024-06-11T18:23:33Z" + message: "" + observedGeneration: 2 + reason: Deprecated + status: "False" + type: ChannelDeprecated + - lastTransitionTime: "2024-06-11T18:23:33Z" + message: "" + observedGeneration: 2 + reason: Deprecated + status: "False" + type: BundleDeprecated + installedBundle: + name: openshift-pipelines-operator-rh.v1.12.2 + version: 1.12.2 + resolvedBundle: + name: openshift-pipelines-operator-rh.v1.12.2 + version: 1.12.2 ---- -<1> Verify that the version is updated to `1.12.1`. ==== .Troubleshooting -* If you specify a target version or channel that does not exist, you can run the following command to check the status of your Operator or extension: +* If you specify a target version or channel that is deprecated or does not exist, you can run the following command to check the status of your extension: + [source,terminal] ---- $ oc get clusterextension -o yaml ---- + -.Example output +.Example output for a version that does not exist [%collapsible] ==== [source,text] ---- -oc get clusterextension pipelines-operator -o yaml apiVersion: olm.operatorframework.io/v1alpha1 kind: ClusterExtension metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","packageName":"openshift-pipelines-operator-rh","version":"2.0.0"}} - creationTimestamp: "2024-02-06T17:47:15Z" - generation: 1 + {"apiVersion":"olm.operatorframework.io/v1alpha1","kind":"ClusterExtension","metadata":{"annotations":{},"name":"pipelines-operator"},"spec":{"channel":"latest","installNamespace":"openshift-operators","packageName":"openshift-pipelines-operator-rh","pollInterval":"30m","version":"3.0"}} + creationTimestamp: "2024-06-11T18:23:26Z" + generation: 3 name: pipelines-operator - resourceVersion: "82667" - uid: dffe2c89-b9c4-427e-b694-ada0b37fc0a9 + resourceVersion: "71852" + uid: ce0416ba-13ea-4069-a6c8-e5efcbc47537 spec: channel: latest + installNamespace: openshift-operators packageName: openshift-pipelines-operator-rh upgradeConstraintPolicy: Enforce - version: 2.0.0 + version: "3.0" status: conditions: - - lastTransitionTime: "2024-02-06T17:47:21Z" - message: installation has not been attempted due to failure to gather data for - resolution - observedGeneration: 1 - reason: InstallationStatusUnknown - status: Unknown - type: Installed - - lastTransitionTime: "2024-02-06T17:47:21Z" - message: no package "openshift-pipelines-operator-rh" matching version "2.0.0" - found in channel "latest" - observedGeneration: 1 + - lastTransitionTime: "2024-06-11T18:29:02Z" + message: 'error upgrading from currently installed version "1.12.2": no package + "openshift-pipelines-operator-rh" matching version "3.0" found in channel "latest"' + observedGeneration: 3 reason: ResolutionFailed status: "False" type: Resolved + - lastTransitionTime: "2024-06-11T18:29:02Z" + message: installation has not been attempted as resolution failed + observedGeneration: 3 + reason: InstallationStatusUnknown + status: Unknown + type: Installed + - lastTransitionTime: "2024-06-11T18:29:02Z" + message: deprecation checks have not been attempted as resolution failed + observedGeneration: 3 + reason: Deprecated + status: Unknown + type: Deprecated + - lastTransitionTime: "2024-06-11T18:29:02Z" + message: deprecation checks have not been attempted as resolution failed + observedGeneration: 3 + reason: Deprecated + status: Unknown + type: PackageDeprecated + - lastTransitionTime: "2024-06-11T18:29:02Z" + message: deprecation checks have not been attempted as resolution failed + observedGeneration: 3 + reason: Deprecated + status: Unknown + type: ChannelDeprecated + - lastTransitionTime: "2024-06-11T18:29:02Z" + message: deprecation checks have not been attempted as resolution failed + observedGeneration: 3 + reason: Deprecated + status: Unknown + type: BundleDeprecated ---- ==== diff --git a/operators/olm_v1/index.adoc b/operators/olm_v1/index.adoc index 5be47eade9..cc577992e8 100644 --- a/operators/olm_v1/index.adoc +++ b/operators/olm_v1/index.adoc @@ -36,7 +36,7 @@ Earlier Technology Preview phases of {olmv1} introduced a new `Operator` API; th For more information, see xref:../../operators/olm_v1/arch/olmv1-operator-controller.adoc#olmv1-operator-controller[Operator Controller] and xref:../../operators/olm_v1/arch/olmv1-catalogd.adoc#olmv1-catalogd[Catalogd]. Improved control over extension updates:: -With improved insight into catalog content, administrators can specify target versions for installation and updates. This grants administrators more control over the target version of extension updates. For more information, see xref:../../operators/olm_v1/olmv1-installing-an-operator-from-a-catalog.adoc#olmv1-updating-an-operator_olmv1-installing-operator[Updating an Operator]. +With improved insight into catalog content, administrators can specify target versions for installation and updates. This grants administrators more control over the target version of extension updates. For more information, see xref:../../operators/olm_v1/olmv1-installing-an-operator-from-a-catalog.adoc#olmv1-updating-an-operator_olmv1-installing-operator[Updating an cluster extension]. Flexible extension packaging format:: Administrators can use file-based catalogs to install and manage extensions, such as {olm}-based Operators, similar to the {olmv0} experience.