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
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
Kubernetes livenessProbe and readinessProbe cause that ubiquity container logs errors every readinessProbe period (default 5 secs). Probes are defined as default as:
readinessProbe:
tcpSocket:
port: 9999
Probes make these lines in ubiquity pod log:
2019/04/18 10:48:18 http: TLS handshake error from 172.28.112.162:48322: EOF
2019/04/18 10:48:23 http: TLS handshake error from 172.28.112.162:48334: EOF
2019/04/18 10:48:28 http: TLS handshake error from 172.28.112.162:48368: EOF
2019/04/18 10:48:33 http: TLS handshake error from 172.28.112.162:48380: EOF
2019/04/18 10:48:35 http: TLS handshake error from 172.28.112.162:48392: EOF
2019/04/18 10:48:38 http: TLS handshake error from 172.28.112.162:48414: EOF
...
Similarly probes cause errors in ubiquity-db pod log every 2 second:
Kubernetes livenessProbe and readinessProbe cause that ubiquity container logs errors every readinessProbe period (default 5 secs). Probes are defined as default as:
Probes make these lines in ubiquity pod log:
Similarly probes cause errors in ubiquity-db pod log every 2 second:
The text was updated successfully, but these errors were encountered: