How do I specify

core.propeller.max-output-size-bytes

? It is not exposed by the

values.yaml

file

The

core.propeller.max-output-size-bytes

parameter has been deprecated in favor of the

storage.limits.maxDownloadMBs

configuration. This new setting is not directly exposed in the

values.yaml

file, but you can add it using the

configuration.inline

field or by editing the

storage.yaml

section in your deployment configuration. For example, add the following to your configuration:

storage:
  limits:
    maxDownloadMBs: 100

This approach is confirmed in recent discussions and PRs, which clarify that

max-output-size-bytes

should no longer be used and that

maxDownloadMBs

is the supported way to set the maximum output size for blobs in FlytePropeller and related components. You may need to manually add this to your config if it is not present in your chart's

values.yaml

file or use the

inline

configuration override if supported by your deployment method. See the linked sources for more details and examples. Would you like more detail on how to apply this in a specific deployment (e.g., Helm, Flyte-binary, or Flyte-core)? Sources: - Flyte issue: limit exceeded. 5.357096mb > 2mb. with Flyte-binary Chart 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

all good