Skip to content

Conversation

@kimiyasharifi
Copy link

Add MaxConnectionsToAcceptPerSocketEvent to EnvoyListenerConfig

  • Introduce MaxConnectionsToAcceptPerSocketEvent in ListenerParameters struct.
  • This allows configuring the maximum connections accepted per socket event in Envoy listener.

@kimiyasharifi kimiyasharifi requested a review from a team as a code owner November 9, 2025 11:09
@kimiyasharifi kimiyasharifi requested review from sunjayBhatia and tsaarni and removed request for a team November 9, 2025 11:09
@sunjayBhatia sunjayBhatia requested review from a team, izturn and rajatvig and removed request for a team November 9, 2025 11:10
@github-actions
Copy link

github-actions bot commented Nov 9, 2025

Hi @kimiyasharifi! Welcome to our community and thank you for opening your first Pull Request. Someone will review it soon. Thank you for committing to making Contour better. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace

kimiyasharifi and others added 2 commits November 9, 2025 15:13
…alue

MaxConnectionsToAcceptPerSocketEvent is a *wrapperspb.UInt32Value in EnvoyListenerConfig,
so wrap the uint32 value using wrapperspb.UInt32() to fix the type mismatch
and prevent compilation errors.
@kimiyasharifi kimiyasharifi force-pushed the add/max-connections-to-accept-param branch from 4cbba23 to 4ebb517 Compare November 16, 2025 07:12
Copy link
Member

@sunjayBhatia sunjayBhatia left a comment

Choose a reason for hiding this comment

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

This PR looks like it currently includes unrelated changes to the title/description and deletes the existing github workflow files

To get this in we'll need some cleanup on the diff to only include relevant changes

@github-actions
Copy link

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 60d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

  • Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
  • Mark this PR as fresh by commenting or pushing a commit
  • Close this PR
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants