-
Notifications
You must be signed in to change notification settings - Fork 27
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
Operator doesn't show the status for Kepler #315
Comments
Please ignore the above comment. It turns out that I mixed the issue. It will be helpful to run |
So the issue regarding why the status is not shown is because the OLM does not seem to handle nested fields very well. Conditions is nested inside of ExporterStatus in the KeplerStatus struct. Note KeplerStatus only contains one field which is ExporterStatus. One strategy is to flatten ExporterStatus and pull out the Conditions. The Conditions can then be populated by ExporterStatus or other Statuses in the future like ModelServer. This may not be necessary because KeplerInternal should handle this? Is this strategy ok? I am not sure if there is another way. |
@KaiyiLiu1234 , thanks for the update. I think issue doesn't make it clear what we are trying to achieve. The object of this task is to explore if UI honours - https://github.com/openshift/console/blob/master/frontend/packages/operator-lifecycle-manager/src/components/descriptors/reference/reference.md#3-conditions and we can specify the path to |
We don't see any exporter status when deploying Kepler using the latest bundle
quay.io/sustainable_computing_io/kepler-operator-bundle:v1alpha1
on the OpenShift console.Below attached is the screenshot for reference:
The text was updated successfully, but these errors were encountered: