skydns2 backend broken for multiple ports about registrator HOT 5 CLOSED

I think I'll chat to the skydns folks about how they think services that expose multiple ports should be handled. I don't think they're aiming at standard SRV lookup.

from registrator.

Since I didn't add skydns, can you clarify the difference in how it works and how it should work?

from registrator.

Hmmm. It should be broken for etcd too. Let me take a look and figure out
what you did there.

If I specify SERVICE_ID AND SERVICE_NAME for a container that exposes 26379
and 6379, only 6379 makes it into skydns.
On 14 Oct 2014 18:55, "Jeff Lindsay" [email protected] wrote:

Since I didn't add skydns, can you clarify the difference in how it works
and how it should work?

—
Reply to this email directly or view it on GitHub
https://github.com/progrium/registrator/issues/33#issuecomment-59078535.

from registrator.

@sheldonh it looks like instead of setting one SERVICE_NAME and one SERVICE_ID for the container, you need to use this method of providing unique names on a per-port basis: Multiple services with metadata.

The default naming pattern appends the port number if there are multiple ports exposed by the container, e.g. "web-80" and "web-443". However, if you set SERVICE_NAME explicitly, it's overriding that name for all exposed ports.

Perhaps a warning would help if multiple services in the container have the same id and name.

from registrator.

Sounds like it's working as expected and @mgood's suggestion for the workaround sounds right.

from registrator.