From 2c85669fb9d61129668cb512d65c88e8da5abbde Mon Sep 17 00:00:00 2001 From: chenhuan12 Date: Wed, 30 Aug 2017 16:53:19 +0800 Subject: [PATCH] fix typo fix typo --- .../debug-application-cluster/logging-stackdriver.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/tasks/debug-application-cluster/logging-stackdriver.md b/docs/tasks/debug-application-cluster/logging-stackdriver.md index fb29b010cf..ccaba3ea08 100644 --- a/docs/tasks/debug-application-cluster/logging-stackdriver.md +++ b/docs/tasks/debug-application-cluster/logging-stackdriver.md @@ -53,7 +53,7 @@ Stackdriver Logging agents to the running cluster. that don't have fluentd pod allocated already. You can ensure that your node is labelled properly by running `kubectl describe` as follows: - ```shell + ``` kubectl describe node $NODE_NAME ``` @@ -69,7 +69,7 @@ Stackdriver Logging agents to the running cluster. Ensure that the output contains the label `beta.kubernetes.io/fluentd-ds-ready=true`. If it is not present, you can add it using the `kubectl label` command as follows: - ```shell + ``` kubectl label node $NODE_NAME beta.kubernetes.io/fluentd-ds-ready=true ``` @@ -79,7 +79,7 @@ Stackdriver Logging agents to the running cluster. 1. Deploy a `ConfigMap` with the logging agent configuration by running the following command: - ```shell + ``` kubectl create -f https://k8s.io/docs/tasks/debug-application-cluster/fluentd-gcp-configmap.yaml ``` @@ -88,7 +88,7 @@ Stackdriver Logging agents to the running cluster. 1. Deploy the logging agent `DaemonSet` by running the following command: - ```shell + ``` kubectl create -f https://k8s.io/docs/tasks/debug-application-cluster/fluentd-gcp-ds.yaml ```