Skip to content
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.

Do not identify masters #123

Open
guillermodep opened this issue Jan 3, 2020 · 5 comments
Open

Do not identify masters #123

guillermodep opened this issue Jan 3, 2020 · 5 comments

Comments

@guillermodep
Copy link

Hi, kube resource reports does not get the masters label.

@hjacobs
Copy link
Owner

hjacobs commented Jan 3, 2020

@guillermodep can you be a little bit more specific what the problem is you experience? Please elaborate otherwise it's hard to help.

@guillermodep
Copy link
Author

Hi Henning, sorry for the little information, the issue is that in my okd cluster I have 3 masters, 3 infra and 4 workers, but kube reports see all the nodes as workers.

Please see the information below:

image

KUBE-reports

image

@hjacobs
Copy link
Owner

hjacobs commented Jan 5, 2020

@guillermodep can you paste the output of kubectl get node .... -o yaml for the master nodes here? Kubernetes Resource Report uses the kubernetes.io/role label (https://github.com/hjacobs/kube-resource-report/blob/master/kube_resource_report/report.py#L30), maybe a different label is used in your setup.

@guillermodep
Copy link
Author

U 're right, In OKD the label is: "node-role.kubernetes.io/compute=true", so I going to add the label just in order to try.

@guillermodep
Copy link
Author

"node-role.kubernetes.io/compute=true" this is for workers, for masters is: "node-role.kubernetes.io/master=true"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants