Skip to content

Commit a9f89c0

Browse files
committed
Update bundle-upgrade to allow tradtl OLM install
1 parent e48b021 commit a9f89c0

File tree

3 files changed

+13
-3
lines changed

3 files changed

+13
-3
lines changed

modules/olm-installing-operators-from-operatorhub.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ifeval::["{context}" == "olm-installing-operators-in-namespace"]
1212
endif::[]
1313

1414
[id="olm-installing-operators-from-operatorhub_{context}"]
15-
= Operator installation with OperatorHub
15+
= About Operator installation with OperatorHub
1616

1717
OperatorHub is a user interface for discovering Operators; it works in conjunction with Operator Lifecycle Manager (OLM), which installs and manages Operators on a cluster.
1818

modules/osdk-bundle-upgrade-olm.adoc

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,19 @@ The `run bundle-upgrade` subcommand automates triggering an installed Operator t
1111

1212
.Prerequisites
1313

14-
- Operator installed with OLM by using the `run bundle` subcommand
14+
- Operator installed with OLM either by using the `run bundle` subcommand or with traditional OLM installation
1515
- A bundle image that represents a later version of the installed Operator
1616

1717
.Procedure
1818

19-
. If your Operator has not already been installed on OLM with the `run bundle` subcommand, install the earlier version of your Operator by specifying the bundle image. For example, for a Memcached Operator:
19+
. If your Operator has not already been installed with OLM, install the earlier version either by using the `run bundle` subcommand or with traditional OLM installation.
20+
+
21+
[NOTE]
22+
====
23+
If the earlier version of the bundle was installed traditionally using OLM, the newer bundle that you intend to upgrade to must not exist in the index image referenced by the catalog source. Otherwise, running the `run bundle-upgrade` subcommand will cause the registry pod to fail because the newer bundle is already referenced by the index that provides the package and cluster service version (CSV).
24+
====
25+
+
26+
For example, you can use the following `run bundle` subcommand for a Memcached Operator by specifying the earlier bundle image:
2027
+
2128
[source,terminal]
2229
----

operators/operator_sdk/osdk-working-bundle-images.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ You can use the Operator SDK to package, deploy, and upgrade Operators in the bu
99

1010
include::modules/osdk-bundle-deploy-olm.adoc[leveloffset=+1]
1111
include::modules/osdk-bundle-upgrade-olm.adoc[leveloffset=+1]
12+
.Additional resources
13+
14+
* xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-adding-operators-to-a-cluster[Traditional Operator installation with OLM]
1215

1316
[id="osdk-working-bundle-images-additional-resources"]
1417
== Additional resources

0 commit comments

Comments
 (0)