RFE - centralize information about route & registry in About page

[jupierce]

In OpenShift 3.x, the About page displayed information about routes, DNS, and how to access the internal registry. In OpenShift 4, this information is available, but distributed around the UI. Personnel fielding user issues with starter clusters are interested in having a single link they can share to get users on track and would benefit from this information being restored.

Opening here so that stakeholders can discuss. cc: @jiri-fiala @wgordon17

[wgordon17]

Here's a screenshot of the information that we're providing in v3:

[spadgett]

For context, here are the 4.x implementations: #1431 and #1491

This actually seems more hidden to me than showing up directly on the resource pages themselves. If you have a route, you can see the canonical router hostname for that route. If you have an image stream, you can see specific commands for pushing to and pulling from that image stream.

From an implementation standpoint, this is tricky because we don't know the router hostname without actually have a route resource.

I'm not sure if this will work in environments when there are multiple routers since there isn't a single router hostname as I understand. cc @ironcladlou

[spadgett]

We could conceivably get the public registry hostname from one of the image streams in the openshift namespace and show it in the about dialog. Router canonical hostname is more difficult.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.