Skip to content

Commit a66af45

Browse files
authored
Merge pull request #25871 from ydFu/patch-1
Add content in init-containers.md
2 parents 8260261 + 4ff57af commit a66af45

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

content/en/docs/concepts/workloads/pods/init-containers.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,7 @@ You can start this Pod by running:
133133
```shell
134134
kubectl apply -f myapp.yaml
135135
```
136+
The output is similar to this:
136137
```
137138
pod/myapp-pod created
138139
```
@@ -141,6 +142,7 @@ And check on its status with:
141142
```shell
142143
kubectl get -f myapp.yaml
143144
```
145+
The output is similar to this:
144146
```
145147
NAME READY STATUS RESTARTS AGE
146148
myapp-pod 0/1 Init:0/2 0 6m
@@ -150,6 +152,7 @@ or for more details:
150152
```shell
151153
kubectl describe -f myapp.yaml
152154
```
155+
The output is similar to this:
153156
```
154157
Name: myapp-pod
155158
Namespace: default
@@ -224,6 +227,7 @@ To create the `mydb` and `myservice` services:
224227
```shell
225228
kubectl apply -f services.yaml
226229
```
230+
The output is similar to this:
227231
```
228232
service/myservice created
229233
service/mydb created
@@ -235,6 +239,7 @@ Pod moves into the Running state:
235239
```shell
236240
kubectl get -f myapp.yaml
237241
```
242+
The output is similar to this:
238243
```
239244
NAME READY STATUS RESTARTS AGE
240245
myapp-pod 1/1 Running 0 9m
@@ -319,11 +324,9 @@ reasons:
319324

320325

321326

322-
323327
## {{% heading "whatsnext" %}}
324328

325329

326330
* Read about [creating a Pod that has an init container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container)
327331
* Learn how to [debug init containers](/docs/tasks/debug-application-cluster/debug-init-containers/)
328332

329-

0 commit comments

Comments
 (0)