This issue concerns the add new route screen in OpenShift Origin. Compare the simplicity of the oc command compared to the UI equivalent:
oc expose service parksmap
vs
I think it might be better to follow a progressive disclosure pattern on this screen, and by default showing only those fields necessary to create the route with the extra options hidden below a toggle. E.g., a great example of progressive disclosure at work in a very similar type of problem is when you do add to project > (choose python / 3.5) > click on advanced. by default you get the bare basics, but you can open up the more specific opts on demand only if needed. That way, newer users / users with simpler needs can get things done more quickly with less distractions / overwhelm. Here's how that looks:
Version
oc v1.5.1+7b451fc
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://console.gshipley.gce.pixy.io:8443
openshift v1.5.1+7b451fc
kubernetes v1.5.2+43a9be4
This issue concerns the add new route screen in OpenShift Origin. Compare the simplicity of the oc command compared to the UI equivalent:
vs
I think it might be better to follow a progressive disclosure pattern on this screen, and by default showing only those fields necessary to create the route with the extra options hidden below a toggle. E.g., a great example of progressive disclosure at work in a very similar type of problem is when you do add to project > (choose python / 3.5) > click on advanced. by default you get the bare basics, but you can open up the more specific opts on demand only if needed. That way, newer users / users with simpler needs can get things done more quickly with less distractions / overwhelm. Here's how that looks:
Version
oc v1.5.1+7b451fc
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://console.gshipley.gce.pixy.io:8443
openshift v1.5.1+7b451fc
kubernetes v1.5.2+43a9be4