Skip to content
This repository was archived by the owner on May 25, 2023. It is now read-only.

Conversation

eed3si9n
Copy link
Contributor

@eed3si9n eed3si9n commented Jan 8, 2019

This creates labels for com.lightbend.rp.management-endpoint and com.lightbend.rp.remoting-endpoint, and changes the default names to "management" and "remoting", following the convention set in Akka Management documentation.

Ref lightbend/reactive-cli#177

/cc @lightbend/play-lagom

@ghost ghost assigned eed3si9n Jan 8, 2019
@ghost ghost added the review label Jan 8, 2019
eed3si9n added a commit to eed3si9n/reactive-cli that referenced this pull request Jan 8, 2019
Fixes lightbend#177

This specifies the management endpoint name explicity to `-Dakka.management.cluster.bootstrap.contact-point-discovery.port-name`.
By default the management endpoint name will fallback to `"akka-mgmt-http"` for backward compatibility.

In the future, sbt-reactive-app can declare the management endpoint name using "management-endpoint" as a label on the Docker image. See lightbend/sbt-reactive-app#164.

These changes combined together provides softlanding of the switch to `"management"` in akka/akka-management#274.
eed3si9n added a commit to eed3si9n/reactive-cli that referenced this pull request Jan 8, 2019
Fixes lightbend#177

This specifies the management endpoint name explicity to `-Dakka.management.cluster.bootstrap.contact-point-discovery.port-name`.
By default the management endpoint name will fallback to `"akka-mgmt-http"` for backward compatibility.

In the future, sbt-reactive-app can declare the management endpoint name using "management-endpoint" as a label on the Docker image. See lightbend/sbt-reactive-app#164.

These changes combined together provides softlanding of the switch to `"management"` in akka/akka-management#274.
@thomschke
Copy link

When running an akka cluster in a service-mesh (like istio), then there is a requirement for port names.

Service ports must be named. The port names must be of the form [-] with http, http2, grpc, mongo, or redis as the in order to take advantage of Istio’s routing features.

For akka-management the port-name should be http-management (instead of management).

@eed3si9n
Copy link
Contributor Author

@thomschke This PR is making the names consistent with Akka Management's doc. If the default value should be changed, I'd suggest you open issue under https://github.com/akka/akka-management. Also I am not sure if you do want the "management" port to take advantage of Istio's routing feature.

This creates labels for com.lightbend.rp.management-endpoint and com.lightbend.rp.remoting-endpoint, and changes the default names to `"management"` and `"remoting"`, following the convention set in Akka Management documentation.

Ref lightbend/reactive-cli#177
Create an instance of Config to pick up the port number for Play, Akka remoting, and Akka Management.
@eed3si9n eed3si9n changed the title (don't merge yet) create labels for endpoint names create labels for endpoint names Jan 25, 2019
@eed3si9n eed3si9n changed the title create labels for endpoint names create labels for endpoint names + probe application.conf for actual port assignments Jan 25, 2019
@eed3si9n eed3si9n merged commit 0bd5425 into lightbend:master Jan 25, 2019
@ghost ghost removed the review label Jan 25, 2019
@eed3si9n eed3si9n deleted the wip/endpoint branch January 25, 2019 17:56
eed3si9n added a commit to lightbend/reactive-cli that referenced this pull request Jan 29, 2019
Ref lightbend/reactive-lib#117
Ref lightbend/sbt-reactive-app#164

Since sbt-reactive-app captures the endpoint ports (such as port 9000), and because reactive-lib no longer attempts to override the ports for Play and Akka, the RP_ENDPOINT* environment variables are no longer necessary.
@eed3si9n eed3si9n added this to the 1.7.0 milestone Feb 5, 2019
eed3si9n added a commit that referenced this pull request Feb 14, 2019
#164 implemented endpoint port probing using Lightbend Config.
It turns out there's a seprate http endpoint creation going on for Lagom, which I missed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants