You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
My problem is link to the usage of Vcluster. With Vcluster, I have virtual cluster (with proper etcd) inside my K8S cluster. The workload (pod) are run / sync on host cluster but not the other component like Deployement, STS, etc ...
So KRR is not able to scan those pod because KRR only focus on Deployement, sts etc.
Prom exporter is on host cluster, so only know objects present on host cluster (not inside the vcluster).
Bonus, to avoid conflict, Vcluster rename the pod during the sync. So Prom have metric for pod like "myPod-HashId" when inside vcluster the pod name is "myPod". That mean, event running KRR inside vcluster is not possible because the POD name (inside vcluster) is not the same as the metric name that come from Host cluster.
Describe the solution you'd like
Ability to scan POD object directly.
Describe alternatives you've considered
Run inside vcluster, but as name are different, this not work.
Are you interested in contributing a PR for this?
Yes. (but my python knowledge are really low :D) If yes, we will provide guidance what parts of the code to modify and help you.
Additional context
Not sure if this PR cover my needed : #266
Example from Host view (where prom metric are) : dp-app-demo-5fbc4d8f54-2cm9c-x-demo-develop-client1--073b2da98c
Same inside vcluster : dp-app-demo-5fbc4d8f54-2cm9c
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
My problem is link to the usage of Vcluster. With Vcluster, I have virtual cluster (with proper etcd) inside my K8S cluster. The workload (pod) are run / sync on host cluster but not the other component like Deployement, STS, etc ...
So KRR is not able to scan those pod because KRR only focus on Deployement, sts etc.
Prom exporter is on host cluster, so only know objects present on host cluster (not inside the vcluster).
Bonus, to avoid conflict, Vcluster rename the pod during the sync. So Prom have metric for pod like "myPod-HashId" when inside vcluster the pod name is "myPod". That mean, event running KRR inside vcluster is not possible because the POD name (inside vcluster) is not the same as the metric name that come from Host cluster.
Describe the solution you'd like
Ability to scan POD object directly.
Describe alternatives you've considered
Run inside vcluster, but as name are different, this not work.
Are you interested in contributing a PR for this?
Yes. (but my python knowledge are really low :D) If yes, we will provide guidance what parts of the code to modify and help you.
Additional context
Not sure if this PR cover my needed : #266
Example from Host view (where prom metric are) : dp-app-demo-5fbc4d8f54-2cm9c-x-demo-develop-client1--073b2da98c
Same inside vcluster : dp-app-demo-5fbc4d8f54-2cm9c
The text was updated successfully, but these errors were encountered: