Zipking readiness probe 503

[EnolMG]

Describe the Bug

The pod don't start beacuse readines probe with error 503. I have configured elasticsearch env variables to connect to a elastic 8.2 cluster. The log ends with

2022-05-23 10:12:49.392  INFO 1 --- [           main] c.l.a.c.Flags                            : Using OpenSSL: BoringSSL, 0x1010007f
2022-05-23 10:12:50.678  INFO 1 --- [           main] c.l.a.s.d.DocStringExtractor             : Using com.linecorp.armeria.thrift.jsonDir: META-INF/armeria/thrift
2022-05-23 10:12:50.720  INFO 1 --- [           main] c.l.a.c.u.SystemInfo                     : Hostname: zipkin-server-75d9b5b4f8-mshps (from /proc/sys/kernel/hostname)
2022-05-23 10:12:51.133  INFO 1 --- [oss-http-*:9411] c.l.a.s.Server                           : Serving HTTP at /0.0.0.0:9411 - http://127.0.0.1:9411/
2022-05-23 10:12:51.138  INFO 1 --- [           main] c.l.a.s.ArmeriaAutoConfiguration         : Armeria server started at ports: {/0.0.0.0:9411=ServerPort(/0.0.0.0:9411, [http])}
2022-05-23 10:12:51.210  INFO 1 --- [           main] z.s.ZipkinServer                         : Started ZipkinServer in 6.383 seconds (JVM running for 8.539)
2022-05-23 10:16:09.208  INFO 1 --- [orker-epoll-2-1] c.l.a.i.JavaVersionSpecific              : Using the APIs optimized for: Java 9+

So I guess it starts correct but I can't see more errors to fix the problem.

I use this image version:
openzipkin/zipkin:2.17.1

[codefromthecrypt]

is this a problem with the helm chart? zipkin's docker healthcheck works or we would get broken CI.

[jcchavezs]

At some point we had an issue like this because zipkin was accepting https but the health endpoint is hard coded to do http. I can't find the issue tho, maybe it was on gitter.