Skip to content

feat(grpc): add configurable maximum size limit for received gRPC messages#3048

Merged
migmartri merged 2 commits intochainloop-dev:mainfrom
corang:feat/grpc-configurable-size-limit
Apr 20, 2026
Merged

feat(grpc): add configurable maximum size limit for received gRPC messages#3048
migmartri merged 2 commits intochainloop-dev:mainfrom
corang:feat/grpc-configurable-size-limit

Conversation

@corang
Copy link
Copy Markdown
Contributor

@corang corang commented Apr 16, 2026

Adds a configurable max_recv_msg_size option to the controlplane gRPC server, allowing operators to increase the default 4MB message size limit. This resolves ResourceExhausted errors when pushing attestations larger than 4MB (e.g., attestations with large SBOMs or SARIF reports).

The setting is exposed end-to-end:

  • Proto config field on Server.GRPC
  • Applied as a gRPC server option in the controlplane
  • Configurable via Helm with controlplane.grpcMaxRecvMsgSize

When unset, the standard gRPC default of 4MB applies.

Example Helm usage:

controlplane:
  grpcMaxRecvMsgSize: 16777216  # 16MB

…sages

Signed-off-by: Jordan McClintock <jordan@defenseunicorns.com>
@corang corang force-pushed the feat/grpc-configurable-size-limit branch from e6c1b4a to 561ae62 Compare April 16, 2026 20:08
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 6 files

Copy link
Copy Markdown
Member

@migmartri migmartri left a comment

Choose a reason for hiding this comment

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

LGTM, please fix the conflict and let me know.

BTW, while testing your PR we noticed some mayor improvements in the attestation #3056 push payload that will reduce the size of that payload ~60%. What API calls were causing you the error?

Signed-off-by: Jordan McClintock <jordan@defenseunicorns.com>
@corang
Copy link
Copy Markdown
Contributor Author

corang commented Apr 20, 2026

LGTM, please fix the conflict and let me know.

BTW, while testing your PR we noticed some mayor improvements in the attestation #3056 push payload that will reduce the size of that payload ~60%. What API calls were causing you the error?

It was just using the chainloop attestation push command but there are a lot of pieces of evidence and an entire other attestation attached to it so I think it's just gonna be large regardless. Fixed that conflict too!

@migmartri migmartri merged commit bb484cd into chainloop-dev:main Apr 20, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants