Skip to content

Commit

Permalink
fix topology zone list value quote issue in docs
Browse files Browse the repository at this point in the history
  • Loading branch information
bingchenli committed Mar 8, 2024
1 parent 108bdf5 commit 9f73e39
Show file tree
Hide file tree
Showing 6 changed files with 18 additions and 18 deletions.
6 changes: 3 additions & 3 deletions website/content/en/docs/concepts/scheduling.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ All examples below assume that the NodePool doesn't have constraints to prevent
- matchExpressions:
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2b"]
Expand All @@ -225,7 +225,7 @@ Changing the second operator to `NotIn` would allow the pod to run in `us-west-2
```yaml
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "NotIn"
values: ["us-west-2b"]
Expand All @@ -243,7 +243,7 @@ Here, if `us-west-2a` is not available, the second term will cause the pod to ru
- matchExpressions: # OR
- key: "topology.kubernetes.io/zone" # AND
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone" # AND
operator: "NotIn"
values: ["us-west-2b"]
Expand Down
6 changes: 3 additions & 3 deletions website/content/en/preview/concepts/scheduling.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ All examples below assume that the NodePool doesn't have constraints to prevent
- matchExpressions:
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2b"]
Expand All @@ -226,7 +226,7 @@ Changing the second operator to `NotIn` would allow the pod to run in `us-west-2
```yaml
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "NotIn"
values: ["us-west-2b"]
Expand All @@ -244,7 +244,7 @@ Here, if `us-west-2a` is not available, the second term will cause the pod to ru
- matchExpressions: # OR
- key: "topology.kubernetes.io/zone" # AND
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone" # AND
operator: "NotIn"
values: ["us-west-2b"]
Expand Down
6 changes: 3 additions & 3 deletions website/content/en/v0.32/concepts/scheduling.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -213,7 +213,7 @@ All examples below assume that the NodePool doesn't have constraints to prevent
- matchExpressions:
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2b"]
Expand All @@ -224,7 +224,7 @@ Changing the second operator to `NotIn` would allow the pod to run in `us-west-2
```yaml
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "NotIn"
values: ["us-west-2b"]
Expand All @@ -242,7 +242,7 @@ Here, if `us-west-2a` is not available, the second term will cause the pod to ru
- matchExpressions: # OR
- key: "topology.kubernetes.io/zone" # AND
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone" # AND
operator: "NotIn"
values: ["us-west-2b"]
Expand Down
6 changes: 3 additions & 3 deletions website/content/en/v0.33/concepts/scheduling.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ All examples below assume that the NodePool doesn't have constraints to prevent
- matchExpressions:
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2b"]
Expand All @@ -225,7 +225,7 @@ Changing the second operator to `NotIn` would allow the pod to run in `us-west-2
```yaml
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "NotIn"
values: ["us-west-2b"]
Expand All @@ -243,7 +243,7 @@ Here, if `us-west-2a` is not available, the second term will cause the pod to ru
- matchExpressions: # OR
- key: "topology.kubernetes.io/zone" # AND
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone" # AND
operator: "NotIn"
values: ["us-west-2b"]
Expand Down
6 changes: 3 additions & 3 deletions website/content/en/v0.34/concepts/scheduling.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ All examples below assume that the NodePool doesn't have constraints to prevent
- matchExpressions:
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2b"]
Expand All @@ -225,7 +225,7 @@ Changing the second operator to `NotIn` would allow the pod to run in `us-west-2
```yaml
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "NotIn"
values: ["us-west-2b"]
Expand All @@ -243,7 +243,7 @@ Here, if `us-west-2a` is not available, the second term will cause the pod to ru
- matchExpressions: # OR
- key: "topology.kubernetes.io/zone" # AND
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone" # AND
operator: "NotIn"
values: ["us-west-2b"]
Expand Down
6 changes: 3 additions & 3 deletions website/content/en/v0.35/concepts/scheduling.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ All examples below assume that the NodePool doesn't have constraints to prevent
- matchExpressions:
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2b"]
Expand All @@ -225,7 +225,7 @@ Changing the second operator to `NotIn` would allow the pod to run in `us-west-2
```yaml
- key: "topology.kubernetes.io/zone"
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone"
operator: "NotIn"
values: ["us-west-2b"]
Expand All @@ -243,7 +243,7 @@ Here, if `us-west-2a` is not available, the second term will cause the pod to ru
- matchExpressions: # OR
- key: "topology.kubernetes.io/zone" # AND
operator: "In"
values: ["us-west-2a, us-west-2b"]
values: ["us-west-2a", "us-west-2b"]
- key: "topology.kubernetes.io/zone" # AND
operator: "NotIn"
values: ["us-west-2b"]
Expand Down

0 comments on commit 9f73e39

Please sign in to comment.