Steeltoe icon indicating copy to clipboard operation
Steeltoe copied to clipboard

Actuator Endpoints should listen on a different port than application port

Open hananiel opened this issue 5 years ago • 2 comments

Support listening to actuators on a separate port than Application port.

hananiel avatar Jun 29 '20 15:06 hananiel

This is already possible through the Action<IEndpointConventionBuilder> arg that is available on several extensions or by adding the startup filter more directly:

services.AddSingleton<IStartupFilter>(new AllActuatorsStartupFilter(c => c.RequireHost("*:5010")));

When we address this item, see about making it a config entry and update the documentation to include this approach regardless of the "best" option in 4.0 so it's clear how to do it in 3.x

TimHess avatar Aug 15 '22 19:08 TimHess

We need to have the webserver also configured to listen on the port and then we can add a restriction on the particular endpoints as this convention is doing. And we also have to add a convention to all others to not listen on the "management host/port"

hananiel avatar Sep 07 '22 22:09 hananiel

Can AddAllActuators should detect kubernetes and expose actuators on additional port?

hananiel avatar Oct 10 '22 19:10 hananiel