diff --git a/serving/setting-up-a-logging-plugin.md b/serving/setting-up-a-logging-plugin.md
index 111a2a19f..0de828660 100644
--- a/serving/setting-up-a-logging-plugin.md
+++ b/serving/setting-up-a-logging-plugin.md
@@ -56,12 +56,8 @@ is in process to get rid of the sidecar. The steps to configure are:
 Operators need to deploy Knative components after the configuring:
 
 ```shell
-# In case there is no change with the controller code
-bazel run config:controller.delete
 # Deploy the configuration for sidecar
 kubectl apply --filename config/config-observability.yaml
-# Deploy the controller to make configuration for sidecar take effect
-bazel run config:controller.apply
 
 # Deploy the DaemonSet to make configuration for DaemonSet take effect
 kubectl apply --filename <the-fluentd-config-for-daemonset> \
@@ -73,6 +69,10 @@ kubectl apply --filename <the-fluentd-config-for-daemonset> \
 In the commands above, replace `<the-fluentd-config-for-daemonset>` with the
 Fluentd DaemonSet configuration file, e.g. `config/monitoring/150-stackdriver`.
 
+**NOTE**: The deployment above will not affect the fluentd sidecar of existing
+pods. Developers need to redeploy their app to get the newest configuration for
+the fluentd sidecar used to send logs to `/var/log`.
+
 **NOTE**: Operators sometimes need to deploy extra services as the logging
 backends. For example, if they desire Elasticsearch&Kibana, they have to deploy
 the Elasticsearch and Kibana services. Knative provides this sample: