Services could link to the api service proxy

[colemickens]

Dashboard version: 1.4.0-beta1
Kubernetes version: 1.4.0-alpha.3
Operating system: ubuntu
Node.js version: n/a
Go version: n/a

Just a nice to have feature req:

It would be nice if dashboard could detect that I'm accessing it through the service proxy and then offer to make these internal endpoints hyperlinks as well.

[bryk]

That's good suggestion. We though about it in the past, but then realized that it is hard to detect whether you're running behind the proxy. Will take a closer look at this after our next release.

[maciaszczykm]

Another potential issue here is, that proxy might not allow enter all of the services. Number of them can be filtered or inaccessible through proxy. We'll have to investigate it deeper to find out if it's possible to implement.

[colemickens]

"filtered" or "inaccessible" ?

The only thing I can think of is cases where the user running kubectl proxy has limited RBAC roles.

(This brings up the point that the dashboard is basically bypassing RBAC in many cases).

[maciaszczykm]

@colemickens In my understanding, in case of kubectl proxy --api-prefix=/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard usage, only http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard will be served.

[colemickens]

Oh thanks for explaining, I didn't know that!

[maciaszczykm]

No problem. It's not so clearly described in kubectl proxy --help.

[cheld]

Relates to
#2249

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[maciaszczykm]

As it was already said it is hard to detect if the proxy is used and if given service is available. I will close it until we will find a good solution.