Kubernetes Pod to Pod communication via ClusterIp – Connection: close
Why does Kubernetes overrides and sets the HTTP response header as Connection: close for pod to pod communication via ClusterIp service. This behavior is resulting in a new connection creation and thereby response slowness on critical applications.
Internal service port and external service port does not match : kubernetes
So I was creating a demo project in order to learn kubernetes basics that’s where I had a task to be done. The IP of POD and IP of its corresponding Service endpoints are supposed to be same but they are different
In my case :
IP: 10.224.0.25
POD Endpoints : 10.224.0.31