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 Progressing condition type? #126

Open
joelanford opened this issue Feb 13, 2023 · 0 comments
Open

Add Progressing condition type? #126

joelanford opened this issue Feb 13, 2023 · 0 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@joelanford
Copy link
Member

joelanford commented Feb 13, 2023

As of #217, we have removed the Ready condition, and we added the Installed condition in #218 and Resolved condition in #213.

We may want to consider another condition type called Progressing that tells a user that the controller is working toward (or not) achieving the desired state specified in the operator spec.

This would be useful to understand context when status.installedBundleSource and status.resolvedBundleSource differ.

@joelanford joelanford mentioned this issue Mar 1, 2023
3 tasks
@tmshort tmshort mentioned this issue May 18, 2023
4 tasks
@joelanford joelanford changed the title Rename Ready condition? Add Progressing condition type? May 19, 2023
@awgreene awgreene added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

2 participants