update hermes rate limit config - #12720
Merged
Merged
Conversation
LeoZhangZXZ
requested review from
Kuckkuck,
ashifnihalb,
ibakshay,
joluc,
notandy,
notque,
olandr,
richardtief,
timojohlo,
trouaux and
viennaa
as code owners
September 4, 2026 10:27
wiltongarcia
approved these changes
Sep 4, 2026
ibakshay
approved these changes
Sep 7, 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
3 participants
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.
Motivation
The Hermes API binary now supports per-token rate limiting. The helm chart needs to
expose the new config keys so regions can opt in without editing templates directly.
What Changed
hermes.rateLimitblock tovalues.yamlwith all six parameters (alldefault to 0 / disabled for backward compatibility).
RateLimit.*keys to_hermes.conf.tplso they are rendered intothe API config map.
Leave all at 0 to keep rate limiting disabled (the default).
Related PRs