Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi! After bumping flyte from v1.5.0 to v1.6.0 I found that the task resource config doesn’t propagate to AWS Batch Job’s resource config, I define CPU and memory like this:
```@task(requests=Resources(mem="16Gi", cpu="8"), task_config=AWSBatchConfig(platformCapabilities="EC2"))```
But in AWS batch it’s always 1 vcpu and 1049 mem
Any idea why?

<@USU6W5ATA> Sorry for the ping, but do you have any idea?

what’s the resource limit in flyteadmin configmap

I didn’t set one, I only set:
```  task_resource_defaults:
    task_resources:
      defaults:
        cpu: 1000m
        memory: 1000Mi
        storage: 1000Mi
      limits:
        cpu: 256
        memory: 512Gi
        storage: 512Gi```

No luck, seems like it’s only using the default values

Do you know why or should I create an issue? <@USU6W5ATA>