You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 30, 2019. It is now read-only.
This globally sets the default discovery method to kubernetes-api, which is only appropriate to use for Cluster Bootstrap and not for inter-service discovery.
While this recipe does not currently use Akka Discovery for anything else, users are likely to copy it as it is. Anyone using the Akka gRPC integration will need another global default discovery method, and in the future, Lagom will have a ServiceLocator implementation based on Akka Discovery.
The recipe should be updated to set akka.management.cluster.bootstrap.contact-point-discovery.discovery-method instead of akka.discovery.method, as described in akka/akka-management#316.
The text was updated successfully, but these errors were encountered:
This is the current configuration for the Cluster Bootstrap Discovery Method:
lagom-recipes/kubernetes-deployment/hello-kubernetes-java-mvn/hello-impl/src/main/resources/prod-application.conf
Lines 10 to 16 in 2203a64
lagom-recipes/kubernetes-deployment/hello-kubernetes-java-mvn/stream-impl/src/main/resources/prod-application.conf
Lines 10 to 16 in 2203a64
This globally sets the default discovery method to
kubernetes-api
, which is only appropriate to use for Cluster Bootstrap and not for inter-service discovery.While this recipe does not currently use Akka Discovery for anything else, users are likely to copy it as it is. Anyone using the Akka gRPC integration will need another global default discovery method, and in the future, Lagom will have a
ServiceLocator
implementation based on Akka Discovery.The recipe should be updated to set
akka.management.cluster.bootstrap.contact-point-discovery.discovery-method
instead ofakka.discovery.method
, as described in akka/akka-management#316.The text was updated successfully, but these errors were encountered: