Задать вопрос

Почему не работает kube-proxy в ubuntu 22.04?

Здравсвтуйте.
Я начинаю изучать кубирнетис и после установки кубирнетесе на двух VDS. (master и worker) node. увидел что kube-poryx на worker node а flannel то в статусе работает то нет.
Пытался разобраться и тонну сайтов перебрал но так и не понял как ее решить, подскажите пожалуйста в чем может быть проблема?

Пробовал добавить след. команду на master и worker ноде: sudo sysctl -w net.ipv4.conf.all.route_localnet=1

NAME                        STATUS   ROLES           AGE    VERSION   INTERNAL-IP       EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
kube-master-1.stand.local   Ready    control-plane   3d2h   v1.27.2   185.133.80.80     <none>        Ubuntu 22.04.2 LTS   5.15.0-73-generic   containerd://1.6.21
kube-worker-1.stand.local   Ready    <none>          3d1h   v1.27.2   109.240.200.150   <none>        Ubuntu 22.04.2 LTS   5.15.0-72-generic   containerd://1.6.21


NAMESPACE      NAME                                                READY   STATUS             RESTARTS          AGE    IP                NODE                        NOMINATED NODE   READINESS GATES
default        dev1-microservice-web-deployment-56bbb88669-6f2jm   0/1     CrashLoopBackOff   211 (2m46s ago)   22h    10.244.1.74       kube-worker-1.stand.local   <none>           <none>
kube-flannel   kube-flannel-ds-792n8                               1/1     Running            671 (8m7s ago)    3d1h   109.240.200.150   kube-worker-1.stand.local   <none>           <none>
kube-flannel   kube-flannel-ds-wjrhg                               1/1     Running            2 (26h ago)       3d1h   185.133.80.80     kube-master-1.stand.local   <none>           <none>
kube-system    coredns-5d78c9869d-6mmjv                            1/1     Running            2 (26h ago)       3d2h   10.244.0.6        kube-master-1.stand.local   <none>           <none>
kube-system    coredns-5d78c9869d-sx4qz                            1/1     Running            2 (26h ago)       3d2h   10.244.0.7        kube-master-1.stand.local   <none>           <none>
kube-system    etcd-kube-master-1.stand.local                      1/1     Running            3 (26h ago)       3d2h   185.133.80.80    kube-master-1.stand.local   <none>           <none>
kube-system    kube-apiserver-kube-master-1.stand.local            1/1     Running            3 (26h ago)       3d2h   185.133.80.80     kube-master-1.stand.local   <none>           <none>
kube-system    kube-controller-manager-kube-master-1.stand.local   1/1     Running            3 (26h ago)       3d2h   185.133.80.80     kube-master-1.stand.local   <none>           <none>
kube-system    kube-proxy-8v79t                                    1/1     Running            2 (26h ago)       3d2h   185.133.80.80     kube-master-1.stand.local   <none>           <none>
kube-system    kube-proxy-m78bz                                    0/1     CrashLoopBackOff   705 (3m35s ago)   3d1h   109.240.200.150   kube-worker-1.stand.local   <none>           <none>
kube-system    kube-scheduler-kube-master-1.stand.local            1/1     Running            3 (26h ago)       3d2h   185.133.80.80     kube-master-1.stand.local   <none>           <none>


I0602 15:28:27.874344       1 node.go:141] Successfully retrieved node IP: 109.240.200.150
I0602 15:28:27.874425       1 server_others.go:110] "Detected node IP" address="109.240.200.150"
I0602 15:28:27.874495       1 server_others.go:551] "Using iptables proxy"
I0602 15:28:27.889148       1 server_others.go:190] "Using iptables Proxier"
I0602 15:28:27.889178       1 server_others.go:197] "kube-proxy running in dual-stack mode" ipFamily=IPv4
I0602 15:28:27.889203       1 server_others.go:198] "Creating dualStackProxier for iptables"
I0602 15:28:27.889216       1 server_others.go:481] "Detect-local-mode set to ClusterCIDR, but no IPv6 cluster CIDR defined, defaulting to no-op detect-local for IPv6"
I0602 15:28:27.889261       1 proxier.go:253] "Setting route_localnet=1 to allow node-ports on localhost; to change this either disable iptables.localhostNodePorts (--iptables-localhost-nodeports) or set nodePortAddresses (--nodeport-addresses) to filter loopback addresses"
I0602 15:28:27.890181       1 server.go:657] "Version info" version="v1.27.2"
I0602 15:28:27.890195       1 server.go:659] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
I0602 15:28:27.892642       1 conntrack.go:52] "Setting nf_conntrack_max" nfConntrackMax=196608
I0602 15:28:27.892848       1 config.go:188] "Starting service config controller"
I0602 15:28:27.892873       1 shared_informer.go:311] Waiting for caches to sync for service config
I0602 15:28:27.892907       1 config.go:315] "Starting node config controller"
I0602 15:28:27.892912       1 shared_informer.go:311] Waiting for caches to sync for node config
I0602 15:28:27.892990       1 config.go:97] "Starting endpoint slice config controller"
I0602 15:28:27.893004       1 shared_informer.go:311] Waiting for caches to sync for endpoint slice config
I0602 15:28:27.993252       1 shared_informer.go:318] Caches are synced for node config
I0602 15:28:27.993335       1 shared_informer.go:318] Caches are synced for service config
I0602 15:28:27.993414       1 shared_informer.go:318] Caches are synced for endpoint slice config
  • Вопрос задан
  • 215 просмотров
Подписаться 2 Простой 1 комментарий
Пригласить эксперта
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Похожие вопросы