Update Kuberbetes Blog URLs (#8612)

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

content/en/docs/concepts/services-networking/connect-applications-service.md

@@ -20,7 +20,7 @@ By default, Docker uses host-private networking, so containers can talk to other
 
 Coordinating ports across multiple developers is very difficult to do at scale and exposes users to cluster-level issues outside of their control. Kubernetes assumes that pods can communicate with other pods, regardless of which host they land on. We give every pod its own cluster-private-IP address so you do not need to explicitly create links between pods or mapping container ports to host ports. This means that containers within a Pod can all reach each other's ports on localhost, and all pods in a cluster can see each other without NAT. The rest of this document will elaborate on how you can run reliable services on such a networking model.
 
-This guide uses a simple nginx server to demonstrate proof of concept. The same principles are embodied in a more complete [Jenkins CI application](http://blog.kubernetes.io/2015/07/strong-simple-ssl-for-kubernetes.html).
+This guide uses a simple nginx server to demonstrate proof of concept. The same principles are embodied in a more complete [Jenkins CI application](https://kubernetes.io/blog/2015/07/strong-simple-ssl-for-kubernetes).
 
 {{% /capture %}}
 

content/en/docs/concepts/workloads/pods/pod-overview.md

@@ -28,8 +28,8 @@ Pods in a Kubernetes cluster can be used in two main ways:
 
 The [Kubernetes Blog](http://blog.kubernetes.io) has some additional information on Pod use cases. For more information, see:
 
-* [The Distributed System Toolkit: Patterns for Composite Containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html)
-* [Container Design Patterns](http://blog.kubernetes.io/2016/06/container-design-patterns.html)
+* [The Distributed System Toolkit: Patterns for Composite Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns)
+* [Container Design Patterns](https://kubernetes.io/blog/2016/06/container-design-patterns)
 
 Each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run multiple instances), you should use multiple Pods, one for each instance. In Kubernetes, this is generally referred to as _replication_. Replicated Pods are usually created and managed as a group by an abstraction called a Controller. See [Pods and Controllers](#pods-and-controllers) for more information.
 

content/en/docs/concepts/workloads/pods/pod.md

@@ -110,7 +110,7 @@ application, in general.
 
 For a longer explanation, see [The Distributed System ToolKit: Patterns for
 Composite
-Containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html).
+Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns).
 
 ## Alternatives considered