Kubernetes http请求始终在k8s群集pod的容器中被阻止
阶段:Kubernetes http请求始终在k8s群集pod的容器中被阻止,kubernetes,containers,Kubernetes,Containers,阶段: 连接容器的外壳 curl www.xxx.com(//这将一直等待) 然后在主机中使用tcpdump,并通过ip进行过滤 tcpdump-i eth0主机ip 3 11:05:05 2019/12/2 133.5701630 10.171.162.231 111.111.222.333 TCP TCP: [Bad CheckSum]Flags=......S., SrcPort=48836, DstPort=HTTP(80), PayloadLen=0, Seq=1268434
tcpdump
,并通过ip进行过滤
tcpdump-i eth0主机ip
3 11:05:05 2019/12/2 133.5701630 10.171.162.231 111.111.222.333 TCP TCP: [Bad CheckSum]Flags=......S., SrcPort=48836, DstPort=HTTP(80), PayloadLen=0, Seq=126843476, Ack=0, Win=29200 ( Negotiating scale factor 0x7 ) = 29200
4 11:05:05 2019/12/2 133.5704230 111.111.222.333 10.171.162.231 TCP TCP:Flags=...A..S., SrcPort=HTTP(80), DstPort=48836, PayloadLen=0, Seq=3228156738, Ack=126843477, Win=2896 ( Negotiated scale factor 0x9 ) = 1482752
5 11:05:05 2019/12/2 133.5704630 10.171.162.231 111.111.222.333 TCP TCP: [Bad CheckSum]Flags=...A...., SrcPort=48836, DstPort=HTTP(80), PayloadLen=0, Seq=126843477, Ack=3228156739, Win=229 (scale factor 0x7) = 29312
6 11:05:05 2019/12/2 133.5705430 10.171.162.231 111.111.222.333 HTTP HTTP:Request, GET /api/test, Query:debug
7 11:05:05 2019/12/2 133.5707110 111.111.222.333 10.171.162.231 TCP TCP:Flags=...A...., SrcPort=HTTP(80), DstPort=48836, PayloadLen=0, Seq=3228156739, Ack=126843596, Win=6 (scale factor 0x9) = 3072
tcp标志是
src -> dst syn
dst -> src syn/ack
src -> dst ack
src -> dst ack/push
dst -> src ack
curl
命令将等待很长时间,然后抛出超时错误。在正常请求中,有一个dst->src ack/push
数据包,但我从未收到过
我不知道为什么以及如何解决它
---我的朋友,亚马尔
apiVersion: apps/v1
kind: Deployment
metadata:
name: test-app-dep
labels:
app: test-app
version: stable
spec:
replicas: 2
selector:
matchLabels:
app: test-app
version: stable
template:
metadata:
labels:
app: test-app
version: stable
spec:
containers:
- image: test-app
name: test-app
livenessProbe:
httpGet:
path: /health/status
port: 80
initialDelaySeconds: 3
periodSeconds: 10
ports:
- containerPort: 80
这可能是因为多种原因。使用给定的信息很难猜测curl命令的问题。请添加YAML文件,以便更好地了解您的配置,也许有人可以帮助您。@RewanthCool我更新了我的问题。我有两个集群,只有一个集群有这个问题,所以我不认为这是配置的原因。这是发生在所有的吊舱或在这个特定的部署?是的。所有的pod都将在这一天发生cluster@quanweili部署的运行状况如何?服务是否已启动并在端口80上运行?如果可能的话,您是否可以共享您在上述部署文件中使用的映像名称,以便我们也可以尝试复制它?