Skip to content

Commit 8949fe3

Browse files
authored
Merge pull request kubernetes#1421 from yuzhiquan/patch-typo
cleanup(enhancements): typo
2 parents 54ff1aa + 5119121 commit 8949fe3

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

keps/sig-node/0009-node-heartbeat.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -283,7 +283,7 @@ both real clusters and Kubemark.
283283
GA:
284284
- Enabled by default for a release with no complaints.
285285
- Frequency of NodeStatus defaulted to 5m
286-
- kubectl describe node showing information from corrsponding Lease object
286+
- kubectl describe node showing information from corresponding Lease object
287287

288288

289289
## Implementation History

keps/sig-node/20190129-pid-limiting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,4 +189,4 @@ GA
189189
### Version 1.15
190190

191191
- Graduate `SupportNodePidsLimit` to beta by adding node e2e test
192-
coverage for node cgrop isoation.
192+
coverage for node cgroup isoation.

keps/sig-node/20190131-runas-groupid.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@ Note that this change does not introduce an equivalent field called runAsNonRoot
228228
and PodSecurityContext. There was ongoing discussion about this field at PR [#62216](https://github.com/kubernetes/kubernetes/pull/62217)
229229
The summary of this discussion seems as follows:-
230230
- Use PSP MustRunAs Group strategy to guarantee that Pod never runs with 0 as Primary Group ID.
231-
- Using the PSP MustRunaAs Group strategy forces Pod to always specify a RunAsGroup
231+
- Using the PSP MustRunAs Group strategy forces Pod to always specify a RunAsGroup
232232
- RunAsGroup field when specified in PodSpec, will always override USER field in Dockerfile
233233

234234
There are other potentially unresolved discussions in that PR which need a followup.

0 commit comments

Comments
 (0)