K
Q

Question

Kubernetes pod unable to connect to rabbit mq instance running locally

11/22/2018

I am moving my application from docker to kubernetes \ helm - and so far I have been successful except for setting up incoming \ outgoing connections.

One particular issue I am facing is that I am unable to connect to the rabbitmq instance running locally on my machine on another docker container.

app-deployment.yaml:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: jks
  labels:
    app: myapp
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: myapp
    spec:
      imagePullSecrets:
      - name: ivsecret
      containers:
      - env:
        - name: JOBQUEUE
          value: jks_jobqueue
        - name: PORT
          value: "80"
        image: repo.url
        name: jks
        ports:
        - containerPort: 80
        volumeMounts:
          - name: config-vol
            mountPath: /etc/sys0
      volumes:
        - name: config-vol
          configMap:
            name: config

      restartPolicy: Always

------------

app-service.yaml:

apiVersion: v1
kind: Service
metadata:
  name: jks
spec:
  ports:
  - name: "80"
    port: 80
    targetPort: 80
  selector:
    app: myapp

I see errors on my container, complaining that it is not able to connect to my machine. I tried curl from inside the container:

curl 10.2.10.122:5672
curl: (7) Failed to connect to 10.20.11.11 port 5672: Connection timed out

But the same when I deploy as a docker container works fine - and I am able to connect to the rabbit mq instance running on my machine on port 5672.

Is there something I would need to do to set up a connection from the pod to my local machine?

-- Chillax

kubernetes

kubernetes-helm

kubernetes-pod

minikube

2 Answers

11/22/2018

You are exposing port 80 for both, the pod and the service. Then you curl on port 5672.

Either expose port 5672 of the pod and curl it directly, or expose port 5672 of the service and keep port 80 on the pod, and curl on port 5672 of the service.

This would be a high level "sketch" of how to hit a pod:

you -curl-> service1(80:80) -> pod1(80)
you -curl-> service2(80:5672) -> pod2(5672)

So say you have two pods. One of them is serving on port 80, and the other one on port 5672. You can create two services; each of them targeting one pod. The services can be running on port 80 and map the requests to the ports 80 and 5672 of the pods.

Now you can't make one service to do the both forwarding. Needs to be one service per pod. Can be a deployment, or a group of pods, but these need to be serving on the same port.

-- suren

Source: StackOverflow

11/23/2018

If I understood the setup:

minikube is running on the local machine.
rabbitmq is running on the local machine, too, and is listening on port 5672.
the IP where rabbitmq is running is 10.2.10.122 .
an application - jks - is running on minikube.

The problem is that it is not possible to connect from the jks application to rabbitmq, correct?

One way to make it work is to first create a Service without selector :

apiVersion: "v1"
kind: "Service"
metadata:
  name: "svc-external-rabbitmq"
spec:
  ports:
  - name: "rabbitmq"
    protocol: "TCP"
    port: 5672
    targetPort: 5672
    nodePort: 0
selector: {}

...next, create Endpoints object for the Service:

apiVersion: "v1"
kind: "Endpoints"
metadata:
  name: "svc-external-rabbitmq"
subsets:
  - addresses:
    - ip: "10.2.10.122"
    ports:
    - name: "rabbitmq"
      port: 5672

...then use the service name - svc-external-rabbitmq - in the jks application to connect to rabbitmq.

For an explanation, see Services without selectors in the Kubernetes documentation. I've used this setup with a Cassandra cluster where the Cassandra nodes' IPs were all listed as addresses.

EDIT: Notice that in some cases a Service of type ExternalName could work, too.

-- apisim

Source: StackOverflow

KQ

Kubernetes pod unable to connect to rabbit mq instance running locally

Similar Questions

2 Answers

K
Q