Web based Kubernetes Dashboard with a focus on privacy that requires no active components or special privileges in your cluster.
Apache License 2.0
24
stars
48
forks
source link
UXC-10 & 15 & 19: Having two semantics with different terminology for the status “Bound“ and “Available” or “Completed” and “Running” should be discussed #3004
Description
UXC-10 & 15 & 19:
Having two semantics with different terminology for the status “Bound“ and “Available” or “Completed” and “Running” should be discussed with UA -> Because you lose context of the semantic of the object status
In general, to make it more easy for users to scan the table pages it would be important to have very clear definitions of what’s green, what’s orange, what’s red, and not to mix them up.
This also means having consistent terminology between the different resources.
Description UXC-10 & 15 & 19: Having two semantics with different terminology for the status “Bound“ and “Available” or “Completed” and “Running” should be discussed with UA -> Because you lose context of the semantic of the object status
In general, to make it more easy for users to scan the table pages it would be important to have very clear definitions of what’s green, what’s orange, what’s red, and not to mix them up.
This also means having consistent terminology between the different resources.
Reasons https://wiki.one.int.sap/wiki/display/uxc/UXC-019 https://wiki.one.int.sap/wiki/display/uxc/UXC-015 https://wiki.one.int.sap/wiki/pages/viewpage.action?spaceKey=uxc&title=UXC-010
Attachments