-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Dashboard panics on getting heapster selector when stateful sets not supported by cluster #1916
Comments
What is your kubernetes version? I have found only 1 situation where this error might occur and it is if cluster does not support stateful sets. We should fix that anyway. I have renamed issue title because this one is too generic. |
I'm encountering this issue as well:
My cluster only had one ss and pod when this happened - deleting and re-creating the ss caused the error to go away. Will post stacktrace if i encounter it again |
We will remove this check and return no metrics instead of panic. |
I have checked and this is already fixed by #2017. |
one side note: the same error will pop up if you have typo in the yaml file for statefulset. e.g. imagePullPolicy: always, which should be Always. in case anyone run into the same issue. |
Issue details
Environment
Steps to reproduce
Observed result
Dashboard reported Unknown Server Error (500):
Expected result
Comments
The text was updated successfully, but these errors were encountered: