How to solve the problem that Pod cannot access itself through Service IP in K8S?

How to solve the problem that Pod in K8S can not access itself through Service IP. In view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Problem description: pod can ping the Service name, but cannot connect to the corresponding port through nc or telnet

Resolve:

1. Modify svc mode cluster ip to load balance solution, but Aliyun needs to create slb. You can buy private network-shared slb for free.

2. Modify k8s configuration: kubelet-hairpin-mode configuration (https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#pods-are-not-accessible-via-their-service-ip)

), confirm that this configuration in the cluster uses the default configuration. The default configuration is promiscuous-bridge. If kubenet is not enabled, the configuration will be automatically switched to hairpin-veth mode.

This is the answer to how to solve the problem that Pod in K8S cannot access through Service IP. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.