Correct max val. of azure-load-balancer-tcp-idle-timeout

[atakadams]

This updates the max value description of service.beta.kubernetes.io/azure-load-balancer-tcp-idle-timeout from 30 to 100. Previously the max value was limited to 30 but now it's incresed to fit the underlying ALB capability.

Configurable TCP Idle timeout limit does not match Azure limit https://github.com/kubernetes-sigs/cloud-provider-azure/issues/4360

Increase service idle max timeout to 100 minutes https://github.com/kubernetes-sigs/cloud-provider-azure/pull/4361

[prmerger-automator[bot]]

@atakadams : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 87ed7dc:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/aks/load-balancer-standard.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@asudbring

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[Nickomang]

Thanks for the feedback, @atakadams! At this time, we're in the process of migrating this content to a new repository. I'll be closing this pull request for now, but I will follow up over the next few weeks with details on how you can re-open the changes against the new repo. We appreciate the patience as we finalize the migration.

#please-close

[Nickomang]

@atakadams , We’re happy to share that contributions to AKS are once again possible at MicrosoftDocs/azure-aks-docs. We appreciated your patience during this migration.

To re-open your contribution, follow these steps:

1. Fork and clone the new repository MicrosoftDocs/azure-aks-docs.
2. Create a new branch in your fork.
3. Copy the raw markdown for each file touched in your original PR.
4. In your fork’s new branch, paste each markdown file.
5. Commit the changes and open a new PR against the MicrosoftDocs/azure-aks-docs main branch.