You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a placeholder/container issue to track bugs, UX, etc issues discovered during hackweek
Low value bugs (fixes should be straight forward)
(BUG) Rancher Backups / Backups / Create - Schedule placeholder suggests @midnight yet when entered we say this is an Invalid cron schedule
(BUG) Persistent Volume Detail Page (default Config tab)- Border box showing the associated PVC grows crazy high when the 'Customise` tab is selected
(BUG/UX) Detail Masthead - Age field is not live
Screenshot taken many minutes after creation. Given that our table age is live, this seems a bit misleading
(BUG) Setup Page has no vertical scroll bar
Note - Would Sean's changes to a responsive log in page fix this?
High Value UX
(UX) K9S Comparison - There's no way to see an overview of which pods are consuming high CPU/Memory. This is useful when your tiny node can't hack it, made worse when it can't handle monitoring app. The info is shown in k9s, but didn't see it in kubectl get pod -n cattle-system -o wide
(UX) Resource Finalizers - It's not obvious if a resource has a finalizer. We should make this more prominent (it doesn't have to be in-your-face obvious). As a secondary issue we should then think about how to help the user remove this, as a last resort, to remove a resource. This would help in situations where a cluster was now getting deleted.
(UX) Cluster Tools List - When one is installed we show associated resources. If you click on the card it takes you through to app details page with the Resource list showing by default. If a NS filter is set (like the default) the resource list is empty (which jars when we've just said there are 'x' resources. Generally should detail page resource lists be fitlered by the NS values?
(UX) Mistakes when installing helm apps are costly
If a mistake leads to a condition that will never succeed the user has to wait 10 minutes for the helm operation to fail before deleting/updating the helm app with a fix
There are helm operation pods in progress... but it's hard to align when multiple operations are running
(i tried to install a chart requiring a PVC, then made a mistake when installing longhorn)
Medium Value UX
(UX) Cluster Tools List - Clicking on Install takes user straight to install wizard. I wanted to learn more before installed (via chart detail page)
This is a placeholder/container issue to track bugs, UX, etc issues discovered during hackweek
Low value bugs (fixes should be straight forward)
@midnight
yet when entered we say this is anInvalid cron schedule
High Value UX
kubectl get pod -n cattle-system -o wide
Medium Value UX
Install
takes user straight to install wizard. I wanted to learn more before installed (via chart detail page)this
refers to, specifically when the command isn't shown (windows nodes can't initially be applied)Run the command below....
General (known, issues somewhere)
The text was updated successfully, but these errors were encountered: