Epic Goal

The File Integrity Operator use the operator-sdk project for managing the deployment framework. As the deployment framework changes, there are changes necessary in the operator in anticipation for 4.11. The operator-sdk engagement team provided us a review and report of these items. The goal is to address the items in the report.

Why is this important?

The report's findings cover issues that need to be addressed to ensure compatibility with 4.11+. Some are minor and could be reasonably deferred. One item is critical for both operators (operator-sdk version update/migration) and comprises the bulk of the epic's work.

Scenarios

Address items from the operator-sdk report for the File Integrity Operator

Acceptance Criteria

File Integrity Operator deploys and runs properly on 4.11

Dependencies (internal and external)

None

Open questions::

None

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>