8000 Remove GCE references from service-access-application-cluster.md (#8765) · ArduinoBot/website@e690ca4 · GitHub
[go: up one dir, main page]

Skip to content

Commit e690ca4

Browse files
codenrhodenk8s-ci-robot
authored andcommitted
Remove GCE references from service-access-application-cluster.md (kubernetes#8765)
Remove links and references that are GCE specific. (kubernetes#8764)
1 parent b24f632 commit e690ca4

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

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

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -101,15 +101,12 @@ provides load balancing for an application that has two running instances.
101101
see the node address by running `kubectl cluster-info`. If you are
102102
using Google Compute Engine instances, you can use the
103103
`gcloud compute instances list` command to see the public addresses of your
104-
nodes. For more information about this command, see the [GCE documentation](https://cloud.google.com/sdk/gcloud/
105-
reference/compute/instances/list).
104+
nodes.
106105

107106
1. On your chosen node, create a firewall rule that allows TCP traffic
108107
on your node port. For example, if your Service has a NodePort value of
109108
31568, create a firewall rule that allows TCP traffic on port 31568. Different
110-
cloud providers offer different ways of configuring firewall rules. See [the
111-
GCE documentation on firewall rules](https://cloud.google.com/compute/docs/vpc/firewalls),
112-
for example.
109+
cloud providers offer different ways of configuring firewall rules.
113110

114111
1. Use the node address and node port to access the Hello World application:
115112
```shell

0 commit comments

Comments
 (0)
0