New answers tagged

0

If my assumption is correct that's related to having a loadbalancer that wasn't correctly deleted. Which could be resulted by redeploying a service (of type: load balancer) in a short time before Azure cleans up the previously associated loadbalancer resource. To my knowledge, that could be fixed with the rolling of Kubernetes 1.17 and the Loadbalancer ...


Top 50 recent answers are included