Consolidate YAML files [part-15] (#9380)

This is the last PR for moving the YAML/JSON sample files. There still
need some follow up PRs to:
- rename the `codenew` shortcode to `code`.
- move the examples_test.go to where it really belongs.

content/en/docs/concepts/cluster-administration/logging.md

@@ -160,7 +160,7 @@ Consider the following example. A pod runs a single container, and the container
 writes to two different log files, using two different formats. Here's a
 configuration file for the Pod:
 
-{{< code file="two-files-counter-pod.yaml" >}}
+{{< codenew file="admin/logging/two-files-counter-pod.yaml" >}}
 
 It would be a mess to have log entries of different formats in the same log
 stream, even if you managed to redirect both components to the `stdout` stream of
@@ -170,7 +170,7 @@ the logs to its own `stdout` stream.
 
 Here's a configuration file for a pod that has two sidecar containers:
 
-{{< code file="two-files-counter-pod-streaming-sidecar.yaml" >}}
+{{< codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" >}}
 
 Now when you run this pod, you can access each log stream separately by
 running the following commands:
@@ -226,7 +226,7 @@ which uses fluentd as a logging agent. Here are two configuration files that
 you can use to implement this approach. The first file contains
 a [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) to configure fluentd.
 
-{{< code file="fluentd-sidecar-config.yaml" >}}
+{{< codenew file="admin/logging/fluentd-sidecar-config.yaml" >}}
 
 **Note**: The configuration of fluentd is beyond the scope of this article. For
 information about configuring fluentd, see the
@@ -235,7 +235,7 @@ information about configuring fluentd, see the
 The second file describes a pod that has a sidecar container running fluentd.
 The pod mounts a volume where fluentd can pick up its configuration data.
 
-{{< code file="two-files-counter-pod-agent-sidecar.yaml" >}}
+{{< codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" >}}
 
 After some time you can find log messages in the Stackdriver interface.