github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-02 16:29:21 +00:00
Code Issues Projects Releases Wiki Activity

Fix output formatting for Getting Into Containers doc

Browse Source
This commit is contained in:
Satnam Singh 2015-07-19 00:13:42 +01:00
parent 715f2c488f
commit ece25d03a7
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/user-guide/getting-into-containers.md
View File

@ -40,14 +40,14 @@ Kubernetes exposes [services](services.md#environment-variables) through environ
We first create a pod and a service, We first create a pod and a service,
``` ```console
$ kubectl create -f examples/guestbook/redis-master-controller.yaml $ kubectl create -f examples/guestbook/redis-master-controller.yaml
$ kubectl create -f examples/guestbook/redis-master-service.yaml $ kubectl create -f examples/guestbook/redis-master-service.yaml
``` ```
wait until the pod is Running and Ready, wait until the pod is Running and Ready,
``` ```console
$ kubectl get pod $ kubectl get pod
NAME READY REASON RESTARTS AGE NAME READY REASON RESTARTS AGE
redis-master-ft9ex 1/1 Running 0 12s redis-master-ft9ex 1/1 Running 0 12s
@ -55,7 +55,7 @@ redis-master-ft9ex 1/1 Running 0 12s
then we can check the environment variables of the pod, then we can check the environment variables of the pod,
``` ```console
$ kubectl exec redis-master-ft9ex env $ kubectl exec redis-master-ft9ex env
... ...
REDIS_MASTER_SERVICE_PORT=6379 REDIS_MASTER_SERVICE_PORT=6379
@ -71,13 +71,13 @@ We can use these environment variables in applications to find the service.
It is convenient to use `kubectl exec` to check if the volumes are mounted as expected. It is convenient to use `kubectl exec` to check if the volumes are mounted as expected.
We first create a Pod with a volume mounted at /data/redis, We first create a Pod with a volume mounted at /data/redis,
``` ```console
kubectl create -f docs/user-guide/walkthrough/pod-redis.yaml kubectl create -f docs/user-guide/walkthrough/pod-redis.yaml
``` ```
wait until the pod is Running and Ready, wait until the pod is Running and Ready,
``` ```console
$ kubectl get pods $ kubectl get pods
NAME READY REASON RESTARTS AGE NAME READY REASON RESTARTS AGE
storage 1/1 Running 0 1m storage 1/1 Running 0 1m
@ -85,7 +85,7 @@ storage 1/1 Running 0 1m
we then use `kubectl exec` to verify that the volume is mounted at /data/redis, we then use `kubectl exec` to verify that the volume is mounted at /data/redis,
``` ```console
$ kubectl exec storage ls /data $ kubectl exec storage ls /data
redis redis
``` ```
@ -94,7 +94,7 @@ redis
After all, open a terminal in a pod is the most direct way to introspect the pod. Assuming the pod/storage is still running, run After all, open a terminal in a pod is the most direct way to introspect the pod. Assuming the pod/storage is still running, run
``` ```console
$ kubectl exec -ti storage -- bash $ kubectl exec -ti storage -- bash
root@storage:/data# root@storage:/data#
``` ```