<p>First, let me show the kubernetes entities from a namespace called "kong":</p>

<pre><code>[projadmin@VOFDGSTP1 ~]$ kubectl get all -n kong
NAME                               READY   STATUS    RESTARTS   AGE
pod/ingress-kong-5d997d864-wsmsw   2/2     Running   2          13d

NAME                              TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
service/kong-proxy                LoadBalancer   10.100.200.3     &lt;pending&gt;     80:31180/TCP,443:31315/TCP   13d
service/kong-validation-webhook   ClusterIP      10.100.200.175   &lt;none&gt;        443/TCP                      13d

NAME                           READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/ingress-kong   1/1     1            1           13d

NAME                                     DESIRED   CURRENT   READY   AGE
replicaset.apps/ingress-kong-5d997d864   1         1         1       13d
</code></pre>

<p>When I am trying to ping the IPs from above, I am getting timeout error.</p>

<pre><code>[projadmin@VOFDGSTP1 ~]$ curl -i 10.100.200.175
curl: (7) Failed connect to 10.100.200.175:80; Connection timed out
[projadmin@VOFDGSTP1 ~]$ curl -i 10.100.200.176
curl: (7) Failed connect to 10.100.200.176:80; Connection timed out
[projadmin@VOFDGSTP1 ~]$ curl -i 10.100.200.3
curl: (7) Failed connect to 10.100.200.3:80; Connection timed out
</code></pre>

<p>By the information you shared I could suppose you are trying to run the command outside the Cluster.</p>

<p>If you are doing this, it will not working, because you can't reach the <code>ClusterIP</code> services outside the cluster.</p>

<blockquote>
  <p><code>ClusterIP</code>: Exposes the Service on a cluster-internal IP. Choosing this value makes the Service only reachable from within the cluster. This is the default <code>ServiceType</code>.</p>
</blockquote>

<p>To check if the server you are connected is part of the cluster, type <code>kubectl get nodes -owide</code> e try to find the the ip in the list.</p>

<p>I see your service <code>service/kong-proxy</code> is with <code>EXTERNAL-IP: &lt;pending&gt;</code>, it's probably is occurring because you are trying to use a bare metal installation of Kubernetes, in this case you need to use <a href="https://metallb.universe.tf/" rel="nofollow noreferrer">MetalLB</a> to make your <code>LoadBalancer</code> configuration working.</p>

<p>An alternative to test your service is use <code>kubectl port-foward</code>, this will map your service to localhost and you can acces by <a href="http://localhost:8080" rel="nofollow noreferrer">http://localhost:8080</a>. Example:</p>

<p><code>kubectl port-forward svc/kong-proxy -n kong 8080:80</code></p>

<p>This command will map your service on port 8080 of your localhost.</p>

<p><strong>References:</strong></p>

<p><a href="https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types" rel="nofollow noreferrer">Services types</a></p>

<p><a href="https://metallb.universe.tf/" rel="nofollow noreferrer">MetalLB</a></p>

<p><a href="https://kubectl.docs.kubernetes.io/pages/container_debugging/port_forward_to_pods.html" rel="nofollow noreferrer">port-forward</a></p>
