无法从kubernetes中的另一个Pod ping Postgres Pod [英] Can't ping postgres pod from another pod in kubernetes

问题描述

我创建了一个忙碌的Pod，以按照yaml来测试数据库连接

I created one busy pod to test db connection by following yaml

pod.yaml

kind: Pod
apiVersion: v1
metadata:
  name: marks-dummy-pod
spec:
  containers:
    - name: marks-dummy-pod
      image: djtijare/ubuntuping:v1
      command: ["/bin/bash", "-ec", "while :; do echo '.'; sleep 5 ; done"]
  restartPolicy: Never

使用的Dockerfile:-

Dockerfile used :-

FROM ubuntu
RUN apt-get update && apt-get install -y iputils-ping
CMD bash

我以

postgresservice.yaml

postgresservice.yaml

kind: Service
apiVersion: v1
metadata:
 name: postgressvc
spec:
 type: ClusterIP
 ports:
 - port: 5432
   targetPort: 5432

所创建服务的端点为

kind: Endpoints
apiVersion: v1
metadata:
 name: postgressvc
subsets:
 - addresses:
     - ip: 172.31.6.149
   ports:
     - port: 5432

然后我在Pod(kubectl exec -it mark-dummy-pod bash)内运行了 ping 172.31.6.149 ，但没有运行.(ping本地主机正在运行)

Then i ran ping 172.31.6.149 inside pod (kubectl exec -it mark-dummy-pod bash) but not working.(ping localhost is working)

kubectl get pods，svc，ep -o wide

NAME                                       READY   STATUS    RESTARTS   AGE     IP             NODE              NOMINATED NODE   READINESS GATES
pod/marks-dummy-pod                        1/1     Running   0          43m     192.168.1.63   ip-172-31-11-87   <none>           <none>


NAME                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE     SELECTOR
service/postgressvc        ClusterIP   10.107.58.81     <none>        5432/TCP         33m     <none>


NAME                         ENDPOINTS           AGE
endpoints/postgressvc        172.31.6.149:5432   32m

P Ekambaram的答案输出

kubectl获取广告连播，svc，ep -o宽给出

NAME                            READY   STATUS    RESTARTS   AGE    IP             NODE              NOMINATED NODE   READINESS GATES
pod/postgres-855696996d-w6h6c   1/1     Running   0          44s    192.168.1.66   ip-172-31-11-87   <none>           <none>


NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE    SELECTOR
service/postgres        NodePort    10.110.203.204   <none>        5432:31076/TCP   44s    app=postgres



 NAME                      ENDPOINTS           AGE
endpoints/postgres        192.168.1.66:5432   44s

推荐答案

所以问题出在我的DNS吊舱中，它位于namespace = kube-system

So problem was in my DNS pod in namespace=kube-system

我只是创建新的kubernetes设置，并确保DNS正常工作

I just create new kubernetes setup and make sure that DNS is working

有关新设置，请参阅我对另一个问题的回答

For new setup refer to my answer of another question

如何启动kubelet服务??

这篇关于无法从kubernetes中的另一个Pod ping Postgres Pod的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！