Repository navigation
feat: add Redis-backed gateway rate limiting - #21
Merged
ramioooz merged 4 commits intoSep 1, 2026
Merged
Conversation
Member
Author
|
Follow-up CI fix
Verification:
Related project task: |
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
RequestRateLimitersupport for public customer and account routes.config-repo/api-gateway/api-gateway-sit.yml.0.0.3and Helm chart to0.3.0.Verification
./mvnw --batch-mode clean verify -qhelm lint helm --stricthelm template api-gateway helm --values helm/values-sit.yaml429 Too Many Requests.Project Tracking
api-gateway#4(Redis-backed rate limiting).Related PRs and merge order
infra-sit#23for the shared Redis service.api-gateway#20for the gateway resilience baseline.config-repo#35for the gateway resilience configuration.mainonceapi-gateway#20is merged.config-reporate-limit configuration PR.There is no fixed delay between merges; wait for CI and confirm the prerequisite deployment/configuration is available before the next rollout.