Browse Source
docs: fix some typos (#5618)
Although it is spelling mistakes, it might make affect while reading.
Signed-off-by: Nguyen Hai Truong <truongnh@vn.fujitsu.com>
pull/5575/head
Nguyen Hai Truong
4 years ago
committed by
GitHub
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with
3 additions and
3 deletions
-
docs/comparisons.md
-
docs/kubernetes-reliability.md
|
|
|
@ -1,4 +1,4 @@ |
|
|
|
# Comparaison |
|
|
|
# Comparison |
|
|
|
|
|
|
|
## Kubespray vs [Kops](https://github.com/kubernetes/kops) |
|
|
|
|
|
|
|
|
|
|
|
@ -12,14 +12,14 @@ By default the normal behavior looks like: |
|
|
|
1. Kubelet updates it status to apiserver periodically, as specified by |
|
|
|
`--node-status-update-frequency`. The default value is **10s**. |
|
|
|
|
|
|
|
2. Kubernetes controller manager checks the statuses of Kubelets every |
|
|
|
2. Kubernetes controller manager checks the statuses of Kubelet every |
|
|
|
`–-node-monitor-period`. The default value is **5s**. |
|
|
|
|
|
|
|
3. In case the status is updated within `--node-monitor-grace-period` of time, |
|
|
|
Kubernetes controller manager considers healthy status of Kubelet. The |
|
|
|
default value is **40s**. |
|
|
|
|
|
|
|
> Kubernetes controller manager and Kubelets work asynchronously. It means that |
|
|
|
> Kubernetes controller manager and Kubelet work asynchronously. It means that |
|
|
|
> the delay may include any network latency, API Server latency, etcd latency, |
|
|
|
> latency caused by load on one's master nodes and so on. So if |
|
|
|
> `--node-status-update-frequency` is set to 5s in reality it may appear in |
|
|
|
|
