Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix console outout of logging doc #11529

Merged
merged 1 commit into from
Jul 18, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/user-guide/logging.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ The logs of a running container may be fetched using the command `kubectl logs`.
this pod specification [counter-pod.yaml](../../examples/blog-logging/counter-pod.yaml), which has a container which writes out some text to standard
output every second. (You can find different pod specifications [here](logging-demo/).)

```
```yaml
apiVersion: v1
kind: Pod
metadata:
Expand All @@ -58,14 +58,14 @@ output every second. (You can find different pod specifications [here](logging-d

we can run the pod:

```
$ kubectl create -f ./counter-pod.yaml
pods/counter
```console
$ kubectl create -f ./counter-pod.yaml
pods/counter
```

and then fetch the logs:

```
```console
$ kubectl logs counter
0: Tue Jun 2 21:37:31 UTC 2015
1: Tue Jun 2 21:37:32 UTC 2015
Expand All @@ -79,7 +79,7 @@ $ kubectl logs counter
If a pod has more than one container then you need to specify which container's log files should
be fetched e.g.

```
```console
$ kubectl logs kube-dns-v3-7r1l9 etcd
2015/06/23 00:43:10 etcdserver: start to snapshot (applied: 30003, lastsnap: 20002)
2015/06/23 00:43:10 etcdserver: compacted log at index 30003
Expand Down