DNS based service discovery about olric HOT 8 OPEN

Hey @luisdavim,

Thank you for reporting this. It would be good having a default implementation based on DNS. Olric already depends on (indirectly) github.com/miekg/dns. I think this task can be a good first issue. Please feel free to provide a design document and create a PR for this feature.

from olric.

Is this still relevant?

I am looking for my first issue and this seems easy enough.

from olric.

Yes, I think this is still relevant.

from olric.

Is this still relevant?

I am looking for my first issue and this seems easy enough.

Hello,

Yes, it's still relevant but we should start working on an RFC before implementing the feature.

from olric.

Ok. I am sorry but I am not sure what you mean by an RFC.

If I understood this issue correctly, what you want is something similar to how nginx dns service discovery works.

My initial idea is to implement the ServiceDiscovery interface and simply create a default plugin for service discovery.

However I am quite green and would appreciate some guidance.

from olric.

Plugins for service discovery already exist. The point of this issue is to have a native, default service discovery mechanism.

See also:

• https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
• https://www.haproxy.com/blog/dns-service-discovery-haproxy

from olric.

Plugins for service discovery already exist. The point of this issue is to have a native, default service discovery mechanism.

If I understand it correctly, plugins for service discovery are written in Go, and they implement an interface from here. That package is the common dependency between orlic and service discovery plugin (orlic consumes the interface, the plugin implements it).

All I would need to do is provide a default implementation that is used instead where appropriate. Am I on the right track here?

from olric.

The idea is that we would have a default service discovery mechanism based on DNS, without having to use plugins.

An RFC (request for comments) is a document where you would explain the proposed implementation so it cabeceiras reviewed and agreed upon before starting the actual implementation.

from olric.