Goals

Enable and provide a set of validation checks and scorecard tests to ensure Operator bundle quality and warrant functional correctness.

Why is this important?

Validations and testing are essential before publishing Operator releases.
Operator SDK wants to:

• provides a validator interface for loading validator(s) so pipeline teams can easily add/edit validation rules for Operator bundle validation (no need to wait for a new SDK release).

• establish a set of checks (using validators) to ensure Operator bundle quality (including the checks for the upcoming file-based catalog).

• work with Operator teams to come up with more scorecards to warrant functional correctness.

Deliverables

• Operator SDK provides a validator interface for loading validator(s) either locally or in-remote for the "bundle validate" command.

• work with Red Hat pipeline team to enable “best practices” validating checks for bundles

• establish a set of checks as “best practices” validator to ensure Operator bundle quality (including the checks for the upcoming file-based catalog).

• work with Operator teams to develop custom scorecards to warrant functional correctness. (e.g. set-up a disconnected-like cluster and run your Operator and Operands)