Docs: How to modify NLB TCP timeout.

[hrdkmshra]

What this PR does / why we need it:

Updates documentation regarding TCP idle timeout configuration for Network Load Balancers (NLB). The current documentation states that the timeout cannot be modified. This PR updates this information to reflect that the TCP idle timeout is configurable, helping users who need to adjust timeout values for their specific use cases.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

How Has This Been Tested?

aws elbv2 modify-listener-attributes \
        --listener-arn <listner-arn> \
        --attributes Key=tcp.idle_timeout.seconds,Value=4999

Used the following TLS termination in AWS Load Balancer manifest

It updates the TCP idle timeout value.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: hrdkmshra (1fdb3f0, 263d267, 51eea3a)

[k8s-ci-robot]

Welcome @hrdkmshra!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @hrdkmshra. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx ready!

Name	Link
🔨 Latest commit	263d267
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/68067eab9fe1370008450a06
😎 Deploy Preview	https://deploy-preview-13242--kubernetes-ingress-nginx.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hrdkmshra]

References :

1. https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout

Note :

There are few things that I noticed :

1. Regarding the following annotation in TLS termination in AWS Load Balancer manifest it doesn't affect the actual TCP idle timeout settings in the NLB listeners. Changes to this value in the manifest do not propagate to the NLB listener configuration either.

service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "60"

Please feel free to correct my understanding if I have misunderstood.

[Gacko]

/retitle Docs: How to modify NLB TCP timeout.
/triage accepted
/kind documentation
/priority backlog
/lgtm

[Gacko]

/cherry-pick release-1.12

[Gacko]

/cherry-pick release-1.11

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.12

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.11

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-sigs/prow repository.

[Gacko]

Please sign the CLA, otherwise we cannot accept your proposal and will close this PR within a week.

[Gacko]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gacko, hrdkmshra

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:

• docs/OWNERS [Gacko]

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

[hrdkmshra]

thank you Gacko@ for having a look, I have completed my signup for CLA and made some minute changes again.

[Gacko]

/unhold

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #13249

In response to this:

/cherry-pick release-1.12

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #13250

In response to this:

/cherry-pick release-1.11

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-sigs/prow repository.