Tweak k8s URLs to point to v1.8 topics (#417)

docker-for-mac/kubernetes.md

@@ -4,4 +4,4 @@ keywords: mac, edge, kubernetes, kubectl, orchestration
 title: Deploy to Kubernetes
 ---
 
-{% include kubernetes-mac-win.md platform="mac" %}
+{% include kubernetes-mac-win.md platform="mac" %}

ee/ucp/authorization/group-resources.md

@@ -18,7 +18,7 @@ next_steps:
 ## Kubernetes namespace
 
 A
-[namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
+[namespace](https://v1-8.docs.kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
 is a logical area for a Kubernetes cluster. Kubernetes comes with a "default"
 namespace for your cluster objects (plus two more for system and public
 resources). You can create custom namespaces, but unlike Swarm collections,
@@ -27,7 +27,7 @@ namespaces _cannot be nested_.
 > Resource types that can be placed into a Kubernetes namespace include: Pods,
 > Deployments, NetworkPolicies, Nodes, Services, Secrets, and many more.
 
-Resources are placed into a namespace when you create a kubernetes object. A
+Resources are placed into a namespace when you create a Kubernetes object. A
 drop down displays all available namespaces and one must be selected.
 
 ## Swarm collection
@@ -93,7 +93,7 @@ set.
 
 > Default collections and collection labels
 >
-> Default collections are good for users who ony work on a well-defined slice of
+> Default collections are good for users who work only on a well-defined slice of
 > the system, as well as users who deploy stacks and don't want to edit the
 > contents of their compose files. A user with more versatile roles in the
 > system, such as an administrator, might find it better to set custom labels for

ee/ucp/authorization/index.md

@@ -76,7 +76,7 @@ assign application resources to that path.
 > Networks, Nodes, Services, Secrets, and Volumes.
 
 A
-[namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
+[namespace](https://v1-8.docs.kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
 is a logical area for a Kubernetes cluster. Kubernetes comes with a "default"
 namespace for your cluster objects (plus two more for system and public
 resources). You can create custom namespaces, but unlike Swarm collections,

ee/ucp/user/services/deploy-kubernetes-workload.md

@@ -107,7 +107,7 @@ The service connects the cluster's internal port 80 to the external port
 
 The YAML definition connects the service to the NGINX server by using the
 app label `nginx` and a corresponding label selector.
-[Learn about using a service to expose your app](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose-intro/).
+[Learn about using a service to expose your app](https://v1-8.docs.kubernetes.io/docs/tutorials/kubernetes-basics/expose-intro/).
 
 ## Update the deployment
 
@@ -156,7 +156,7 @@ spec:
 {% if include.version=="kubectl" %}
 
 With Docker EE, you deploy your Kubernetes objects on the command line by using
-`kubectl`. [Install and set up kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/).
+`kubectl`. [Install and set up kubectl](https://v1-8.docs.kubernetes.io/docs/tasks/tools/install-kubectl/).
 
 Use a client bundle to configure your client tools, like Docker CLI and `kubectl`
 to communicate with UCP instead of the local deployments you might have running.