Update Kuberbetes Blog URLs (#8612)

- blog.kubernetes.io => kubernetes.io/blog/
- Kubernetes blog => Kuberentes Blog
- Remove *.html

content/en/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md

@@ -133,7 +133,7 @@ the shared Volume is lost.
 {{% capture whatsnext %}}
 
 * Learn more about
-[patterns for composite containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html).
+[patterns for composite containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns).
 
 * Learn about
 [composite containers for modular architecture](http://www.slideshare.net/Docker/slideshare-burns).

content/en/docs/tasks/administer-cluster/reserve-compute-resources.md

@@ -86,7 +86,7 @@ It is not meant to reserve resources for system daemons that are run as pods.
 performance dashboard](http://node-perf-dash.k8s.io/#/builds) exposes `cpu` and
 `memory` usage profiles of `kubelet` and `docker engine` at multiple levels of
 pod density. [This blog
-post](http://blog.kubernetes.io/2016/11/visualize-kubelet-performance-with-node-dashboard.html)
+post](https://kubernetes.io/blog/2016/11/visualize-kubelet-performance-with-node-dashboard)
 explains how the dashboard can be interpreted to come up with a suitable
 `kube-reserved` reservation.
 

content/en/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md

@@ -58,7 +58,7 @@ would provision a network resource like a Google Compute Engine persistent disk,
 an NFS share, or an Amazon Elastic Block Store volume. Cluster administrators can also
 use [StorageClasses](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#storageclass-v1-storage)
 to set up
-[dynamic provisioning](http://blog.kubernetes.io/2016/10/dynamic-provisioning-and-storage-in-kubernetes.html).
+[dynamic provisioning](https://kubernetes.io/blog/2016/10/dynamic-provisioning-and-storage-in-kubernetes).
 
 Here is the configuration file for the hostPath PersistentVolume:
 

content/en/docs/tasks/debug-application-cluster/resource-usage-monitoring.md

@@ -60,4 +60,4 @@ Now that you've learned a bit about Heapster, feel free to try it out on your ow
 
 ***
 *Authors: Vishnu Kannan and Victor Marmol, Google Software Engineers.*
-*This article was originally posted in [Kubernetes blog](http://blog.kubernetes.io/2015/05/resource-usage-monitoring-kubernetes.html).*
+*This article was originally posted in [Kubernetes Blog](https://kubernetes.io/blog/2015/05/resource-usage-monitoring-kubernetes).*

content/en/docs/tasks/run-application/run-replicated-stateful-application.md

@@ -200,7 +200,7 @@ Ready before starting Pod `N+1`.
 After the Init Containers complete successfully, the regular containers run.
 The MySQL Pods consist of a `mysql` container that runs the actual `mysqld`
 server, and an `xtrabackup` container that acts as a
-[sidecar](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html).
+[sidecar](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns).
 
 The `xtrabackup` sidecar looks at the cloned data files and determines if
 it's necessary to initialize MySQL replication on the slave.