[Housekeeping] Use single configuration option for maximum blobstore size #4487
Labels
backlogged
For internal use. Reserved for contributor team workflow.
exo
housekeeping
Issues that help maintain flyte and keep it tech-debt free
Describe the issue
Currently there are multiple configuration values for the maximum size for a blobstore file between I/O writing, dynamic closure offloading, etc.
What if we do not do this?
Users frequently run into issues with increasing the maximum size with unclear instructions on what values need to change.
Related component(s)
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: