Health check timeout against standalone tiger proxy in mesh setup

[achelos-lrz]

Hello Tiger Team,

we want to integrate a Tiger proxy in standalone mode with the mesh setup (https://gematik.github.io/app-Tiger/Tiger-User-Manual.html#_mesh_setup_traffic_endpoints)

We defined

tigerProxy:
    proxyId: IBM
    trafficEndpoints:
      - http://another.tiger.proxy:<adminPort>

as documented (of course with our domain names and configured ports) but after starting the test suite the health check for the configured traffic endpoint throws a timeout error.

It appears that the test suite performs a health check against http://another.tiger.proxy:<admin-port>/actuator/health but this endpoint does not exist (verified via curl, returns a 404 status code and according response body).
If I understood the code correctly the health check for the mesh integration of external tiger proxies is performed in de.gematik.test.tiger.proxy.AbstractTigerProxy#isGivenTigerProxyHealthy and uses a hardcoded "/actuator/health" path suffix.

Could you give us some direction where our setup configuration might be wrong or could you verify that there is an actual problem when integrating an external standalone tiger proxy?

Kind regards
Lukas