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

Extend operator Status for improving user experience #240

Open
gazarenkov opened this issue Feb 27, 2024 · 0 comments
Open

Extend operator Status for improving user experience #240

gazarenkov opened this issue Feb 27, 2024 · 0 comments
Labels
jira Issue will be sync'ed to Red Hat JIRA kind/epic
Milestone

Comments

@gazarenkov
Copy link
Member

gazarenkov commented Feb 27, 2024

This is the follow-up of improving Operator Status topic.
For the time being the only information we can obtain from the Status is where the operator succeeded with creation runtime objects (Deployments, Services, default configurations etc)
Ideally, the Status should NOT be overloaded but contain enough information for User and dependent code to make it clear:

  • What's going on with runtime and where to see more detailed information if something going wrong.
  • How to reach Backstage application (best effort of exposing direct URL or some hints how to obtain it)
  • What configuration objects (ConfigMaps, Secrets) take part in Backstage Application config
  • As part of the Level 2 Capability Level, the operator should convey inability to manage an unsupported version of the Operand in the status section of the CR
  • ... (not limited to)
@github-actions github-actions bot added the jira Issue will be sync'ed to Red Hat JIRA label Feb 27, 2024
@gazarenkov gazarenkov added this to the M3 milestone Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira Issue will be sync'ed to Red Hat JIRA kind/epic
Projects
None yet
Development

No branches or pull requests

1 participant