Skip to content

OpenShift M3: Published into OperatorHub #2346

Open
@mflendrich

Description

@mflendrich

The big picture

Acceptance criteria for M3

  • Release process for Operator includes a step to publish (by merging an upstream PR) to OperatorHub.
  • A version of Operator successfully published using the method above.

Tasks

Preview Give feedback
No tasks being tracked yet.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/platform/openshiftkind/epicCategorizes issue as an epic.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions