Configurable TCP Idle timeout limit does not match Azure limit

[JoelSpeed]

What happened:

Azure documents that the load balancer tcp idle timeout is configurable between 4 minutes and 100 minutes.

If you use the service.beta.kubernetes.io/azure-load-balancer-tcp-idle-timeout annotation on a service, and set the value to 100 minutes, an error is returned saying that the maximum value is 30 mins.

What you expected to happen:

100 minute value should be accepted and should be configured for the load balancer managed by the service.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Code to update looks to be here,

cloud-provider-azure/pkg/provider/azure_loadbalancer.go

Line 2634 in c18b82b

max = 30

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others:

[feiskyer]

Thanks for reporting the issue. This is a bug we should fix.