New RunLLM response generated: >>>*# Question* Are these configs helm-able? https://docs.flyte.org/projects/flytectl/en/latest/gen/flytectl_get_workflow-execution-config.html do they live in config-maps somewhere # Answer Yes, these configurations can be managed via Helm. Flyte configurations, including those for workflow execution, are typically specified in ConfigMaps, which can be managed and deployed using Helm. For example, the

flyte-propeller-config

ConfigMap includes various configurations for Flyte, such as the

max-output-size-bytes

parameter. You can modify these configurations in your Helm values file and apply them using Helm. Here is an example of how you might specify configurations in a Helm values file:

configmap:
  core:
    propeller:
      max-output-size-bytes: 10485760

This would then be rendered into the

flyte-propeller-config

ConfigMap when you deploy Flyte using Helm. According to the Flyte Helm configuration, you can manage various configurations, including those for the Flyte scheduler, Flyte console, and Flyte data catalog, through Helm values. Would you like more detailed steps on how to configure these settings using Helm? Sources: - Flyte Helm configuration - Flyte Propeller ConfigMap Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1720721445.262129 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.