You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TiDB Pod now has a Probe to probe TiDB Server's /status path. K8s Probe cannot send client certificate when requested. Now that TiDB Server has enabled TLS, TiDB Server has forced to verify the client certificate, so the Probe always failed to work.
Readiness probe failed: Get https://10.244.0.17:10080/status: remote error: tls: bad certificate
The text was updated successfully, but these errors were encountered:
However, tidb docker image does not contain curl and the builtin wget does not support specifying TLS certificates. So in order to use command to do health check, we may need to install curl in the tidb docker image.
TiDB Pod now has a Probe to probe TiDB Server's
/status
path. K8s Probe cannot send client certificate when requested. Now that TiDB Server has enabled TLS, TiDB Server has forced to verify the client certificate, so the Probe always failed to work.The text was updated successfully, but these errors were encountered: