Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-3371

OSC 1.8.0: Check if we need to bump the operator-sdk

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • OSC 1.8.0
    • None
    • None
    • None
    • Kata Sprint #259
    • 0
    • 0.000

      operator-sdk version, of our openshift/sandboxed-containers-operator repository, should match the kubernetes version for the latest OCP we will support.

      To find the match, Ctrl+F the desired Kubernetes version on the operator-sdk release page. If there are no breaking changes mentioned in the release notes, you can just use the latest version.

      Update operator-sdk version in docs/DEVELOPMENT.md

      Follow upgrade docs operator-sdk upgrades: Upgrade SDK Version. If the release notes mention breaking changes, this may be not straightforward.

      Example: the move to Golang v4 plugin in v1.33.0, needed for Kubernetes 1.28 / Openshift 4.16.

      Check go deps of upstream operator-sdk (go.mod):

      • “go get github.com/operator-framework/operator-sdk@v…”
      • “go get github.com/operator-framework/operator-sdk@none”
      • remove operator-sdk lines from go.sum
      • “go mod tidy”
      • Resolve dep issue after go mod tidy
      • Build and address build failures caused by updated dependencies

      Full Steps documentation:

      Operator SDK Migration

      *NOTE:* This issue came from a template. If you find any problems with it, please contact the admins so we can update the template accordingly for the next release.

            bpradipt Pradipta Banerjee
            beraldoleal Beraldo Leal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: