virtual-ip | Virtual/Floating IP Manager

There seems to be two contradictory explanations of how NodePort services route traffic. Services can route traffic to one of the two, not both:

1. Nodes (through the kube-proxy) According to kubectl explain Service.spec.externalTrafficPolicy and this article that adds more detail, packets incoming to NodePort services with Service.spec.externalTrafficPolicy=Local set get routed to a kube-proxy, which then routes the packets to the corresponding pods its running.
   • This kube-proxy networking documentation further supports this theory adding that endpoints add a rule in the service's IPtable that forwards traffic to nodes through the kube-proxy.
2. Pods: services update their IPtables from endpoints, which contain the IP addresses for the pods they can route to. Furthermore, if you remove your service's label selectors and edit endpoints you can change where your traffic is routed to.

If one of these is right, then I must be misunderstanding something.

• If services route to nodes, then why can I edit endpoints without breaking the IPtables?
• If services route to pods, then why would services go through the trouble of routing to nodes when Service.spec.externalTrafficPolicy is set?

in some cluster environments, there are pair servers that are HA 2 by 2. for example i have server1 with IP 22.1.1.1 and server2 with IP 22.1.1.2.
server1 is giving service and server2 is standby. there is this virtual IP 22.1.1.3 that other servers connect to it to get services from server1 and server2.

now i need to monitor this virtual IP to see if it is up and other servers outside its VLAN can connect to it. how i can do this in zabbix?

i don't have an actual physical server to create in zabbix according to this question. i tried to create one but i got errors. also this question is asked 3 years ago. is there any new features i can use to solve this problem?

i had a case where i need to configure an AWS structure similar to the architecture that is described in this article, is but this article is old, when i followed the steps i couldn't pass the step at which i run the script "vip_monitor.sh". so be specific, at the step 5 by running the script i got the following error

I'm a bit confused by some of the Kubernetes documentation on virtual IPs: https://kubernetes.io/docs/concepts/services-networking/service/#the-gory-details-of-virtual-ips.

Userspace As an example, consider the image processing application described above. > When the backend Service is created, the Kubernetes master assigns a virtual IP address, for example 10.0.0.1.

The Kubernetes master assigns that VIP address to what? Where is the VIP address assigned?

How does the virtual IPs of a service integrate with an external ip address?

In order to allow users to choose a port number for their Services, we must ensure that no two Services can collide

Does this mean that when running kubectl get services I could see services having the same port?

When clients connect to the VIP, their traffic is automatically transported to an appropriate endpoint

Who are the clients? Other services within the cluster or some joe smo who's just using your app and knows nothing about kubernetes.