From e690ca416e333f0b3fbe1c25a1e19e6d58381bfc Mon Sep 17 00:00:00 2001 From: Travis Rhoden Date: Wed, 6 Jun 2018 14:52:26 -0600 Subject: [PATCH] Remove GCE references from service-access-application-cluster.md (#8765) Remove links and references that are GCE specific. (#8764) --- .../service-access-application-cluster.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/content/en/docs/tasks/access-application-cluster/service-access-application-cluster.md b/content/en/docs/tasks/access-application-cluster/service-access-application-cluster.md index 9c67c4f628..9c312e003c 100644 --- a/content/en/docs/tasks/access-application-cluster/service-access-application-cluster.md +++ b/content/en/docs/tasks/access-application-cluster/service-access-application-cluster.md @@ -101,15 +101,12 @@ provides load balancing for an application that has two running instances. see the node address by running `kubectl cluster-info`. If you are using Google Compute Engine instances, you can use the `gcloud compute instances list` command to see the public addresses of your - nodes. For more information about this command, see the [GCE documentation](https://cloud.google.com/sdk/gcloud/ -reference/compute/instances/list). + nodes. 1. On your chosen node, create a firewall rule that allows TCP traffic on your node port. For example, if your Service has a NodePort value of 31568, create a firewall rule that allows TCP traffic on port 31568. Different - cloud providers offer different ways of configuring firewall rules. See [the - GCE documentation on firewall rules](https://cloud.google.com/compute/docs/vpc/firewalls), - for example. + cloud providers offer different ways of configuring firewall rules. 1. Use the node address and node port to access the Hello World application: ```shell