fix(installer): restart coredns when change ip, raise cri timeout #942
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
this is a cherry pick of fix(installer): restart coredns when change ip, raise cri timeout #941
coredns also counts as a pod using host ip because the local network's gateway is often used as its upstream DNS server in the pod's
/etc/resolv.conf
, and it needs to be manually updated in case of a CIDR changethe default timeout period of CRI requests is
2m
in kubelet, and can time out during the middle of a normal operation like unpacking a large image on slow hardwares, we explicitly lift it to5m
to make it more tolerable.Target Version for Merge
1.11.4
Related Issues
none
PRs Involving Sub-Systems
fix: also restart coredns when changing IP Installer#142
fix: raise cri timeout to accommodate slow hardwares Installer#143
Other information:
none