Goal: Operator-SDK users have OLM support / integration by default that enables a seamless development and test experience.

Benefit hypothesis: More Operator developer choose to package and publish their Operator for management by OLM and contribution to community OperatorHub(.io).

Why is this important: OLM enables robust release management and lifecycle of Operator which is important to generate an ISV ecosystem in particular and the success of the Operator Framework in general. Enablement starts at the development stage and continues with packaging and releasing Operators. For authors the Operator-SDK needs to provide a first-class entry point into this that people get by default instead of opt-in so it is not an afterthought.

Acceptance criteria:

• SDK supports currently supported OLM packaging formats
• SDK generates OLM packaging by default
• SDK uses sane defaults to generate metadata
• SDK enables subsequent releasing / publishing of Operators for OLM
• SDK enables quick feedback loops when testing Operator deployment through OLM