Hello there,
I would like to rice a discussion about deprecation of legacy observability interface (KC_LEGACY_OBSERVABILITY_INTERFACE=true). I saw that this parameter was marked as deprecated in docs.

We use AWS ECS Service with ECS bridge network + ALB with a targets group. The bridge network is mapping Container ports on EC2 instance ports dynamically. To map ALB (target group) port on a ECS task port like 8080, we set up the container port (8080), container name, arn of a target group on ECS Service configuration. It allows us to create a flow:

Client -> ALB (443 port) -> Target group -> EC2 instance (dynamic port) -> ECS task -> Keycloak Container (8080 port)

ECS service makes all mapping magic behind of the scene. However, the target group makes health-check in all targets associated with it. To simplify everything, there is the magic in the configuration. We define traffic-port as a port health-check. And, the target-group uses allocated dynamic port for each target. There is another option to specify any port. But this port is a constant port, and we can't associate it with dynamically mapped port for management (9000 container port). In this case for us, the best way is to keep health-check on the main (8080) port. Yes we understand that it is an insecure option. However, we block /health /metric endpoints on the ALB side for our clients. And we are good again there =)

I understand that the main supporting tool for you is a Kubernets, but we don't see a migration from ECS to there in the nearest future.
So, could you please to continue support KC_LEGACY_OBSERVABILITY_INTERFACE option? Do you have an alternative for it?
Thank you.