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

Operator-SDK becomes a supported offering

    XMLWordPrintable

Details

    • 100
    • 100% 100%

    Description

      Goal: ISVs get a supported version of the Operator-SDK with downstream branding and packaging.

      Benefit hypothesis: ISVs perceive the Operator-SDK as the supported and recommended way to build Operators for OpenShift.

      Why is this important: The Operator-SDK is currently a fast-moving upstream project. Getting the SDK SDK through officially supported Red Hat distribution mechanisms with explicit Red Hat branding and OpenShift compatibility increases trust and encourages following best practices among ISVs and other OpenShift-focussed SDK users.

      Acceptance criteria:

      • SDK reached version 1.0
      • SDK can receive support cases and official Bugzilla support tickets
      • SDK is available through Red Hat downstream distribution channels
      • SDK is available in the context of OpenShift downloads
      • all SDK dependencies (base images etc) are built using and available through downstream mechanisms
      • SDK denotes version compatibility with OpenShift

      Attachments

        Issue Links

          is blocked by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPPLAN-7760 Helm and Ansible Operator 1.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPPLAN-7776 Increase scorecard adoption

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPECO-1724 downstream: Sync SDK 1.7.2 downstream

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: