Sitelet https://github.com/istio/api/pull/3798
Skip to content

docs: clarify maxConnections applies to HTTP/2 - #3798

Open
git-jxj wants to merge 1 commit into
istio:masterfrom
git-jxj:docs/tcp-max-connections
Open

git-jxj wants to merge 1 commit into
istio:masterfrom
git-jxj:docs/tcp-max-connections

Conversation

@git-jxj

@git-jxj git-jxj commented Oct 2, 2026

Copy link
Copy Markdown

The maxConnections reference currently mentions HTTP/1 and TCP, suggesting that HTTP/2 connections are excluded. Clarify that HTTP/1.1 and HTTP/2 connections count toward the limit, and link to Envoy's explanation of why the circuit breaker threshold can be exceeded.

Regenerate the reference, Go comments, and CRD descriptions. The CRD validation schema is unchanged.

Fixes #3509.

Validation: make gen, buf lint, make test, and generated HTML checks. The documentation check fails on the original reference and passes after regeneration.

@git-jxj
git-jxj requested a review from a team as a code owner October 2, 2026 08:42
@istio-policy-bot

Copy link
Copy Markdown

🤔 🐛 You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?

Courtesy of your friendly test nag.

@istio-testing istio-testing added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test labels Oct 2, 2026
@istio-testing

Copy link
Copy Markdown
Collaborator

Hi @git-jxj. Thanks for your PR.

I'm waiting for a istio 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

Details

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.

1 similar comment
@istio-testing

Copy link
Copy Markdown
Collaborator

Hi @git-jxj. Thanks for your PR.

I'm waiting for a istio 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: Clarify DestinationRule spec.trafficPolicy.connectionPool.tcp.maxConnections

5 participants