User Story

• As a user, I would like the Operator Controller to create a bundleDeployment for each entity in the solution set returned by Deppy.

Background

• The Operator Controller will has a set of objects that contain both a packageName and bundle URL. The Operator Controller must then ensure that the correct bundleDeployments exist on cluster.
  • The packageName and bundle URL object will be available once OLM-2836 is delivered.

Acceptance Criteria

• Only one bundleDeployment is ever present for a particular package.
• If the solution set contains an entity that is not related to an existing bundleDeployment, create the bundleDeployment
• If the solution set contains an entity that is an upgrade for an existing bundleDeployment, update the bundleDeployment (Non-Blocking, nice to have).
• If the operator-controller previously created a bundleDeployment for a entity in the solution set that is no longer present, delete the bundleDeployment.
• Unit tests are created that ensure:
  • a valid bundleDeployment is created for each Operator CR.
  • existing bundleDeployments are updated if a new version of the operator is available in the deppy source (Non-Blocking, nice to have).
  • existing bundleDeployments are removed if their associated operator CR is deleted.

Out of Scope

• Dependencies
• Outside constraints that invalidate an existing bundle deployment, such as supported cluster versions.

Upstream Issue

• https://github.com/operator-framework/operator-controller/issues/77