Skip to content

Add status.resolvedBundleSource #202

Closed
@awgreene

Description

@awgreene

Once the operator-controller has used the deppy library to solve the solution, it should know "what it's going to install next" for a given operator CR. We can showcase this information in the status in a new resolvedBundleSource field.

A corresponding condition should exist which represents whether or not the operator was resolved:

 Status:
  conditions:
    - type: "Resolved"
       status: "False"
       reason: "BigBad"
       message: "The package does not exist"
       observedGeneration: 2

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions