title: Kubernetes readiness Probe exec KO, liveness Probe same exec OK
body: <p>I have configured a readinessProbe on my pod with a binary execution check, which connects to my running server (in the same container) and retrieves some health information (like ready for traffic).</p>
  
  <p>Configured as a readinessProbe, the binary fails to contact my server and get the required info. It connects on a TCP socket.
  But it works correctly when I configured it as a livenessProbe.</p>
  
  <p>Configuration. To make it work, I only changed the type from readinessProbe to livenessProbe.</p>
  
  <pre><code>"readinessProbe": {
                "exec": {
                  "command": [
                    "/opt/bin/ready_probe",
                    "--check_ready_traffic",
                    "--service=myServer-service"
                  ]
                },
                "initialDelaySeconds": 60,
                "timeoutSeconds": 5
              },
  </code></pre>
  
  <p>The service is for the server, to register it's host and port. This is OK.</p>
  
  <p>Version used: kubernetes v1.1.0-origin-1107-g4c8e6f4</p>
  
  <p>Thank you.</p>