Consolidate YAML files [part-12] (#9364)

* Consolidate YAML files [part-12]

Relocate YAML files referenced by the accessing application topic
and the rest of cluster administration.

* Adjust json shortcodes.

content/en/docs/tasks/administer-cluster/running-cloud-controller.md

@@ -41,7 +41,7 @@ Successfully running cloud-controller-manager requires some changes to your clus
   since the cloud controller manager takes over labeling persistent volumes.
 * For the `cloud-controller-manager` to label persistent volumes, initializers will need to be enabled and an InitializerConifguration needs to be added to the system.  Follow [these instructions](/docs/admin/extensible-admission-controllers.md#enable-initializers-alpha-feature) to enable initializers.  Use the following YAML to create the InitializerConfiguration:
 
-{{< code file="persistent-volume-label-initializer-config.yaml" >}}
+{{< codenew file="admin/cloud/pvl-initializer-config.yaml" >}}
 
 Keep in mind that setting up your cluster to use cloud controller manager will change your cluster behaviour in a few ways:
 
@@ -71,7 +71,7 @@ For cloud controller managers not in Kubernetes core, you can find the respectiv
 
 For providers already in Kubernetes core, you can run the in-tree cloud controller manager as a Daemonset in your cluster, use the following as a guideline:
 
-{{< code file="cloud-controller-manager-daemonset-example.yaml" >}}
+{{< codenew file="admin/cloud/ccm-example.yaml" >}}
 
 
 ## Limitations