I would like to configure Quarkus to exclude the health endpoint from mutual TLS (mTLS) so that Kubernetes can access it.
Is this possible that you set up a specific “route” in your application configuration to allow unauthenticated access to the health endpoint?

I have configured the application.properties like this:

# Server TLS
quarkus.http.insecure-requests=disabled
quarkus.http.ssl.certificate.key-store-file=tls/keystore.p12
quarkus.http.ssl.certificate.key-store-file-type=PKCS12
quarkus.http.ssl.certificate.key-store-password=123456

# Client certificate authentication
quarkus.http.ssl.client-auth=required
quarkus.http.ssl.certificate.trust-store-file=tls/truststore.p12
quarkus.http.ssl.certificate.trust-store-password=123456

I have disabled HTTP port 8080 and configured that only the mTLS is possible.
How should I configure/implement so that the health endpoint is reachable without only via TLS not mutual TLS validation.