I have exec'd into a running container to see why it is never in a ready state, after seeing the following in the result of a describe in k8s:
Warning Unhealthy 79s (x10 over 2m3s) kubelet Readiness probe failed: failed to ping localhost:25565 : could not connect to Minecraft server: dial tcp [::1]:25565: connect: connection refused
Warning Unhealthy 28s (x11 over 73s) kubelet Readiness probe failed: failed to ping localhost:25565 : EOF
After getting into the container, I can see that the minecraft server is running as the port is being listened to properly, but this binary always fails to connect.
I have exec'd into a running container to see why it is never in a ready state, after seeing the following in the result of a
describe
in k8s:After getting into the container, I can see that the minecraft server is running as the port is being listened to properly, but this binary always fails to connect.