-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Network view should group pods into higher level workload #5468
Labels
enhancement
New feature or request
Comments
Whoever fixes this, please also right justify the network view |
This was addressed for the normal tree view, but not the network tree view |
Merged
10 tasks
Maybe something like this: podGroups-NetworkView.mov |
10 tasks
keithchong
added a commit
to keithchong/argo-cd
that referenced
this issue
May 9, 2022
…proj#5468) Signed-off-by: Keith Chong <kykchong@redhat.com>
keithchong
added a commit
that referenced
this issue
May 12, 2022
… (#8996) Signed-off-by: Keith Chong <kykchong@redhat.com>
keithchong
added a commit
to keithchong/argo-cd
that referenced
this issue
May 13, 2022
Signed-off-by: Keith Chong <kykchong@redhat.com>
10 tasks
alexmt
pushed a commit
that referenced
this issue
May 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The network view does not look good when you have a large application with many pods.
Most of the time, users don't care how traffic is routed to individual pods, but rather to some higher level workload that created that pod (e.g. ReplicaSet).
Proposal
Instead of showing lines to many pods, we should connect the service to the parent of the pod. Possibly leveraging what we did in the pod view:
The text was updated successfully, but these errors were encountered: