File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
content/en/docs/concepts/workloads/pods Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -75,7 +75,7 @@ Here are some ways to mitigate involuntary disruptions:
75
75
and [ stateful] ( /docs/tasks/run-application/run-replicated-stateful-application/ ) applications.)
76
76
- For even higher availability when running replicated applications,
77
77
spread applications across racks (using
78
- [ anti-affinity] ( /docs/user-guide/node-selection/#inter -pod-affinity-and-anti-affinity-beta-feature ) )
78
+ [ anti-affinity] ( /docs/concepts/scheduling-eviction/assign -pod-node/# affinity-and-anti-affinity ) )
79
79
or across zones (if using a
80
80
[ multi-zone cluster] ( /docs/setup/multiple-zones ) .)
81
81
@@ -104,7 +104,7 @@ ensure that the number of replicas serving load never falls below a certain
104
104
percentage of the total.
105
105
106
106
Cluster managers and hosting providers should use tools which
107
- respect PodDisruptionBudgets by calling the [ Eviction API] ( /docs/tasks/administer-cluster/safely-drain-node/#the- eviction-api )
107
+ respect PodDisruptionBudgets by calling the [ Eviction API] ( /docs/tasks/administer-cluster/safely-drain-node/#eviction-api )
108
108
instead of directly deleting pods or deployments.
109
109
110
110
For example, the ` kubectl drain ` subcommand lets you mark a node as going out of
You can’t perform that action at this time.
0 commit comments