-
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 errors if pod's owner reference is not supported #3251
Comments
We have to solve it because there are multiple resources that are not supported. |
@yqwang-ms If you are familiar with Go, perhaps you would be interested in fixing this issue so we can release fix for it :) We are quite occupied with Angular migration and we do not have time for it at the moment. |
Thanks @maciaszczykm for the comment, I will try first but not sure :) |
Hi @maciaszczykm I have not got free to look into the code, do you have resource to fix it now? :) |
At the moment I am focused on getting ng migration done. Perhaps someone else will pick it up. |
@maciaszczykm is this planned to be included in next release, or earliest 2.0.0? It is tiny fix, but would be great to have it for these who already use CRDs early (kubeflow/spark-operator#484). |
Earliest in 2.0.0, @mrow4a. If you would be willing to create bugfix branch on top of old release then we can get it released perhaps. |
Steps to reproduce
The pod is created as:
podObject.OwnerReferences = []meta.OwnerReference{*meta.NewControllerRef(configMapObject, ConfigMapGroupVersionKind)}
Environment
Observed result
Dashboard reported Internal Server Error (500):
Comments
By setting the owner is also a controller, the Pod functions normally, except for its detail cannot be viewed from kube dashboard, and the dashboard shows error:
"Unknown reference kind ConfigMap".
Seems this is related to #3158
Please help :)
The text was updated successfully, but these errors were encountered: