billions-hairdresser-78656
04/24/2025, 9:52 PM<jemalloc>: MADV_DONTNEED does not work (memset will be used instead)
<jemalloc>: (This is the expected behavior if you are running under QEMU)
Running Execution on Remote.
Request rejected by the API, due to Invalid input.
RPC Failed, with Status: StatusCode.INVALID_ARGUMENT
Details: Requested MEMORY default [2Gi] is greater than current limit set in the platform configuration [1Gi]. Please contact Flyte Admins to change these limits or consult the configuration
Researching I see that there are several configMaps that can be modified:
• flyte-admin-base-config
• flyte-admin-clusters-config
• flyte-clusterresourcesync-config
Could you tell me some doc or how to correctly configure these parameters?average-finland-92144
04/29/2025, 6:50 PMconfiguration:
inline:
task_resources:
defaults:
cpu: 500m #example values
memory: 500Mi
storage: 500Mi
The above assumes you are using flyte-binary. Also as you may noticed, it doesn't specify limits but just default resource requests. If you need to limit resource consumption at the project-domain level, setting ResourceQuotas can be a better pattern.
Let me know if this helps or if you are using Flyte Helm chart as the config is located in a different section