• DevOps
  • 按照3.1一直拉取不到gitee仓库代码,跪求大神帮一个

jayang
看看你用的什么CNI网络插件,describe以及log插件对应的pod(比如calico/flannel)看看有没有什么异常
分别在宿主机与容器里执行ip addrip route看网络配置
在宿主机上执行iptables-save看防火墙配置

    kevendeng
    的 flannel,应该是找到原因了,docker0网卡 mtu 是1500, flannel拉起来的Pod 全部是 1450

    kevendeng 第一次接触liunx的 ,没啥经验,谢谢老哥了,我看下 flannel的配置里面有没有设置mtu的选项,设好应该就可以了,单独的容器 不用k8s 是可以curl https://gitee.com的

      jayang 宿主机应该还有个interface是cni0吧,你的集群中flannel没用docker0这个接口,用的是cni0,应该不是因为你说的这个问题。

        jayang 隧道网络的mtu是这样的,留了一部分,这个是正常的

        jayang K8S里的POD本来用的就是flannel的接口,你不能连通外网是因为另外的问题。
        看看你的防火墙规则。
        iptables-save

          jayang 信息不全,你找个paste网站或者保存文件后以附件上传吧。

            kevendeng iptables-save

            # Generated by iptables-save v1.4.21 on Tue Jun  8 15:07:45 2021
            *mangle
            :PREROUTING ACCEPT [342038678:208413799805]
            :INPUT ACCEPT [265463310:73794368324]
            :FORWARD ACCEPT [76697556:134630557832]
            :OUTPUT ACCEPT [257897679:89031504795]
            :POSTROUTING ACCEPT [335889841:223839263418]
            :KUBE-KUBELET-CANARY - [0:0]
            :KUBE-PROXY-CANARY - [0:0]
            COMMIT
            # Completed on Tue Jun  8 15:07:45 2021
            # Generated by iptables-save v1.4.21 on Tue Jun  8 15:07:45 2021
            *filter
            :INPUT ACCEPT [340115:60962861]
            :FORWARD ACCEPT [0:0]
            :OUTPUT ACCEPT [314896:59199626]
            :DOCKER - [0:0]
            :DOCKER-ISOLATION-STAGE-1 - [0:0]
            :DOCKER-ISOLATION-STAGE-2 - [0:0]
            :DOCKER-USER - [0:0]
            :KUBE-EXTERNAL-SERVICES - [0:0]
            :KUBE-FIREWALL - [0:0]
            :KUBE-FORWARD - [0:0]
            :KUBE-KUBELET-CANARY - [0:0]
            :KUBE-PROXY-CANARY - [0:0]
            :KUBE-SERVICES - [0:0]
            -A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
            -A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes externally-visible service portals" -j KUBE-EXTERNAL-SERVICES
            -A INPUT -j KUBE-FIREWALL
            -A FORWARD -j DOCKER-USER
            -A FORWARD -j DOCKER-ISOLATION-STAGE-1
            -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
            -A FORWARD -o docker0 -j DOCKER
            -A FORWARD -i docker0 ! -o docker0 -j ACCEPT
            -A FORWARD -i docker0 -o docker0 -j ACCEPT
            -A FORWARD -o br-f2a1b66523f8 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
            -A FORWARD -o br-f2a1b66523f8 -j DOCKER
            -A FORWARD -i br-f2a1b66523f8 ! -o br-f2a1b66523f8 -j ACCEPT
            -A FORWARD -i br-f2a1b66523f8 -o br-f2a1b66523f8 -j ACCEPT
            -A FORWARD -m comment --comment "kubernetes forwarding rules" -j KUBE-FORWARD
            -A FORWARD -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
            -A FORWARD -s 10.244.0.0/16 -j ACCEPT
            -A FORWARD -d 10.244.0.0/16 -j ACCEPT
            -A OUTPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
            -A OUTPUT -j KUBE-FIREWALL
            -A DOCKER -d 172.18.0.4/32 ! -i br-f2a1b66523f8 -o br-f2a1b66523f8 -p tcp -m tcp --dport 80 -j ACCEPT
            -A DOCKER -d 172.18.0.4/32 ! -i br-f2a1b66523f8 -o br-f2a1b66523f8 -p tcp -m tcp --dport 22 -j ACCEPT
            -A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
            -A DOCKER-ISOLATION-STAGE-1 -i br-f2a1b66523f8 ! -o br-f2a1b66523f8 -j DOCKER-ISOLATION-STAGE-2
            -A DOCKER-ISOLATION-STAGE-1 -j RETURN
            -A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
            -A DOCKER-ISOLATION-STAGE-2 -o br-f2a1b66523f8 -j DROP
            -A DOCKER-ISOLATION-STAGE-2 -j RETURN
            -A DOCKER-USER -j RETURN
            -A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
            -A KUBE-FIREWALL ! -s 127.0.0.0/8 -d 127.0.0.0/8 -m comment --comment "block incoming localnet connections" -m conntrack ! --ctstate RELATED,ESTABLISHED,DNAT -j DROP
            -A KUBE-FORWARD -m conntrack --ctstate INVALID -j DROP
            -A KUBE-FORWARD -m comment --comment "kubernetes forwarding rules" -m mark --mark 0x4000/0x4000 -j ACCEPT
            -A KUBE-FORWARD -m comment --comment "kubernetes forwarding conntrack pod source rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
            -A KUBE-FORWARD -m comment --comment "kubernetes forwarding conntrack pod destination rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
            COMMIT
            # Completed on Tue Jun  8 15:07:45 2021
            # Generated by iptables-save v1.4.21 on Tue Jun  8 15:07:45 2021
            *nat
            :PREROUTING ACCEPT [515:102748]
            :INPUT ACCEPT [501:101009]
            :OUTPUT ACCEPT [3619:244322]
            :POSTROUTING ACCEPT [2742:175712]
            :DOCKER - [0:0]
            :KUBE-KUBELET-CANARY - [0:0]
            :KUBE-MARK-DROP - [0:0]
            :KUBE-MARK-MASQ - [0:0]
            :KUBE-NODEPORTS - [0:0]
            :KUBE-POSTROUTING - [0:0]
            :KUBE-PROXY-CANARY - [0:0]
            :KUBE-SEP-232DQYSHL5HNRYWJ - [0:0]
            :KUBE-SEP-A4UL7OUXQPUR7Y7Q - [0:0]
            :KUBE-SEP-CPH3WXMLRJ2BZFXW - [0:0]
            :KUBE-SEP-ELORNGZOTUPHZG5W - [0:0]
            :KUBE-SEP-SISP6ORRA37L3ZYK - [0:0]
            :KUBE-SEP-XNZERJBNXRGRQGMS - [0:0]
            :KUBE-SEP-XRFUWCXKVCLGWYQC - [0:0]
            :KUBE-SERVICES - [0:0]
            :KUBE-SVC-ERIFXISQEP7F7OF4 - [0:0]
            :KUBE-SVC-JD5MR3NA4I4DYORP - [0:0]
            :KUBE-SVC-NPX46M4PTMTKRN6Y - [0:0]
            :KUBE-SVC-TCOU7JCQXEZGVUNU - [0:0]
            -A PREROUTING -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
            -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
            -A OUTPUT -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
            -A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER
            -A POSTROUTING -s 10.244.0.0/24 ! -o docker0 -j MASQUERADE
            -A POSTROUTING -s 172.18.0.0/16 ! -o br-f2a1b66523f8 -j MASQUERADE
            -A POSTROUTING -m comment --comment "kubernetes postrouting rules" -j KUBE-POSTROUTING
            -A POSTROUTING -s 10.244.0.0/16 -d 10.244.0.0/16 -j RETURN
            -A POSTROUTING -s 10.244.0.0/16 ! -d 224.0.0.0/4 -j MASQUERADE
            -A POSTROUTING ! -s 10.244.0.0/16 -d 10.244.0.0/24 -j RETURN
            -A POSTROUTING ! -s 10.244.0.0/16 -d 10.244.0.0/16 -j MASQUERADE
            -A POSTROUTING -s 172.18.0.4/32 -d 172.18.0.4/32 -p tcp -m tcp --dport 80 -j MASQUERADE
            -A POSTROUTING -s 172.18.0.4/32 -d 172.18.0.4/32 -p tcp -m tcp --dport 22 -j MASQUERADE
            -A DOCKER -i docker0 -j RETURN
            -A DOCKER -i br-f2a1b66523f8 -j RETURN
            -A DOCKER ! -i br-f2a1b66523f8 -p tcp -m tcp --dport 10080 -j DNAT --to-destination 172.18.0.4:80
            -A DOCKER ! -i br-f2a1b66523f8 -p tcp -m tcp --dport 10022 -j DNAT --to-destination 172.18.0.4:22
            -A KUBE-MARK-DROP -j MARK --set-xmark 0x8000/0x8000
            -A KUBE-MARK-MASQ -j MARK --set-xmark 0x4000/0x4000
            -A KUBE-POSTROUTING -m mark ! --mark 0x4000/0x4000 -j RETURN
            -A KUBE-POSTROUTING -j MARK --set-xmark 0x4000/0x0
            -A KUBE-POSTROUTING -m comment --comment "kubernetes service traffic requiring SNAT" -j MASQUERADE
            -A KUBE-SEP-232DQYSHL5HNRYWJ -s 10.244.0.7/32 -m comment --comment "kube-system/kube-dns:dns" -j KUBE-MARK-MASQ
            -A KUBE-SEP-232DQYSHL5HNRYWJ -p udp -m comment --comment "kube-system/kube-dns:dns" -m udp -j DNAT --to-destination 10.244.0.7:53
            -A KUBE-SEP-A4UL7OUXQPUR7Y7Q -s 10.244.0.7/32 -m comment --comment "kube-system/kube-dns:dns-tcp" -j KUBE-MARK-MASQ
            -A KUBE-SEP-A4UL7OUXQPUR7Y7Q -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp" -m tcp -j DNAT --to-destination 10.244.0.7:53
            -A KUBE-SEP-CPH3WXMLRJ2BZFXW -s 10.244.0.7/32 -m comment --comment "kube-system/kube-dns:metrics" -j KUBE-MARK-MASQ
            -A KUBE-SEP-CPH3WXMLRJ2BZFXW -p tcp -m comment --comment "kube-system/kube-dns:metrics" -m tcp -j DNAT --to-destination 10.244.0.7:9153
            -A KUBE-SEP-ELORNGZOTUPHZG5W -s 10.192.7.111/32 -m comment --comment "default/kubernetes:https" -j KUBE-MARK-MASQ
            -A KUBE-SEP-ELORNGZOTUPHZG5W -p tcp -m comment --comment "default/kubernetes:https" -m tcp -j DNAT --to-destination 10.192.7.111:6443
            -A KUBE-SEP-SISP6ORRA37L3ZYK -s 10.244.0.8/32 -m comment --comment "kube-system/kube-dns:dns" -j KUBE-MARK-MASQ
            -A KUBE-SEP-SISP6ORRA37L3ZYK -p udp -m comment --comment "kube-system/kube-dns:dns" -m udp -j DNAT --to-destination 10.244.0.8:53
            -A KUBE-SEP-XNZERJBNXRGRQGMS -s 10.244.0.8/32 -m comment --comment "kube-system/kube-dns:metrics" -j KUBE-MARK-MASQ
            -A KUBE-SEP-XNZERJBNXRGRQGMS -p tcp -m comment --comment "kube-system/kube-dns:metrics" -m tcp -j DNAT --to-destination 10.244.0.8:9153
            -A KUBE-SEP-XRFUWCXKVCLGWYQC -s 10.244.0.8/32 -m comment --comment "kube-system/kube-dns:dns-tcp" -j KUBE-MARK-MASQ
            -A KUBE-SEP-XRFUWCXKVCLGWYQC -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp" -m tcp -j DNAT --to-destination 10.244.0.8:53
            -A KUBE-SERVICES ! -s 10.244.0.0/16 -d 10.1.0.1/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-MARK-MASQ
            -A KUBE-SERVICES -d 10.1.0.1/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-SVC-NPX46M4PTMTKRN6Y
            -A KUBE-SERVICES ! -s 10.244.0.0/16 -d 10.1.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:metrics cluster IP" -m tcp --dport 9153 -j KUBE-MARK-MASQ
            -A KUBE-SERVICES -d 10.1.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:metrics cluster IP" -m tcp --dport 9153 -j KUBE-SVC-JD5MR3NA4I4DYORP
            -A KUBE-SERVICES ! -s 10.244.0.0/16 -d 10.1.0.10/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-MARK-MASQ
            -A KUBE-SERVICES -d 10.1.0.10/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-SVC-TCOU7JCQXEZGVUNU
            -A KUBE-SERVICES ! -s 10.244.0.0/16 -d 10.1.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-MARK-MASQ
            -A KUBE-SERVICES -d 10.1.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-SVC-ERIFXISQEP7F7OF4
            -A KUBE-SERVICES -m comment --comment "kubernetes service nodeports; NOTE: this must be the last rule in this chain" -m addrtype --dst-type LOCAL -j KUBE-NODEPORTS
            -A KUBE-SVC-ERIFXISQEP7F7OF4 -m comment --comment "kube-system/kube-dns:dns-tcp" -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-A4UL7OUXQPUR7Y7Q
            -A KUBE-SVC-ERIFXISQEP7F7OF4 -m comment --comment "kube-system/kube-dns:dns-tcp" -j KUBE-SEP-XRFUWCXKVCLGWYQC
            -A KUBE-SVC-JD5MR3NA4I4DYORP -m comment --comment "kube-system/kube-dns:metrics" -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-CPH3WXMLRJ2BZFXW
            -A KUBE-SVC-JD5MR3NA4I4DYORP -m comment --comment "kube-system/kube-dns:metrics" -j KUBE-SEP-XNZERJBNXRGRQGMS
            -A KUBE-SVC-NPX46M4PTMTKRN6Y -m comment --comment "default/kubernetes:https" -j KUBE-SEP-ELORNGZOTUPHZG5W
            -A KUBE-SVC-TCOU7JCQXEZGVUNU -m comment --comment "kube-system/kube-dns:dns" -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-232DQYSHL5HNRYWJ
            -A KUBE-SVC-TCOU7JCQXEZGVUNU -m comment --comment "kube-system/kube-dns:dns" -j KUBE-SEP-SISP6ORRA37L3ZYK
            COMMIT
            # Completed on Tue Jun  8 15:07:45 2021
            14 天 后

            jayang 如果可以的话,去找一个有 mtr 命令的容器,在集群中运行看看网络具体走的什么链路。

              johnniang
              还是没找到 就是这种现象 能Ping通 但是无法curl ,docker 单独拉取的镜像都可以curl 下来网页

              6 天 后

              我也碰到类似问题,创建流水线,选择代码仓库,点确认后,报500错误,换成svn也是这样,感觉是容器/pod与外面网络不通,这个网络问题怎么解决
              ![
              ](https://)
              ![
              ](https://)

              • Rick 回复了此帖

                plus_chao 有报错,得把报错信息贴上来,另外,你的这个问题应该和这个帖子不是一个主题吧