Skip to content

Commit

Permalink
Fix issues in configure-volume-storage
Browse files Browse the repository at this point in the history
* ps command not found
* wrong code format

Signed-off-by: Jamie Zhuang <lanchongyizu@gmail.com>
  • Loading branch information
lanchongyizu committed Jul 15, 2018
1 parent e8d351b commit 9de0c3c
Showing 1 changed file with 20 additions and 18 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -37,51 +37,53 @@ restarts. Here is the configuration file for the Pod:

1. Create the Pod:

kubectl create -f https://k8s.io/examples/pods/storage/redis.yaml
kubectl create -f https://k8s.io/examples/pods/storage/redis.yaml

1. Verify that the Pod's Container is running, and then watch for changes to
the Pod:

kubectl get pod redis --watch
kubectl get pod redis --watch

The output looks like this:

NAME READY STATUS RESTARTS AGE
redis 1/1 Running 0 13s
NAME READY STATUS RESTARTS AGE
redis 1/1 Running 0 13s

1. In another terminal, get a shell to the running Container:

kubectl exec -it redis -- /bin/bash
kubectl exec -it redis -- /bin/bash

1. In your shell, go to `/data/redis`, and create a file:

root@redis:/data# cd /data/redis/
root@redis:/data/redis# echo Hello > test-file
root@redis:/data# cd /data/redis/
root@redis:/data/redis# echo Hello > test-file

1. In your shell, list the running processes:

root@redis:/data/redis# ps aux
root@redis:/data/redis# apt-get update
root@redis:/data/redis# apt-get install procps
root@redis:/data/redis# ps aux

The output is similar to this:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
redis 1 0.1 0.1 33308 3828 ? Ssl 00:46 0:00 redis-server *:6379
root 12 0.0 0.0 20228 3020 ? Ss 00:47 0:00 /bin/bash
root 15 0.0 0.0 17500 2072 ? R+ 00:48 0:00 ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
redis 1 0.1 0.1 33308 3828 ? Ssl 00:46 0:00 redis-server *:6379
root 12 0.0 0.0 20228 3020 ? Ss 00:47 0:00 /bin/bash
root 15 0.0 0.0 17500 2072 ? R+ 00:48 0:00 ps aux

1. In your shell, kill the redis process:

root@redis:/data/redis# kill <pid>
root@redis:/data/redis# kill <pid>

where `<pid>` is the redis process ID (PID).

1. In your original terminal, watch for changes to the redis Pod. Eventually,
you will see something like this:

NAME READY STATUS RESTARTS AGE
redis 1/1 Running 0 13s
redis 0/1 Completed 0 6m
redis 1/1 Running 1 6m
NAME READY STATUS RESTARTS AGE
redis 1/1 Running 0 13s
redis 0/1 Completed 0 6m
redis 1/1 Running 1 6m

At this point, the Container has terminated and restarted. This is because the
redis Pod has a
Expand All @@ -90,7 +92,7 @@ of `Always`.

1. Get a shell into the restarted Container:

kubectl exec -it redis -- /bin/bash
kubectl exec -it redis -- /bin/bash

1. In your shell, goto `/data/redis`, and verify that `test-file` is still there.

Expand Down

0 comments on commit 9de0c3c

Please sign in to comment.