Skip to content

feat: ability to set status for destination not found in stateful session#44210

Merged
phlax merged 5 commits into
envoyproxy:mainfrom
rudrakhp:strict_stateful_session_status_notfound
Apr 14, 2026
Merged

feat: ability to set status for destination not found in stateful session#44210
phlax merged 5 commits into
envoyproxy:mainfrom
rudrakhp:strict_stateful_session_status_notfound

Conversation

@rudrakhp
Copy link
Copy Markdown
Member

@rudrakhp rudrakhp commented Apr 1, 2026

Commit Message: feat: ability to set status for destination not found in stateful session
Additional Description: Follow up for #43944 to add the status_on_strict_destination_not_found to allow users to define status to respond with if strict destination doesn't exist.
Risk Level: Low (new API)
Testing: Unit testing
Docs Changes: N/A
Release Notes: Yes
Platform Specific Features: N/A
Fixes: #42686

@repokitteh-read-only
Copy link
Copy Markdown

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to (api/envoy/|docs/root/api-docs/).
envoyproxy/api-shepherds assignee is @mattklein123
CC @envoyproxy/api-watchers: FYI only for changes made to (api/envoy/|docs/root/api-docs/).

🐱

Caused by: #44210 was opened by rudrakhp.

see: more, trace.

…sion

Signed-off-by: Rudrakh Panigrahi <rudrakh97@gmail.com>
@rudrakhp rudrakhp force-pushed the strict_stateful_session_status_notfound branch from bce1e8f to ce2bca6 Compare April 1, 2026 22:10
mattklein123
mattklein123 previously approved these changes Apr 4, 2026
@repokitteh-read-only repokitteh-read-only Bot removed the api label Apr 4, 2026
@mattklein123
Copy link
Copy Markdown
Member

Needs main merge otherwise lgtm, thanks.

/wait

@rudrakhp
Copy link
Copy Markdown
Member Author

rudrakhp commented Apr 4, 2026

/retest

Copy link
Copy Markdown
Member

@phlax phlax left a comment

Choose a reason for hiding this comment

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

@rudrakhp very minor docs literal nit - then should be good to land

// The HTTP status code to return when ``strict`` mode is enabled and the requested destination
// is not found in the set of available endpoints. This does not apply when the destination exists
// but is unhealthy. This field has no effect when ``strict`` is set to ``false`` and will be
// ignored. Defaults to 503 (Service Unavailable) if not specified or set to 0.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
// ignored. Defaults to 503 (Service Unavailable) if not specified or set to 0.
// ignored. Defaults to ``503`` (Service Unavailable) if not specified or set to ``0``.

@phlax phlax self-assigned this Apr 14, 2026
Signed-off-by: Rudrakh Panigrahi <rudrakh97@gmail.com>
@rudrakhp rudrakhp requested a review from phlax April 14, 2026 12:56
Copy link
Copy Markdown
Member

@phlax phlax left a comment

Choose a reason for hiding this comment

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

lgtm, thanks @rudrakhp

@phlax phlax enabled auto-merge (squash) April 14, 2026 13:11
@rudrakhp
Copy link
Copy Markdown
Member Author

/retest

@phlax phlax merged commit 15d9bde into envoyproxy:main Apr 14, 2026
27 of 29 checks passed
krinkinmu pushed a commit to grnmeira/envoy that referenced this pull request Apr 20, 2026
…sion (envoyproxy#44210)

Signed-off-by: Rudrakh Panigrahi <rudrakh97@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

stateful session header handling in strict mode when requested destination is not available

3 participants