Endpoint Detection and Declaration


Lightbend Orchestration is no longer actively developed and will reach its End of Life on April 15, 2020.

We recommend Migrating to the Improved Kubernetes Deployment Experience.

An endpoint defines how your application communicates with other services and the outside world. Endpoints have a name and optionally an ingress declaration. Ingress defines how your application should be accessible from outside of the cluster, whether that be via path-based routing, virtual hosts, or simply by load balancer ports.


Endpoints are specified using the endpoints sbt setting. For example, the following declares an endpoint, http, that is available on ports 80 and 443 via the virtual host myservice.example.org:

endpoints += HttpEndpoint(
  name = "http",
  ingress = HttpIngress(
    ingressPorts = Vector(80, 443),
    hosts = Vector("myservice.example.org"),
    paths = Vector.empty))

For Play applications, an endpoint, http, is automatically added for Play’s HTTP server.

For Lagom applications, an endpoint, http is automatically declared for each microservice with the appropriate ingress settings. The service locator offers tight integration with it, allowing you to find other services by simply looking up their service name.


When generating configuration for Kubernetes using the rp tool, Service declarations are created for each endpoint. Additionally, if any ingress settings are defined for the endpoint, the appropriate Ingress resources will be created and configured to point at the appropriate service.


When generating configuration for DC/OS using the rp tool, Marathon Port Definitions are generated for each microservice. Additionally, if any ingress settings are defined for the endpoint, the appropriate Marathon-lb configuration is defined.