C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update kubernetes-reliability.md (#7724)

Browse source 
It's a minor change, I just corrected `–` char to `-`.
This commit is contained in:
Hamed Bahadorzadeh 2021-06-21 22:06:51 +04:30 committed by GitHub
parent a31baf3c16
commit 271be92b02
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/kubernetes-reliability.md
View file

@ -56,7 +56,7 @@ services so pods from failed node won't be accessible anymore.
## Fast Update and Fast Reaction
If `-–node-status-update-frequency` is set to **4s** (10s is default).
If `--node-status-update-frequency` is set to **4s** (10s is default).
`--node-monitor-period` to **2s** (5s is default).
`--node-monitor-grace-period` to **20s** (40s is default).
`--default-not-ready-toleration-seconds` and ``--default-unreachable-toleration-seconds`` are set to **30**
@ -78,7 +78,7 @@ minute which may require large etcd containers or even dedicated nodes for etcd.
## Medium Update and Average Reaction
Let's set `-–node-status-update-frequency` to **20s**
Let's set `--node-status-update-frequency` to **20s**
`--node-monitor-grace-period` to **2m** and `--default-not-ready-toleration-seconds` and
``--default-unreachable-toleration-seconds`` to **60**.
In that case, Kubelet will try to update status every 20s. So, it will be 6 * 5
@ -94,7 +94,7 @@ etcd updates per minute.
## Low Update and Slow reaction
Let's set `-–node-status-update-frequency` to **1m**.
Let's set `--node-status-update-frequency` to **1m**.
`--node-monitor-grace-period` will set to **5m** and `--default-not-ready-toleration-seconds` and
``--default-unreachable-toleration-seconds`` to **60**. In this scenario, every kubelet will try to update the status
every minute. There will be 5 * 5 = 25 attempts before unhealthy status. After 5m,