# Node crash recovery To speed up node crash recovery process, edit kube-controller-manager pod: ```bash kubectl get -n kube-system pod | grep kube-controller-manager | cut -f1 -d ' ' | xargs kubectl edit -n kube-system pod ``` Add/edit the following parameters: * `--pod-eviction-timeout=30s` (default 5m0s) * `--node-monitor-period=2s` (default 5s) * `--node-monitor-grace-period=16s` (default 40s) * `--pod-eviction-timeout=30s` (default 5m) * `--node-status-update-frequency` And, of course, you can always have your deployments with replica 2 and service will be up even if one node goes down. ### References --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.devops.buzz/public/kubernetes/kube-controller-manager/node-crash-recovery.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.