Open
Conversation
Add a new Size Limits section specifying that Cloud Controller must enforce a configurable maximum size (default: 1 KB) for route options to prevent excessive NATS bandwidth consumption. - Default limit: 1024 bytes - Configurable via cc.max_route_options_size BOSH property - CC returns HTTP 422 when limit is exceeded - Documents relationship with route emit interval for tuning This addresses feedback from the App-to-App mTLS RFC (PR #1438) where concerns were raised about NATS bandwidth impact of per-route options.
maxmoehl
reviewed
Mar 6, 2026
Member
maxmoehl
left a comment
maxmoehl
left a comment
There was a problem hiding this comment.
Thanks for preparing this amendment. I like it overall, just 1.5 small comments.
Co-authored-by: Maximilian Moehl <44866320+maxmoehl@users.noreply.github.com>
- Remove duplicate 'Operator guidance' line from suggestion merge - Change 'bandwidth usage' to 'resource usage' for consistency - Add note that lowering size limit doesn't affect existing routes
Member
|
We start the final comment period with the goal to accept this change to RFC-27 on 17.3. |
|
I like that this is controlled at the operator level |
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
5 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.
Summary
Adds a Size Limits section to RFC-0027 (Generic Per-Route Features) specifying that Cloud Controller must enforce a configurable maximum size for route options.
Changes
cc.max_route_options_sizeBOSH propertyContext
This addresses feedback from the App-to-App mTLS RFC (PR #1438) where @maxmoehl raised concerns about NATS bandwidth impact of per-route options. The discussion concluded that a global size limit enforced at the Cloud Controller level (with immediate user feedback) is the appropriate solution.
Rationale
Route registration messages are transmitted via NATS at a configurable interval from each app instance to each GoRouter instance. Large route options can significantly impact NATS bandwidth in deployments with many app instances. A 1 KB default accommodates most use cases (e.g., ~25 app GUIDs in an mTLS allowlist) while protecting platform stability.
cc @maxmoehl