Fixed wrong value in exmaple (#9278)
`zk-hs` should be just `zk` in this case.
This commit is contained in:
@@ -848,13 +848,13 @@ This is because the Pods in the `zk` `StatefulSet` have a `PodAntiAffinity` spec
|
|||||||
- key: "app"
|
- key: "app"
|
||||||
operator: In
|
operator: In
|
||||||
values:
|
values:
|
||||||
- zk-hs
|
- zk
|
||||||
topologyKey: "kubernetes.io/hostname"
|
topologyKey: "kubernetes.io/hostname"
|
||||||
```
|
```
|
||||||
|
|
||||||
The `requiredDuringSchedulingIgnoredDuringExecution` field tells the
|
The `requiredDuringSchedulingIgnoredDuringExecution` field tells the
|
||||||
Kubernetes Scheduler that it should never co-locate two Pods from the `zk-hs`
|
Kubernetes Scheduler that it should never co-locate two Pods which have `app` label
|
||||||
Service in the domain defined by the `topologyKey`. The `topologyKey`
|
as `zk` in the domain defined by the `topologyKey`. The `topologyKey`
|
||||||
`kubernetes.io/hostname` indicates that the domain is an individual node. Using
|
`kubernetes.io/hostname` indicates that the domain is an individual node. Using
|
||||||
different rules, labels, and selectors, you can extend this technique to spread
|
different rules, labels, and selectors, you can extend this technique to spread
|
||||||
your ensemble across physical, network, and power failure domains.
|
your ensemble across physical, network, and power failure domains.
|
||||||
|
|||||||
Reference in New Issue
Block a user