Repository navigation
feat: integrate gateway resilience and rate limiting - #22
Merged
Merged
Conversation
…nto feature/5-gateway-resilience-integration
This was referenced Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Integrate the reviewed API Gateway resilience stack into main: route-isolated circuit breakers, safe retry behavior, Redis-backed client rate limiting, fail-closed handling, Helm/image updates, and integration tests.
This PR is non-draft and does not merge directly to main.
Related work
Those PRs were merged into successive feature branches; #20 is on main, while #21 still requires this integration PR.
Verification
Merge guidance
Merge after review. config-repo#35 and #36 may merge before or after this PR; no delay is required. Roll out Gateway resilience only after the gateway and configuration changes are available together.