Goals

• implement several optional and required steps to pass the best practice tests currently failing for the CLO
• align the tests so the CLO can be apply the "Meets Best Practices" label in RHEC

Non-Goals

• any regression in collector features or change in functionality, unless explicitly stated and required

Motivation

• The objective is to get our own RH operators this label before we pursue third party operators.

Alternatives

Acceptance Criteria

• all tasks are complete
• all tests pass or have a permanent exception based on the cluster-logging Best Practices Test Results (catalog) and cluster-logging test results. 
• cluster-logging operator shows as Operator in RHEC (currently listed as 'container image')
• KB article created for Certification (example)

Risk and Assumptions

• We assume an exception will be accepted for our other failures, but they may require additional tasks to be completed

Documentation Considerations

• Any tasks or permanent exceptions will be documented in a KBA (example) to use as baseline for future automated continuous testing.

Open Questions

• [ch] Do we manage our entire lifecycle properly?

Additional Notes

• Original Spike:  https://issues.redhat.com/browse/LOG-6999

• CNF Certification Doc: Operator Best Practice Certification & Continuous Testing
• All CNF best practice test results are complete against OCP 4.17 and need stakeholders to review and comment on the cluster-logging Best Practices Test Results. 
• The ask is for stakeholders to review recommendations in Column B and comment under column A. The remaining failures end up producing a permanent exception, based on feedback from operator owners/stakeholders.