Fix some typo in init-containers.md

Fixed a typo in manage-resources-containers.md (Kubelet → kubelet)
pull/25713/head
Ader 2020-12-19 14:13:40 +08:00 committed by GitHub
parent cb5d05e65b
commit 21c5750086
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -49,9 +49,9 @@ as documented in [Resources](#resources).
Also, init containers do not support `lifecycle`, `livenessProbe`, `readinessProbe`, or
`startupProbe` because they must run to completion before the Pod can be ready.
If you specify multiple init containers for a Pod, Kubelet runs each init
If you specify multiple init containers for a Pod, kubelet runs each init
container sequentially. Each init container must succeed before the next can run.
When all of the init containers have run to completion, Kubelet initializes
When all of the init containers have run to completion, kubelet initializes
the application containers for the Pod and runs them as usual.
## Using init containers