provide a simple REST API to find the public IP / DNS / route of a service

[jstrachan]

right now a service has a private portalIP and could have publicIPs; then it could have routes and could have DNS entries and other things. So its not totally trivial for a client to grok the public address.

It'd be nice if there was an easy REST API to be able to find the IP / host name(s) that should be used for a service given its name. Similar to the endpoints addresses REST API; but to find the public addresses (rather than endpoints implementing a service).

Something like * GET /api/v1beta4/services/{name}/public*

{
  "kind": "PublicServiceAddressList",
   ...
  "items:" [
    {
       "address": "hostOrIPAddress",
       "port": 1234
    },
    {
       "address": "hostOrIPAddress",
       "port": 1234
    }
  ]
}

Either that or we should include this metadata inside the service JSON?

[bparees]

@pweil- @abhgupta can one of you take a look at this request?

[pweil-]

@jstrachan - agree, the info is scattered between multiple objects at the moment and makes it difficult to grok.

There is currently an upstream issue that proposes a reorg of services for v1beta3 that includes route specs, dns specs, portals, and more. kubernetes/kubernetes#2585 (comment)

With that implementation, I think doing a GET on the service itself might be enough to give you all the info you're looking for.

[danmcp]

cc @smarterclayton

[openshift-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.
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