Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
kube-controller-manager is stucking in deleting Azure LB because of wrong idle timeout set #75356
When the Idle Timeout annotation was set to "3" which isn't a supported case, kube-controller-manager is stuck in deleting Azure LB. New service with the same name couldn't be created again even without the annotation.
What you expected to happen:
New service should be created successfully.
How to reproduce it (as minimally and precisely as possible):
kind: Service apiVersion: v1 metadata: name: nginx annotations: service.beta.kubernetes.io/azure-load-balancer-tcp-idle-timeout: "3" spec: type: LoadBalancer loadBalancerIP: "22.214.171.124" ports: - name: http port: 80 targetPort: http - name: https port: 443 targetPort: https selector: app: nginx
kubectl create -f nginx.yaml kubectl get svc kubectl delete -f nginx.yaml kubectl get svc kubectl create -f nginx.yaml
Anything else we need to know?:
@feiskyer - The problem here seems that when we want to call
one of the strategies is to still construct our diff in case of a delete and exercise the
Generally speaking, whenever we update a loadbalancer with unsupported values on annotations, ensuring load balancer will fail resulting in an un-cleaned LB, this is a cross-provider issue.
lgtm. the delete operation should continue to do cleanup job even some wrong options are provided from users.