Brief summary of the bug.

Optimize is crashing and not able to start. This is happening on DEV / INT and PROD of our managed SaaS offering. As discussed with helene.waechtler I create a ticket for this after showcasing.

API Readyz and /actuator/metrics issues

Both readiness and liveness probes fail.{}

Readiness probe failed: Get "http://10.65.51.3:8090/api/readyz": dial tcp 10.65.51.3:8090: connect: connection refused 

Liveness probe failed: dial tcp 10.65.51.3:8090: connect: connection refused

{{}}

This also happens when port-forwarding to the endpoints directly.

This happens on multiple version but however it seems to also sometimes work in some cases:

camunda/optimize:3.10.0-alpha2

camunda/optimize:3.10.0-alpha1

camunda/optimize:3.9.3

camunda/optimize:SNAPSHOT

Steps to reproduce:

1. Start Optimize
2. Try to curl /api/readyz or :8092/actutator

I can also showcase this in a call once more if needed. 

Actual result:

Either connection refused happens or redirect to <cluster-id>/sso/auth

curl localhost:8092/actuator/ -v

•   Trying 127.0.0.1:8092...
• Connected to localhost (127.0.0.1) port 8092 (#0)
  > GET /actuator/ HTTP/1.1
  > Host: localhost:8092
  > User-Agent: curl/7.85.0
  > Accept: /
  >
• Mark bundle as not supporting multiuse
  < HTTP/1.1 302 Found
  < Date: Fri, 06 Jan 2023 14:41:08 GMT
  < X-Content-Type-Options: nosniff
  < X-XSS-Protection: 1; mode=block
  < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
  < Pragma: no-cache
  < Expires: 0
  < X-Frame-Options: DENY
  < Location: http://localhost:8092/0b0b1f10-c43c-4277-9810-9945ec425534/sso/auth0
  < Content-Length: 0
  <
• Connection #0 to host localhost left intact

  Expected result:

Readiness endpoints work and actuator is accessible.