mirror of
https://github.com/kubernetes/node-problem-detector.git
synced 2026-08-20 04:36:41 +00:00
dpacgdm
43702a7424
The health-checker binary honors --cri-timeout when passed via custom plugin rule args. The default containerd configs omitted the flag, so crictl used the 2s built-in default. Add --cri-timeout=10s to the sample Linux and Windows containerd configs. Signed-off-by: dpacgdm <dpac.gdm@gmail.com>
35 lines
804 B
JSON
35 lines
804 B
JSON
{
|
|
"plugin": "custom",
|
|
"pluginConfig": {
|
|
"invoke_interval": "10s",
|
|
"timeout": "3m",
|
|
"max_output_length": 80,
|
|
"concurrency": 1
|
|
},
|
|
"source": "health-checker",
|
|
"metricsReporting": true,
|
|
"conditions": [
|
|
{
|
|
"type": "ContainerRuntimeUnhealthy",
|
|
"reason": "ContainerRuntimeIsHealthy",
|
|
"message": "Container runtime on the node is functioning properly"
|
|
}
|
|
],
|
|
"rules": [
|
|
{
|
|
"type": "permanent",
|
|
"condition": "ContainerRuntimeUnhealthy",
|
|
"reason": "ContainerdUnhealthy",
|
|
"path": "/home/kubernetes/bin/health-checker",
|
|
"args": [
|
|
"--component=cri",
|
|
"--enable-repair=true",
|
|
"--cooldown-time=2m",
|
|
"--cri-timeout=10s",
|
|
"--health-check-timeout=60s"
|
|
],
|
|
"timeout": "3m"
|
|
}
|
|
]
|
|
}
|