If a master is down traffic is impacted is that right ?. Since the loadbalancer . . .

#1

Balaji K:
If a master is down traffic is impacted is that right ?. Since the loadbalancer IP receives packet and forwards which is getting impacted, why in the lectures its said not impacted ?.

#2

Vipul Agarwal:
@Balaji K the control plane (master) being down does not impact traffic. Any existing loadbalancer will continue serving traffic through the worker nodes. However, one cannot make any changes to loadbalancers and ingress if the master is unavailable.

#3

Balaji K:
@Vipul Agarwal These IP’s are hosted in master rt ? i.e the ip which is given as “LoadBalancer Service IP” is on master rt ?.

#4

Basavraj Nilkanthe:
@Balaji K Noo. You get IP address of load balancer from respective cloud provider… Even if you stick with nodePort service type. It’s accessible from node IP address and NodePort port number range from 30000 to 32676 range… It has nothing to do with master Node… However it can’t perform auto renewal with new pod if one goes down. It can’t do kubectl related activity until your master node resume it