Merge pull request #22510 from danielkucera/patch-1
fix example for PodTolerationRestriction annotation
This commit is contained in:
@@ -706,8 +706,8 @@ kind: Namespace
|
|||||||
metadata:
|
metadata:
|
||||||
name: apps-that-need-nodes-exclusively
|
name: apps-that-need-nodes-exclusively
|
||||||
annotations:
|
annotations:
|
||||||
scheduler.alpha.kubernetes.io/defaultTolerations: '{"operator": "Exists", "effect": "NoSchedule", "key": "dedicated-node"}'
|
scheduler.alpha.kubernetes.io/defaultTolerations: '[{"operator": "Exists", "effect": "NoSchedule", "key": "dedicated-node"}]'
|
||||||
scheduler.alpha.kubernetes.io/tolerationsWhitelist: '{"operator": "Exists", "effect": "NoSchedule", "key": "dedicated-node"}'
|
scheduler.alpha.kubernetes.io/tolerationsWhitelist: '[{"operator": "Exists", "effect": "NoSchedule", "key": "dedicated-node"}]'
|
||||||
```
|
```
|
||||||
|
|
||||||
### Priority {#priority}
|
### Priority {#priority}
|
||||||
@@ -793,4 +793,4 @@ phase, and therefore is the last admission controller to run.
|
|||||||
in the mutating phase.
|
in the mutating phase.
|
||||||
|
|
||||||
For earlier versions, there was no concept of validating versus mutating and the
|
For earlier versions, there was no concept of validating versus mutating and the
|
||||||
admission controllers ran in the exact order specified.
|
admission controllers ran in the exact order specified.
|
||||||
|
|||||||
Reference in New Issue
Block a user