Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add status.resolvedBundleSource #202

Closed
Tracked by #183
awgreene opened this issue May 9, 2023 · 0 comments · Fixed by #213
Closed
Tracked by #183

Add status.resolvedBundleSource #202

awgreene opened this issue May 9, 2023 · 0 comments · Fixed by #213
Assignees
Milestone

Comments

@awgreene
Copy link
Member

awgreene commented May 9, 2023

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
2 participants