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

empty report #1

Closed
Elexy opened this issue Aug 29, 2019 · 4 comments
Closed

empty report #1

Elexy opened this issue Aug 29, 2019 · 4 comments

Comments

@Elexy
Copy link

Elexy commented Aug 29, 2019

I am running doctor on my arm k3s cluster and get presented with an empty report:

 kubectl doctor                                                                     ✔  1223  16:45:35
INFO[0000] Going for a full scan as no flags are set!   
INFO[0000] Retrieving necessary clientset for targeted k8s cluster. 
INFO[0000]                                              
INFO[0000] Fetched namespaces: [default kube-node-lease kube-public kube-system] 
INFO[0000]                                              
INFO[0000] Starting triage of cluster crucial component health checks. 
INFO[0001] Starting triage of nodes that form the cluster. 
INFO[0001] Starting triage of cluster-wide Endpoints resources. 
INFO[0002] Starting triage of cluster-wide pvc resources. 
INFO[0002] Starting triage of cluster-wide pv resources. 
INFO[0002] Starting triage of deployment resources across cluster 
INFO[0004] Starting triage of replicasets resources across cluster 
INFO[0007] Starting triage of cronjob resources across cluster 
INFO[0009] Triage report coming up in yaml format:      

---
 TriageReport: []

is there any way I can get a bit more (debug) info to figure out why?

@emirozer
Copy link
Owner

Yeah in that case you literally have a clean cluster with no matching anomaly cases, I should give more info there not an empty report

@Elexy
Copy link
Author

Elexy commented Aug 29, 2019

LOL, let me deploy something and check again!

@Elexy Elexy closed this as completed Aug 29, 2019
@emirozer
Copy link
Owner

hahahahahha :D its alright, you still have a valid point :P

emirozer added a commit that referenced this issue Aug 29, 2019
@emirozer
Copy link
Owner

alrighty, i just made a quick release to improve this situation :)

https://github.com/emirozer/kubectl-doctor/releases

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

No branches or pull requests

2 participants