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

Multi-cluster list view - Applications #5961

Closed
Tracked by #5919
nrfox opened this issue Mar 29, 2023 · 2 comments · Fixed by #5990
Closed
Tracked by #5919

Multi-cluster list view - Applications #5961

nrfox opened this issue Mar 29, 2023 · 2 comments · Fixed by #5990
Assignees
Labels
backlog Triaged Issue added to backlog multicluster Related to multi cluster test: front-end/cypress PR adds/updates front-end tests (unit and/or cypress automation )

Comments

@nrfox
Copy link
Contributor

nrfox commented Mar 29, 2023

Applications list page pulls applications from all configured clusters.

@nrfox nrfox mentioned this issue Mar 29, 2023
4 tasks
@nrfox nrfox changed the title Applications Multi-cluster list view - Workloads Mar 29, 2023
@nrfox nrfox added the backlog Triaged Issue added to backlog label Mar 29, 2023
@nrfox nrfox changed the title Multi-cluster list view - Workloads Multi-cluster list view - Applications Mar 29, 2023
@josunect
Copy link
Contributor

josunect commented Mar 30, 2023

Probably the concept of application is a bit different than a workload or a service. As described in apps.go:

AppService deals with fetching Workloads group by "app" label, which will be identified as an "application"

For what we can see now, probably application doesn't need to be tied to a particular cluster:

image

An application can be the logical view of a subset of workloads from different clusters.
An application doesn't have a Logs tab. Not sure if the telemetry for inbound/outbound traffic is filtered by app label, but if that was the case, if we have the unified metrics, we will keep having the same information.

In that case, probably we would want to remove the cluster column from that view, and include the cluster name in the application details.

Does it makes more sense, or do we want to keep splitting also this view by cluster?

@jshaughn
Copy link
Collaborator

jshaughn commented Mar 30, 2023

Hmm, it is an interesting question. In the graph the app and service nodes are still delimited by cluster. Reviews-East is distinct from Reviews-West. I think probably we should maintain that distinction in the list and detail views, but I'm not 100% sure. The thing is, for a detail page mini-graph you would always get a graph showing the app on all clusters (unless we make a change). My general guidance is that a single app or service that is deployed on different clusters may behave differently on a specific cluster, and a user may want to see it specifically for that cluster. Meaning, the workloads for that App, for example, would be limited to the specific cluster.

@josunect josunect added sub-task Ties an issue to an epic and removed sub-task Ties an issue to an epic labels Apr 5, 2023
@matejnesuta matejnesuta added test-add-coverage 📎 this needs test coverage multicluster Related to multi cluster labels Aug 3, 2023
@matejnesuta matejnesuta added test: front-end/cypress PR adds/updates front-end tests (unit and/or cypress automation ) and removed test-add-coverage 📎 this needs test coverage labels Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Triaged Issue added to backlog multicluster Related to multi cluster test: front-end/cypress PR adds/updates front-end tests (unit and/or cypress automation )
Projects
Development

Successfully merging a pull request may close this issue.

4 participants