Epic Goal

• Update the bundleDeployment's status to convey the health of objects.

Why is this important?

• OLM V1 users create an Operator CR in order to install an operator. The Operator Controller then attempts to find an operator that can fulfill the user's needs. If an operator is found, the Operator Controller will create a bundleDeployment, which is a RukPak API that maps to the list of Kubernetes resources that define the operator. The user installing the operator will be very interested in the "health" of the resources defined in the bundleDeployment. If any of the resources are "unhealthy", the user will likely want to investigate the failure.

Previous Work (Optional):

• Technical Brief

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>