merge master to 1.10, with fixes (#7682)

docs/tasks/access-application-cluster/access-cluster.md

@@ -135,10 +135,10 @@ If the application is deployed as a Pod in the cluster, please refer to the [nex
 
 #### Python client
 
-To use [Python client](https://github.com/kubernetes-incubator/client-python), run the following command: `pip install kubernetes`. See [Python Client Library page](https://github.com/kubernetes-incubator/client-python) for more installation options.
+To use [Python client](https://github.com/kubernetes-client/python), run the following command: `pip install kubernetes`. See [Python Client Library page](https://github.com/kubernetes-client/python) for more installation options.
 
 The Python client can use the same [kubeconfig file](/docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig/)
-as the kubectl CLI does to locate and authenticate to the apiserver. See this [example](https://github.com/kubernetes-incubator/client-python/tree/master/examples/example1.py).
+as the kubectl CLI does to locate and authenticate to the apiserver. See this [example](https://github.com/kubernetes-client/python/tree/master/examples/example1.py).
 
 #### Other languages
 

docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md

@@ -1,5 +1,5 @@
 ---
-approvers:
+reviewers:
 - bprashanth
 - davidopp
 title: Configure Your Cloud Provider's Firewalls

docs/tasks/access-application-cluster/create-external-load-balancer.md

@@ -105,6 +105,12 @@ which should produce output like this:
 
 The IP address is listed next to `LoadBalancer Ingress`.
 
+**Note**: If you are running your service on Minikube, you can find the assigned IP address and port with:
+{: .note}
+```bash
+minikube service example-service --url
+```
+
 ## Preserving the client source IP
 
 Due to the implementation of this feature, the source IP seen in the target

docs/tasks/access-application-cluster/frontend.yaml

@@ -12,11 +12,16 @@ spec:
     targetPort: 80
   type: LoadBalancer
 ---
-apiVersion: apps/v1beta1
+apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: frontend
 spec:
+  selector:
+    matchLabels:
+      app: hello
+      tier: frontend
+      track: stable
   replicas: 1
   template:
     metadata:

docs/tasks/access-application-cluster/hello.yaml

@@ -1,8 +1,13 @@
-apiVersion: apps/v1beta1
+apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: hello
 spec:
+  selector:
+    matchLabels:
+      app: hello
+      tier: backend
+      track: stable
   replicas: 7
   template:
     metadata:

docs/tasks/access-application-cluster/service-access-application-cluster.md

@@ -71,6 +71,8 @@ provides load balancing for an application that has two running instances.
         Type:                   NodePort
         IP:                     10.32.0.16
         Port:                   <unset> 8080/TCP
+        TargetPort:             8080/TCP
+        NodePort:               <unset> 31496/TCP
         Endpoints:              10.200.1.4:8080,10.200.2.5:8080
         Session Affinity:       None
         Events:                 <none>

docs/tasks/access-application-cluster/web-ui-dashboard.md

@@ -1,5 +1,5 @@
 ---
-approvers:
+reviewers:
 - bryk
 - mikedanese
 - rf232
@@ -156,7 +156,7 @@ Services and discovery view shows Kubernetes resources that allow for exposing s
 Storage view shows Persistent Volume Claim resources which are used by applications for storing data.
 
 #### Config
-Config view show all Kubernetes resources that are used for live configuration of applications running in clusters. This is now Config Maps and Secrets. The view allows for editing and managing config objects and displays secrets hidden by default.
+Config view shows all Kubernetes resources that are used for live configuration of applications running in clusters. This is now Config Maps and Secrets. The view allows for editing and managing config objects and displays secrets hidden by default.
 
 ![Secret detail view](/images/docs/ui-dashboard-secret-detail.png)