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

docs: fix some typos (#5618)

Browse source 
Although it is spelling mistakes, it might make affect while reading.

Signed-off-by: Nguyen Hai Truong <truongnh@vn.fujitsu.com>
This commit is contained in:
Nguyen Hai Truong 2020-02-26 19:46:28 +07:00 committed by GitHub
parent d2c44dd4df
commit c6170eb79d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/comparisons.md
View file

@ -1,4 +1,4 @@
# Comparaison # Comparison
## Kubespray vs [Kops](https://github.com/kubernetes/kops) ## Kubespray vs [Kops](https://github.com/kubernetes/kops)

4
docs/kubernetes-reliability.md
View file

@ -12,14 +12,14 @@ By default the normal behavior looks like:
1. Kubelet updates it status to apiserver periodically, as specified by 1. Kubelet updates it status to apiserver periodically, as specified by
`--node-status-update-frequency`. The default value is **10s**. `--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**. `–-node-monitor-period`. The default value is **5s**.
3. In case the status is updated within `--node-monitor-grace-period` of time, 3. In case the status is updated within `--node-monitor-grace-period` of time,
Kubernetes controller manager considers healthy status of Kubelet. The Kubernetes controller manager considers healthy status of Kubelet. The
default value is **40s**. 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, > 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 > 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 > `--node-status-update-frequency` is set to 5s in reality it may appear in