Kubernetes pod 无法连接到本地运行的 rabbit mq 实例 [英] Kubernetes pod unable to connect to rabbit mq instance running locally
问题描述
我正在将我的应用程序从 docker 转移到 kubernetes helm - 到目前为止,除了设置传入传出连接之外,我已经成功了.
I am moving my application from docker to kubernetes helm - and so far I have been successful except for setting up incoming outgoing connections.
我面临的一个特殊问题是我无法连接到在我的机器上本地运行的另一个 docker 容器上的 rabbitmq 实例.
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
但是当我部署为 docker 容器时也一样工作正常 - 我能够连接到在端口 5672 上运行在我的机器上的 rabbit mq 实例.
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.
我需要做些什么来建立从 pod 到我的本地机器的连接?
Is there something I would need to do to set up a connection from the pod to my local machine?
推荐答案
您正在为 pod 和服务公开端口 80.然后你在 5672 端口上卷曲.
You are exposing port 80 for both, the pod and the service. Then you curl on port 5672.
要么暴露pod的5672端口直接curl,要么暴露服务的5672端口,保持pod的80端口,curl服务的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)
假设你有两个豆荚.其中一个在端口 80 上提供服务,另一个在端口 5672 上提供服务.您可以创建两个服务;他们每个人都针对一个吊舱.这些服务可以在 80 端口上运行,并将请求映射到 Pod 的 80 和 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.
现在你不能让一个服务来做这两个转发.每个 Pod 需要一个服务.可以是一个部署,也可以是一组 Pod,但这些需要在同一个端口上提供服务.
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.
这篇关于Kubernetes pod 无法连接到本地运行的 rabbit mq 实例的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!