/usr/bin/health-checker

Usage of /usr/bin/health-checker:
      --component string                The component to check health for. Supports kubelet, docker, kube-proxy, and cri (default "kubelet")
      --cooldown-time duration          The duration to wait for the service to be up before attempting repair. (default 2m0s)
      --cri-socket-path string          The path to the cri socket. Used with crictl to specify the socket path. (default "unix:///var/run/containerd/containerd.sock")
      --cri-timeout duration            The duration to wait for crictl to run. (default 2s)
      --crictl-path string              The path to the crictl binary. This is used to check health of cri component. (default "/usr/bin/crictl")
      --enable-repair                   Flag to enable/disable repair attempt for the component. (default true)
      --health-check-timeout duration   The time to wait before marking the component as unhealthy. (default 10s)
      --log-pattern logPatternFlag      The log pattern to look for in service journald logs. The format for flag value <failureThresholdCount>:<logPattern>
      --loopback-time duration          The duration to loop back, if it is 0, health-check will check from start time.
      --service string                  The underlying service responsible for the component. Set to the corresponding component for docker and kubelet, containerd for cri.
  -v, --v Level                         number for the log level verbosity