The operator controller ensures that the correct bundleDeployments exist for each entity in the solution set

[awgreene]

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.

[varshaprasad96]

Attempting to break down the implementation. Please correct me if I'm wrong.

The DeppySolver outputs a solution set which is basically a map of deppy.Identifier and boolean indicating if it was selected for installation or not. If selected, check for the existence of bundle deployment.

Copying the acceptance criteria based on #65:

• 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.
• If a bundleDeployment exists for an entity that is no longer in the solution set, delete the bundleDeployment.

I believe the entity ID would be a unique identifier based on packageName+Version? Is the naming convention already decided, or is a todo based on how we construct the entity sources in #77?

[awgreene]

@varshaprasad96 sorry for the delay, I've updated the description of the ticket with the proper background / AC.

I believe the entity ID would be a unique identifier based on packageName+Version? Is the naming convention already decided, or is a todo based on how we construct the entity sources in #77?

This should be completed as a part of #74

[awgreene]

Completed in #104