Skip to content
This repository has been archived by the owner on May 6, 2019. It is now read-only.

Suggest using DNS instead of kube-api on README #54

Open
ignasi35 opened this issue Feb 18, 2019 · 2 comments
Open

Suggest using DNS instead of kube-api on README #54

ignasi35 opened this issue Feb 18, 2019 · 2 comments

Comments

@ignasi35
Copy link
Contributor

REAMDE.md explains how an implementation of an Akka Discovery mechanism is necessary and uses Kubernetes-API as an example. I think in production users are unlikely to use Kubernetes-API for service-to-service discovery and we should use a production ready example like DNS

@TimMoore
Copy link

I think it would make sense to provide a default via play/reference-overrides.conf that configures the aggregate method with configuration first, and then DNS. This should be a suitable default for almost everyone, and only people with truly custom service registries should need to customize this.

@TimMoore
Copy link

Note that those methods are all part of the core Akka Discovery module, and don't require additional dependencies.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants