Closed freegroup closed 6 years ago
Hi, the status tags are set by the gardener, we cannot influence this. During reconcile they become unavailable but nothing changed in this behavior recently. Likewise, it is nothing new that clusters are getting reconciled from time to time. Previously, we showed the progress as percentage instead of the tractor icon. While we can discuss if a tractor is the best icon to indicate that a reconcile operation is running, I do not fully understand why this minor change causes that much confusion. As I already pointed out, also in previous releases the status tags were gone during reconcile and a progress was shown instead of the checkmark icon...
This is the problem with UX. minor changes can have a big impact. :-) In the end, I get notified that the gardener seems to have a problem right now...
but now honestly - status indicator not there and "Bob the builder" icon - what should the user think?
I think the main issue is that during reconciliation the status tags are not visible. @rfranzke is there a technical reason for this? Could we not keep the last state and only replace it with an updated state after reconciliation? This way, the buttons would not disappear.
That would indeed be helpful. As long as the reconciler has not found issues, the last known status should be shown. That also goes the other way, i.e. whether it was healthy or unhealthy before. Not sure how difficult it would be and what needs to be considered, but from usability PoV, it would definitely be preferable.
@rfranzke We discussed this topic in our UI sync with @vlerenc. May you have another look at the code and change the logic to not remove the labels during reconciliation? This would be very helpful to reduce confusion for the users @freegroup In addition, we decided to change the tractor to a blue checkmark with a progress during reconciliation.
I don't really remember why we disabled the health check while an operation is processing. We might have taken this decision because of this one: If we remove this behaviour the care controller doing the health check would also start its work for newly created clusters and for cluster which are to be deleted or currently in the deletion process. In those cases most of the checks will fail and appear red in the UI. I guess we assumed that this would generate more confusion than just not doing the checks while an operation is in progress.
I still don't fully understand why you do not send the last state of the health checks during reconciliation - a workaround would be to show something like "Health information not available during reconciliation" in the dashboard. But it would be even better if the last result of the health check would stay available during the operation.
So we changed the icon in our upcoming release:
In case of an error during reconcile, an exclamation mark will replace the checkmark:
As you can see, the readiness tags are still not visible during reconcile. @rfranzke, @vlerenc any final thoughts on this before I close this issue?
@Adracus is working on this, i.e. preserving the conditions while reconciling and only changing the conditions, when the condition indeed changes.
since yesterday I got feedback and questions from several stakeholder that the cluster seems to be unstable - After a few investigations, however, it turns out that the clusters are 100% operable. But where does the user's uncertainty come from?
It seems that the icon, which indicates the reconcile, is the problem. It gives you the impression that something is happening/repairing because there is also a forklift in the icon. Additional the status TAG's are missing.
Why not stay the checkmark inside the icon during the reconcile? I think you should allow/use a green checkmark as long as you haven't found a problem.
At the moment the users seems to have a problem with the current UX pattern.