Asking for help? Comment out what you need so we can get more information to help you!
Cluster information:
Kubernetes version: 1.22
Cloud being used: bare-metal
Installation method: kubeadm
Host OS: Linux / Ubuntu
CNI and version:
CRI and version:
I’ve got a basic query on master-worker nodes service routing
I had gone through several posts but I was unable to find out the answer
Lets assume the following setup
10.10.10.32 - Master Node (only-one master node)
10.10.10.1 - Worker Node #1
10.10.10.2 - Worker Node #2
nginx conf
upstream example {
server 10.10.10.1:30001; #worker-node1
server 10.10.10.2:30001; #worker-node2
}
server {
server_name domainname.com
location / {
proxy_pass http://example
}
}
When I hit domainname.com
request would be sent to upstream and response would be received by client
If I understand correctly, in the event of 'master node failure'
we would still be able to reach 'upstream servers'
and response would be received by client
My question is
why not we schedule the pods as 'static pods'?
if requests were able to reach upstream server even in case of 'master node failure'
Note: I understand static-pods are maintained by kubelet and cannot be reached through control plane
Isn’t there any relation to master-node when service was hit with respect to the setup mentioned above ?