Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
Kubespray
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Model registry
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Mirror
Kubespray
Commits
8f5b0c77
Unverified
Commit
8f5b0c77
authored
6 years ago
by
Rong Zhang
Committed by
GitHub
6 years ago
Browse files
Options
Downloads
Plain Diff
Merge pull request #3345 from mirake/fix-typos
Fix some typos
parents
3d270077
0dd82293
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/kubernetes-reliability.md
+2
-2
2 additions, 2 deletions
docs/kubernetes-reliability.md
with
2 additions
and
2 deletions
docs/kubernetes-reliability.md
+
2
−
2
View file @
8f5b0c77
...
@@ -69,7 +69,7 @@ minute which may require large etcd containers or even dedicated nodes for etcd.
...
@@ -69,7 +69,7 @@ minute which may require large etcd containers or even dedicated nodes for etcd.
> If we calculate the number of tries, the division will give 5, but in reality
> If we calculate the number of tries, the division will give 5, but in reality
> it will be from 3 to 5 with `nodeStatusUpdateRetry` attempts of each try. The
> it will be from 3 to 5 with `nodeStatusUpdateRetry` attempts of each try. The
> total number of attem
t
ps will vary from 15 to 25 due to latency of all
> total number of attemp
t
s will vary from 15 to 25 due to latency of all
> components.
> components.
## Medium Update and Average Reaction
## Medium Update and Average Reaction
...
@@ -92,7 +92,7 @@ etcd updates per minute.
...
@@ -92,7 +92,7 @@ etcd updates per minute.
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
`--pod-eviction-timeout`
`--node-monitor-grace-period`
will set to
**5m**
and
`--pod-eviction-timeout`
to
**1m**
. In this scenario, every kubelet will try to update the status every
to
**1m**
. In this scenario, every kubelet will try to update the status every
minute. There will be 5
*
5 = 25 attempts before unhealty status. After 5m,
minute. There will be 5
*
5 = 25 attempts before unhealt
h
y status. After 5m,
Kubernetes controller manager will set unhealthy status. This means that pods
Kubernetes controller manager will set unhealthy status. This means that pods
will be evicted after 1m after being marked unhealthy. (6m in total).
will be evicted after 1m after being marked unhealthy. (6m in total).
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment