@@ -156,7 +156,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
156
156
157
157
## Summary
158
158
159
- This enhancement adds the ability for the container runtime to tell kubelet
159
+ This enhancement adds the ability for the container runtime to instruct kubelet
160
160
which cgroup driver to use. This removes the need for specifying cgroup driver
161
161
in the kubelet configuration and eliminates the possibility of misaligned
162
162
cgroup driver configuration between the kubelet and the runtime.
@@ -216,7 +216,7 @@ This might be a good place to talk about core concepts and how they relate.
216
216
### Risks and Mitigations
217
217
218
218
Field adoption could be considered a risk, though the CRI implementations work
219
- closely with SIG- Node and the feature will move along with CRI implementation
219
+ closely with SIG Node and the feature will move along with CRI implementation
220
220
adoption.
221
221
222
222
## Design Details
@@ -502,7 +502,7 @@ well as the [existing list] of feature gates.
502
502
[existing list]: https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/
503
503
-->
504
504
505
- No feature gate required–the fields are all SIG- Node internal and have simple
505
+ No feature gate required–the fields are all SIG Node internal and have simple
506
506
fallbacks.
507
507
508
508
###### Does enabling the feature change any default behavior?
@@ -877,7 +877,7 @@ Make kubelet the configuration point for cgroup driver so that kubelet would
877
877
inform the runtime which cgroup driver to use. This could be achieved e.g.
878
878
without any changes to the CRI API by the CRI implementation guessing the
879
879
cgroup driver based on the path of the CgroupParent of the pod, passed down in
880
- the RunPodSandboxRequest. However, SIG- Node has decided that the CRI
880
+ the RunPodSandboxRequest. However, SIG Node has decided that the CRI
881
881
implementation should begin to be the source of truth for low-level choices
882
882
like this, and thus this approach was chosen.
883
883
0 commit comments