Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7761

Operator-SDK keeps up with OpenShift k8s releases

XMLWordPrintable

    • 0% To Do, 0% In Progress, 100% Done

      Goal: Operator developers can always use the latest Kubernetes features that the latest OpenShift version is based on.

      Benefit hypothesis: Operator developers are getting value out of the SDK that helps them stay on the current, supported OpenShift version and migrate from one k8s releases to another.

      Why is this important: Operator developers to constantly get value out of using the Operator-SDK. On such value is to stay current with the Kubernetes API that the latest OpenShift version offers.

      Acceptance criteria:

      • always have an SDK versions that supports writing Operators against the Kubernetes API that the latest OpenShift release is based on
      • provide documentation on migrating from one k8s release to another

              Unassigned Unassigned
              DanielMesser Daniel Messer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: