Fix line separation in concepts/architecture/nodes
This commit is contained in:
parent
c9f42c1389
commit
df3eabc37c
|
@ -237,6 +237,7 @@ responsible for:
|
||||||
- Evicting all the pods from the node using graceful termination if
|
- Evicting all the pods from the node using graceful termination if
|
||||||
the node continues to be unreachable. The default timeouts are 40s to start
|
the node continues to be unreachable. The default timeouts are 40s to start
|
||||||
reporting ConditionUnknown and 5m after that to start evicting pods.
|
reporting ConditionUnknown and 5m after that to start evicting pods.
|
||||||
|
|
||||||
The node controller checks the state of each node every `--node-monitor-period` seconds.
|
The node controller checks the state of each node every `--node-monitor-period` seconds.
|
||||||
|
|
||||||
#### Heartbeats
|
#### Heartbeats
|
||||||
|
@ -278,6 +279,7 @@ the same time:
|
||||||
`--large-cluster-size-threshold` nodes - default 50), then evictions are stopped.
|
`--large-cluster-size-threshold` nodes - default 50), then evictions are stopped.
|
||||||
- Otherwise, the eviction rate is reduced to `--secondary-node-eviction-rate`
|
- Otherwise, the eviction rate is reduced to `--secondary-node-eviction-rate`
|
||||||
(default 0.01) per second.
|
(default 0.01) per second.
|
||||||
|
|
||||||
The reason these policies are implemented per availability zone is because one
|
The reason these policies are implemented per availability zone is because one
|
||||||
availability zone might become partitioned from the master while the others remain
|
availability zone might become partitioned from the master while the others remain
|
||||||
connected. If your cluster does not span multiple cloud provider availability zones,
|
connected. If your cluster does not span multiple cloud provider availability zones,
|
||||||
|
|
Loading…
Reference in New Issue