Skip to content

Conversation

jukie
Copy link
Contributor

@jukie jukie commented Jul 2, 2025

What type of PR is this?
feat: default to 1 for MaxAcceptPerSocketEvent

What this PR does / why we need it:
It's recommended to set a value for MaxAcceptPerSocketEvent and 1 is a safe value with either negligible or zero performance impact which other Gateway Controllers use as well.

Which issue(s) this PR fixes:

Fixes #6439

Release Notes: No

@jukie jukie changed the title Add default=1 for MaxAcceptPerSocketEvent Default to 1 for MaxAcceptPerSocketEvent Jul 2, 2025
@jukie jukie marked this pull request as ready for review July 2, 2025 02:50
@jukie jukie requested a review from a team as a code owner July 2, 2025 02:50
Copy link

codecov bot commented Jul 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.87%. Comparing base (a394c61) to head (9b20f76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6447      +/-   ##
==========================================
- Coverage   70.92%   70.87%   -0.06%     
==========================================
  Files         220      220              
  Lines       37260    37263       +3     
==========================================
- Hits        26426    26409      -17     
- Misses       9289     9305      +16     
- Partials     1545     1549       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Signed-off-by: jukie <[email protected]>
@jukie jukie requested a review from rudrakhp July 2, 2025 04:48
jukie and others added 2 commits July 1, 2025 22:56
Co-authored-by: Rudrakh Panigrahi <[email protected]>
Signed-off-by: Isaac <[email protected]>
Signed-off-by: jukie <[email protected]>
Copy link
Member

@zirain zirain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, saw samething in Istio.

@jukie
Copy link
Contributor Author

jukie commented Jul 2, 2025

/retest

@rudrakhp rudrakhp enabled auto-merge (squash) July 2, 2025 06:54
@rudrakhp
Copy link
Member

rudrakhp commented Jul 2, 2025

/retest

@rudrakhp rudrakhp merged commit 752687d into envoyproxy:main Jul 2, 2025
48 of 50 checks passed
@jukie jukie deleted the max-conn-accept-per-socket-defaults branch July 2, 2025 13:34
davem-git pushed a commit to davem-git/gateway that referenced this pull request Jul 8, 2025
* Add default=1 for MaxAcceptPerSocketEvent

Signed-off-by: jukie <[email protected]>

* testdata

Signed-off-by: jukie <[email protected]>

* Fix default

Signed-off-by: jukie <[email protected]>

* Update internal/xds/translator/listener.go

Co-authored-by: Rudrakh Panigrahi <[email protected]>
Signed-off-by: Isaac <[email protected]>

* update const name

Signed-off-by: jukie <[email protected]>

---------

Signed-off-by: jukie <[email protected]>
Signed-off-by: Isaac <[email protected]>
Co-authored-by: Rudrakh Panigrahi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default to 1 for maxConnectionsToAcceptPerSocketEvent
3 participants