<p>I have deployed <strong>Kong-Ingress-controller</strong> using <strong>helm</strong> </p>

<p>And I have Kubernetes's Cluster v1.10 On centos 7 </p>

<p>I am using dedicated Server From OVH Provider </p>

<p>When I create Ingress </p>

<pre><code>cat ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: jenkins 
spec:
  backend:
    serviceName: jenkins
    servicePort: 8080
</code></pre>

<hr>

<pre><code>kubectl get ing
NAME      HOSTS     ADDRESS   PORTS     AGE
jenkins   *                   80        3s
</code></pre>

<hr>

<pre><code>kubectl get svc
NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
jenkins                ClusterIP   10.254.104.80   &lt;none&gt;        8080/TCP         1d
</code></pre>

<p>Now I Can not access this Ingress from Out Side because I am using OVH Server.</p>

<p>Is there a solution? </p>

<p>OVH is not <a href="https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/" rel="nofollow noreferrer">officially supported by Kubernetes</a>. It was supported then generally you would create a Service <code>jenkins</code> of the type <code>LoadBalancer</code> and that would be your externally facing endpoint with a public IP.</p>

<p>Since it's not supported the next best thing is to create a <code>NodePort</code> service. That will create a service that listens on a specific port on all the Kubernetes nodes and forwards the requests to your Pods (only where they are running). So, in this case, you will have to create an <a href="https://www.ovh.com/world/solutions/load-balancer/" rel="nofollow noreferrer">OVH Load Balancer</a> with a public IP and point the backend of that load balancer to the <code>NodePort</code> of the service where your <code>Ingress</code> is listening on.</p>
