Installation by Helm, port do not work


#1

I have a private server (not AWS, Google or others) CentOs 7 with kubernetes 1.11, I did the installation of Kong by Helm.
I ran the command kubectl get all:

NAME                                                  READY     STATUS      RESTARTS   AGE
pod/nonexistent-chicken-kong-6c7588fd4c-6xslh         1/1       Running     1          31m
pod/nonexistent-chicken-kong-migrations-shsss         0/1       Completed   1          31m
pod/nonexistent-chicken-postgresql-7cf5847d67-xrfb8   1/1       Running     0          31m

NAME                                     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
service/kubernetes                       ClusterIP   10.96.0.1        <none>        443/TCP          12d
service/nonexistent-chicken-kong-admin   NodePort    10.107.198.152   <none>        8444:31605/TCP   31m
service/nonexistent-chicken-kong-proxy   NodePort    10.104.213.232   <none>        8443:30827/TCP   31m
service/nonexistent-chicken-postgresql   ClusterIP   10.97.251.204    <none>        5432/TCP         31m

NAME                                             DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/nonexistent-chicken-kong         1         1         1            1           31m
deployment.apps/nonexistent-chicken-postgresql   1         1         1            1           31m

NAME                                                        DESIRED   CURRENT   READY     AGE
replicaset.apps/nonexistent-chicken-kong-6c7588fd4c         1         1         1         31m
replicaset.apps/nonexistent-chicken-postgresql-7cf5847d67   1         1         1         31m

NAME                                            DESIRED   SUCCESSFUL   AGE
job.batch/nonexistent-chicken-kong-migrations   1         1            31m

I ran the command because I checked in the installation document(https://docs.konghq.com/install/kubernetes/) to list everything and then make requests by Curl, but no requests worked out, all returned “Connection refused” to the port .

I also ran the netstat -tulnp command to check the ports and the ports I had to test did not appear.

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1086/master
tcp        0      0 0.0.0.0:6783            0.0.0.0:*               LISTEN      2634/weaver
tcp        0      0 127.0.0.1:6784          0.0.0.0:*               LISTEN      2634/weaver
tcp        0      0 127.0.0.1:33666         0.0.0.0:*               LISTEN      1512/kubelet
tcp        0      0 127.0.0.1:10248         0.0.0.0:*               LISTEN      1512/kubelet
tcp        0      0 127.0.0.1:10249         0.0.0.0:*               LISTEN      2160/kube-proxy
tcp        0      0 127.0.0.1:10251         0.0.0.0:*               LISTEN      1903/kube-scheduler
tcp        0      0 127.0.0.1:2379          0.0.0.0:*               LISTEN      1923/etcd
tcp        0      0 127.0.0.1:10252         0.0.0.0:*               LISTEN      1866/kube-controlle
tcp        0      0 127.0.0.1:2380          0.0.0.0:*               LISTEN      1923/etcd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      888/sshd
tcp6       0      0 ::1:25                  :::*                    LISTEN      1086/master
tcp6       0      0 :::6781                 :::*                    LISTEN      2248/weave-npc
tcp6       0      0 :::6782                 :::*                    LISTEN      2634/weaver
tcp6       0      0 :::10250                :::*                    LISTEN      1512/kubelet
tcp6       0      0 :::30827                :::*                    LISTEN      2160/kube-proxy
tcp6       0      0 :::6443                 :::*                    LISTEN      1905/kube-apiserver
tcp6       0      0 :::10256                :::*                    LISTEN      2160/kube-proxy
tcp6       0      0 :::31605                :::*                    LISTEN      2160/kube-proxy
tcp6       0      0 :::22                   :::*                    LISTEN      888/sshd
udp        0      0 127.0.0.1:323           0.0.0.0:*                           645/chronyd
udp        0      0 0.0.0.0:6783            0.0.0.0:*                           2634/weaver
udp        0      0 0.0.0.0:6784            0.0.0.0:*                           -
udp6       0      0 ::1:323                 :::*                                645/chronyd
udp6       0      0 :::6784                 :::*                                -

The Curl commands executed for testing were these:

$ curl kong-admin-ip-address:8001 
$ curl https://admin-ssl-ip-address:8444 
$ curl &lt;kong-proxy-ip-address:8000 
$ curl https://kong-proxy-ssl-ip-address:8443

I tested with the ip of the master server.
From the installation guide, I did not perform steps 2,3,4,5 and 7 as I installed by Helm.

How can I release these ports? I imagine they are needed to set up the Ingress that I will need.


#2

Hello @Andre_Krebs,

A few questions before I can help you debug the issue:

Are you trying to install Kong as an app on your k8s or as an Ingress controller?
Where (which node/box?) did you run netstat -tunlnp?

I tested with the ip of the master server.

What is the master server are you referring to here?


#3

@hbagdi,
I am wanting to install as an Ingress driver and ran netstat on the cluster master server.

What is the master server are you referring to here?

The cluster master server, the same one that I ran netstat and that I want to use to access the services through the ingress.