Increase service idle max timeout to 100 minutes

[JoelSpeed]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Resolves #4360 by increasing the allowed limit inline with Azures updated limits

Which issue(s) this PR fixes:

Fixes #4360

Special notes for your reviewer:

This limit has been increased on the Azure side and is documented now as 100 minutes maximum, links in the attached issue

Does this PR introduce a user-facing change?

Increase limit for TCP Idle Timeout to 100 minutes

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[feiskyer]

Thanks for the fix.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feiskyer, JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [feiskyer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[feiskyer]

/cherry-pick release-1.27

[k8s-infra-cherrypick-robot]

@feiskyer: once the present PR merges, I will cherry-pick it on top of release-1.27 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.27

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[feiskyer]

/cherry-pick release-1.26

[k8s-infra-cherrypick-robot]

@feiskyer: once the present PR merges, I will cherry-pick it on top of release-1.26 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.26

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[feiskyer]

/cherry-pick release-1.25

[k8s-infra-cherrypick-robot]

@feiskyer: once the present PR merges, I will cherry-pick it on top of release-1.25 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.25

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-infra-cherrypick-robot]

@feiskyer: new pull request created: #4383

In response to this:

/cherry-pick release-1.27

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-infra-cherrypick-robot]

@feiskyer: new pull request created: #4384

In response to this:

/cherry-pick release-1.26

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-infra-cherrypick-robot]

@feiskyer: new pull request could not be created: failed to create pull request against kubernetes-sigs/cloud-provider-azure#release-1.25 from head k8s-infra-cherrypick-robot:cherry-pick-4361-to-release-1.25: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","field":"head","code":"invalid"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-1.25

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.