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

Add label-selector to mitigate workload and data volume #68

Open
semihbkgr opened this issue Mar 3, 2024 · 0 comments · May be fixed by #69
Open

Add label-selector to mitigate workload and data volume #68

semihbkgr opened this issue Mar 3, 2024 · 0 comments · May be fixed by #69

Comments

@semihbkgr
Copy link

This tool may not be applicable to large clusters as it lists all resources within the cluster. We can address this by filtering resources based on labels. It would alleviate the workload and reduce the transmitted data volume from the kube-api.

e.g:

$ kubectl tree hazelcast hz --selector='app.kubernetes.io/instance=hz'                                   ✔ │ 11:28:09 PM  
NAMESPACE  NAME                                  READY  REASON  STATUS   AGE
default    Hazelcast/hz                          -              -        30s
default    ├─Role/hz                             -              -        30s
default    ├─RoleBinding/hz                      -              -        30s
default    ├─Secret/hz                           -              -        30s
default    ├─Service/hz                          -              -        30s
default    │ └─EndpointSlice/hz-t7b2k            -              -        30s
default    ├─ServiceAccount/hz                   -              -        30s
default    └─StatefulSet/hz                      -              -        30s
default      ├─ControllerRevision/hz-7855bcc97c  -              -        30s
default      ├─Pod/hz-0                          True           Current  30s
default      ├─Pod/hz-1                          True           Current  30s
default      └─Pod/hz-2                          True           Current  30s
@semihbkgr semihbkgr linked a pull request Mar 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant