We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have a function which when run asynchronously causes NATS to return this error:
nats: maximum payload exceeded
This is set to 1MB by default: https://nats.io/documentation/faq/#msgsize
And there doesn't appear to be a way to change this in the Helm chart.
The text was updated successfully, but these errors were encountered:
Derek set title: Suggestion: add NATS Streaming maximum payload option to helm chart
Sorry, something went wrong.
Hi are you willing to look into this for yourself?
Generally I'd advise you use S3 or Minio to store large payloads for asynchronous requests.
Alex
@jpds if this is A) possible and B) you want to do this work then go ahead.
/lock: closing as inactive. Feel free to raise a new issue if this is still required
No branches or pull requests
Current Behaviour
We have a function which when run asynchronously causes NATS to return this error:
This is set to 1MB by default: https://nats.io/documentation/faq/#msgsize
And there doesn't appear to be a way to change this in the Helm chart.
The text was updated successfully, but these errors were encountered: