This is a cache of https://docs.okd.io/4.13/operators/operator_sdk/helm/osdk-helm-updating-projects.html. It is a snapshot of the page at 2024-11-24T00:27:57.797+0000.
Updating <strong>helm</strong>-based projects - Developing Operators | Operators | OKD 4.13
  1. Documentation
×

Updating helm-based projects for newer Operator SDK versions

OKD 4.13 supports Operator SDK 1.28.0. If you already have the 1.25.4 CLI installed on your workstation, you can update the CLI to 1.28.0 by installing the latest version.

However, to ensure your existing Operator projects maintain compatibility with Operator SDK 1.28.0, update steps are required for the associated breaking changes introduced since 1.25.4. You must perform the update steps manually in any of your Operator projects that were previously created or maintained with 1.25.4.

Updating helm-based Operator projects for Operator SDK 1.28.0

The following procedure updates an existing helm-based Operator project for compatibility with 1.28.0.

Prerequisites

  • Operator SDK 1.28.0 installed

  • An Operator project created or maintained with Operator SDK 1.25.4

Procedure

  1. Update the image tag in your Operator’s Dockerfile as shown in the following example:

    Example Dockerfile
    FROM registry.redhat.io/openshift4/ose-helm-operator:v4.13 (1)
    1 Update the version tag to v4.13.

  2. Find the ose-kube-rbac-proxy pull spec in the following files, and update the image tag to v4.13:

    • config/default/manager_auth_proxy_patch.yaml

    • bundle/manifests/memcached-operator.clusterserviceversion.yaml

    …
      containers:
      - name: kube-rbac-proxy
        image: registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.13 (1)
…
    1 Update the tag version from v4.12 to v4.13.

Additional resources