test

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

@@ -34,5 +34,5 @@ The `kube-controller-manager` should not run any cloud-specific controllers, sin
 The `kube-apiserver` should not run the Persistent Volume Label admission controller either since the `cloud-controller-manager` takes over labeling persistent volumes.  To prevent the Persistent Volume Label admission plugin from running, make sure the `kube-apiserver` has a `--admission-control` flag with a value that does not include `PersistentVolumeLabel`.
 
 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:
-{% include code.html language="yaml" file="https://github.com/kubernetes/kubernetes/blob/master/examples/cloud-controller-manager/persistent-volume-label-initializer-config.yaml" ghlink="https://github.com/kubernetes/kubernetes/blob/master/examples/cloud-controller-manager/persistent-volume-label-initializer-config.yaml" %}
+{% include code.html language="yaml" file="https://raw.githubusercontent.com/kubernetes/kubernetes/master/examples/cloud-controller-manager/persistent-volume-label-initializer-config.yaml" ghlink="https://raw.githubusercontent.com/kubernetes/kubernetes/master/examples/cloud-controller-manager/persistent-volume-label-initializer-config.yaml" %}