Document URL:

https://docs.openshift.com/container-platform/4.5/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html#nw-exposing-service_configuring-ingress-cluster-traffic-ingress-controller

Section Number and Name:

Prerequisites

Describe the issue:

As per the Prerequisites, the only requirement is to have external system on the same subnet as the cluster but in the example, we show them accessing the services using clusterIP

Example, check point 4(pasting the doc line as such)

4. Use a tool, such as cURL, to make sure you can reach the service using the cluster IP address for the service

but in the actual example(in the box), we refer the POD IP

curl <pod_ip>:<port>

If you the follow documentation, podip:port or clusterip:port wont be accessible say from a bastion node which might be in the same subnet as that of the cluster

Also this example talks about deploying a mysql application. MySQL Service port 3306 is a non http port for the ingress controller to expose directly.

We should use a simple httpd container as the example

Suggestions for improvement:

1. We should show them examples on how to connect using ClusterIP or PodIP from another pod/cluster node
2. Another example like httpd would be preferable

oc new-app registry.redhat.io/rhel8/httpd-24

Additional information:

We have a customer who followed the documentation and complained the mysql service is not reachable. He was trying to access the service from a bastion node using clusterIP.