Skip to content

[enterprise-4.14] OCPBUGS#22716: Fix OPERATOR_SDK_VERSION migration step #83422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2024
Merged

[enterprise-4.14] OCPBUGS#22716: Fix OPERATOR_SDK_VERSION migration step #83422

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 9 additions & 12 deletions modules/osdk-updating-128-to-131.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,16 +41,15 @@ The following procedure updates an existing {type}-based Operator project for co
.Procedure

ifdef::golang,hybrid,java[]
* Edit your Operator project's makefile to update the Operator SDK version to {osdk_ver}, as shown in the following example:
* Edit your Operator project's Makefile to add the `OPERATOR_SDK_VERSION` field and set it to `v{osdk_ver}-ocp`, as shown in the following example:
+
.Example makefile
.Example Makefile
[source,make,subs="attributes+"]
----
# Set the Operator SDK version to use. By default, what is installed on the system is used.
# This is useful for CI or a project to utilize a specific version of the operator-sdk toolkit.
OPERATOR_SDK_VERSION ?= v{osdk_ver} <1>
OPERATOR_SDK_VERSION ?= v{osdk_ver}-ocp
----
<1> Change the version from `{osdk_ver_n1}` to `{osdk_ver}`.
endif::[]

ifdef::helm[]
Expand All @@ -63,16 +62,15 @@ FROM quay.io/operator-framework/helm-operator:v{osdk_ver} <1>
----
<1> Update the Helm Operator version from `{osdk_ver_n1}` to `{osdk_ver}`

. Edit your Operator project's makefile to update the Operator SDK to {osdk_ver}, as shown in the following example:
. Edit your Operator project's Makefile to add the `OPERATOR_SDK_VERSION` field and set it to `v{osdk_ver}-ocp`, as shown in the following example:
+
.Example makefile
.Example Makefile
[source,make,subs="attributes+"]
----
# Set the Operator SDK version to use. By default, what is installed on the system is used.
# This is useful for CI or a project to utilize a specific version of the operator-sdk toolkit.
OPERATOR_SDK_VERSION ?= v{osdk_ver} <1>
OPERATOR_SDK_VERSION ?= v{osdk_ver}-ocp
----
<1> Change the version from `{osdk_ver_n1}` to `{osdk_ver}`.

. If you use a custom service account for deployment, define the following role to require a watch operation on your secrets resource, as shown in the following example:
+
Expand Down Expand Up @@ -126,16 +124,15 @@ FROM quay.io/operator-framework/ansible-operator:v{osdk_ver}
+
If your Operator depends on one of these removed Python modules, update your Dockerfile to install the required modules using the `pip install` command.

. Edit your Operator project's makefile to update the Operator SDK version to {osdk_ver}, as shown in the following example:
. Edit your Operator project's Makefile to add the `OPERATOR_SDK_VERSION` field and set it to `v{osdk_ver}-ocp`, as shown in the following example:
+
.Example makefile
.Example Makefile
[source,make,subs="attributes+"]
----
# Set the Operator SDK version to use. By default, what is installed on the system is used.
# This is useful for CI or a project to utilize a specific version of the operator-sdk toolkit.
OPERATOR_SDK_VERSION ?= v{osdk_ver} <1>
OPERATOR_SDK_VERSION ?= v{osdk_ver}-ocp
----
<1> Change the version from `{osdk_ver_n1}` to `{osdk_ver}`.

. Update your `requirements.yaml` and `requirements.go` files to remove the `community.kubernetes` collection and update the `operator_sdk.util` collection to version `0.5.0`, as shown in the following example:
+
Expand Down