Staus indicator is vague and unclear #15
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
wg/cre
Issues or PRs related to the Custom Runtime Environment (fka Custom Notebook Image) ODH feature.
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current status indicator for a pending CRE is as follows:
image stream phase (CRE phase as fallback if image stream has not been created) is used as the main indicator on status. Error messages are pulled from the latest CRE condition.
Intended Functionality
The status indicator should only use the CRE conditions. These conditions are presented as a list of states a cre can be in. Current status can determined by the last presented condition in the list. However when a user hovers over the status symbol, the more detailed description of the status should be shown (error message).
In some case taking the latest CRE condition isn't always the best option, so a more algorithmic approach will be needed to present the user with the most accurate staus and detail messages.
For example, when the pipelines fail, the last condition is broadly the pipeline failed..., while the more detailed error message is found in the condition just before it
Optionally, a history of the CRE staus could be shown as a simple table/list when viewing the CRE in edit mode or another view.
Acceptance Criteria
related thoth-station/meteor-operator#130
The text was updated successfully, but these errors were encountered: