Consolidate YAML files [part-8] (#9347)

* Consolidate YAML files [part-8]

This PR exacts the YAML files referenced from the following subdirs:

- docs/concepts/workloads
- docs/concepts/configuration
- docs/concepts/policy

The following problems are fixed:

- docs/concepts/workloads/controllers/ doesnt have a 'cronjob.yaml for
  test
- the exactly same `pod.yaml` was used in both the task/config-pod-container
  topic and the concepts/configuration topics.

* Update examples_test.go

* Add missing yaml file.

content/en/docs/concepts/workloads/controllers/daemonset.md

@@ -39,11 +39,11 @@ different flags and/or different memory and cpu requests for different hardware
 
 You can describe a DaemonSet in a YAML file. For example, the `daemonset.yaml` file below describes a DaemonSet that runs the fluentd-elasticsearch Docker image:
 
-{{< code file="daemonset.yaml" >}}
+{{< codenew file="controllers/daemonset.yaml" >}}
 
 * Create a DaemonSet based on the YAML file:
 ```
-kubectl create -f daemonset.yaml
+kubectl create -f https://k8s.io/examples/controllers/daemonset.yaml
 ```
 
 ### Required Fields
@@ -252,4 +252,4 @@ number of replicas and rolling out updates are more important than controlling e
 the Pod runs on.  Use a DaemonSet when it is important that a copy of a Pod always run on
 all or certain hosts, and when it needs to start before other Pods.
 
-{{% /capture %}}
+{{% /capture %}}