Can I use NodePort-type service to access local pod?

If 2 pods of a NodePort-type service are scheduled on node A and node B, when an external client accesses the service using node A’s IP and the service’s port number, will the KubeProxy forward
the client’s request to the pod on node B? Or will the KubeProxy always forward the client’s request to the pod node A?

Does Service | Kubernetes not explain it enough?

According to the documentation, the request will be forwarded by the KubeProxy by some load balancing srategy, right?

the request will be forwarded by the KubeProxy by some load balancing srategy

kube-proxy typically sets up kernel-level rules to do that, rather than playing any active role in redirecting the traffic itself. It’s just faster that way.

Each node proxies that port […] For a node port Service, Kubernetes additionally allocates a port […] Every node in the cluster configures itself to listen on that assigned port and to forward traffic to one of the ready endpoints associated with that Service.

I think that’s all referring to the effect, not the actual implementation. Because the latter depends on the proxy mode that you choose.

To answer the original question, you might be thinking of traffic policies.

Thank you for you hint