Ignasi Marimon-Clos

@AlexLaviolette thanks for the super-thorough explanations and tests. If you could provide a reproducer it'd be a great help to narrow down the issue.

> @ignasi35 Looks like this issue should be transferred to [playframework/play-ws](https://github.com/playframework/play-ws) I agree, let me handle it.

Update: - https://doc.akka.io/docs/akka-management/current/bootstrap/kubernetes-api.html lists the 2552 port - https://doc.akka.io/docs/akka-management/current/kubernetes-deployment/preparing-for-production.html#deployment-spec doesn't list it

The [general recommendation](https://github.com/akka/akka-http/issues/1210) wrt lifecycle management was for libraries (like Akka Management) to document recommended ways to handle the shutdown without actually doing the actual task registration. This leaves users...

> It could be configurable - enable/disable with `off` by default. I think this is counterintuitive. IMHO, having a coherent approach to lifecycle management in all libraries of the ecosystem...

Again in https://travis-ci.com/github/akka/akka-management/jobs/489782209

Hopefully fixed in #859

and again https://travis-ci.com/github/akka/akka-management/jobs/488837960#L2710

https://travis-ci.com/github/akka/akka-management/jobs/486154778#L5907

Again https://travis-ci.com/github/akka/akka-management/jobs/486017783#L6071 ``` [info] - when calling GET /cluster/domain-events *** FAILED *** (770 milliseconds) [info] A timeout occurred waiting for a future to complete. Waited 150 milliseconds. (ClusterHttpManagementRoutesSpec.scala:449) [info] org.scalatest.concurrent.ScalaFutures$$anon$1$$anon$2:...