Skip to content
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.

Add labels for better application grouping and icons in OpenShift Topology View #66

Closed
3 tasks
rm3l opened this issue Dec 12, 2023 · 2 comments
Closed
3 tasks
Labels
priority/low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@rm3l
Copy link
Member

rm3l commented Dec 12, 2023

User Story

As a user of the Operator on OpenShift, I want, in the Topology View, to be able to distinguish the resources created and managed by the Operator from the rest of my other resources, So that I can have a clear separation between different apps in the same namespace.

While doing a quick test of the RHDH image on OpenShift, I noticed that resources from the Helm Chart are currently grouped and have proper icons displayed for PostgreSQL and Backstage. But resources managed by the Operator are using a generic icon and are floating, making it look like they are completely unrelated.
See the screenshot below - Helm resources on the left, and resources created by the operator on the right:

image

Acceptance Criteria

Notes

@rm3l rm3l added the priority/low Nice to have issue. It's not immediately on the project roadmap to get it done. label Dec 22, 2023
@rm3l
Copy link
Member Author

rm3l commented Dec 22, 2023

I just noticed that Openshift does group the resources when creating a Backstage instance from the list of installed operators, which was my main concern here. It also displays the RHDH icon on both the Backstage and Postgresql pods, which is fine right now.

image

Lowering the priority, but we would still need to use the right icon for Postgresql and set the right annotation to connect both pods.

@rm3l
Copy link
Member Author

rm3l commented Aug 19, 2024

JIRA issue: https://issues.redhat.com/browse/RHIDP-3660

/close

@rm3l rm3l closed this as completed Aug 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority/low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
None yet
Development

No branches or pull requests

1 participant