From 69668365ce0a0dc382d33d14612dc6d416465bc3 Mon Sep 17 00:00:00 2001 From: Satnam Singh Date: Sat, 18 Jul 2015 22:47:42 +0100 Subject: [PATCH] Update sidecar logging console output in docs --- contrib/logging/fluentd-sidecar-es/README.md | 4 ++-- contrib/logging/fluentd-sidecar-gcp/README.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/contrib/logging/fluentd-sidecar-es/README.md b/contrib/logging/fluentd-sidecar-es/README.md index b7073dc6686..3802355e0ee 100644 --- a/contrib/logging/fluentd-sidecar-es/README.md +++ b/contrib/logging/fluentd-sidecar-es/README.md @@ -15,12 +15,12 @@ In order to make this work, you have to add a few things to your pod config: 4. The `FILES_TO_COLLECT` environment variable in the sidecar container, telling it which files to collect logs from. These paths should always be in the mounted volume. To try it out, make sure that your cluster was set up to log to Elasticsearch when it was created (i.e. you set `LOGGING_DESTINATION=elasticsearch`), then simply run -``` +```console kubectl create -f logging-sidecar-pod.yaml ``` You should see the logs show up in the cluster's Kibana log viewer shortly after creating the pod. To clean up after yourself, simply run -``` +```console kubectl delete -f logging-sidecar-pod.yaml ``` diff --git a/contrib/logging/fluentd-sidecar-gcp/README.md b/contrib/logging/fluentd-sidecar-gcp/README.md index 578062675b2..0c500a7003c 100644 --- a/contrib/logging/fluentd-sidecar-gcp/README.md +++ b/contrib/logging/fluentd-sidecar-gcp/README.md @@ -15,12 +15,12 @@ In order to make this work, you have to add a few things to your pod config: 4. The `FILES_TO_COLLECT` environment variable in the sidecar container, telling it which files to collect logs from. These paths should always be in the mounted volume. To try it out, make sure that your cluster was set up to log to Google Cloud Logging when it was created (i.e. you set `LOGGING_DESTINATION=gcp` or are running on Container Engine), then simply run -``` +```console kubectl create -f logging-sidecar-pod.yaml ``` You should see the logs show up in the log viewer of the Google Developer Console shortly after creating the pod. To clean up after yourself, simply run -``` +```console kubectl delete -f logging-sidecar-pod.yaml ```