Open merlijn-sebrechts opened 7 years ago
I think this requires some hints from design.
@galgalesh
@elvirafigueras
A user that wants to browse to the application's GUI will end up on this page. If the application isn't exposed, then the page should explain three things to that user.
a) The application indeed has a GUI. b) The GUI isn't currently accessible. c) You can make the GUI accessible by exposing the service.
How does this page do that?
a) By showing the open ports and ip. (no change needed) b) The page hints at this by making the public addresses not clickable. (I don't think this is clear enough.) c) not
Hiding the public addresses only solves b) if the user knows that something is missing, which will not be the case for new and inexperienced users. Maybe a solution is to hide the public addresses and put an "expose" button in its place? I think this makes b) a lot clearer and this also fixes c).
The addresses in the "IP addresses" section are the "private addresses" of those units. The links are "clickable" but clicking on them without a VPN [1] will result in a new browser tab that keeps loading until time-out as shown in the screenshot.
So yes, some messaging for this would be perfect!
[1] Note that, on some private clouds(MAAS, openstack, ..), users will be able to connect to the private address of a unit without a VPN. This depends on the specific setup of the cloud.
When I'm on the unit detail page, I see that the private addresses are clickable but the public ones aren't.
There is no guidance to why the public addresses aren't clickable. It would be great to have maybe an explanation or a link to the "expose application" page.
Surfing to the private addresses won't be possible unless you are using a VPN to the internal network. It might be useful to explain that on this page.