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

Flyte

Can it be that there is a bug in the flyte-core helm charts?

The readme seems to say to use `flytepropeller.cacheSizeMbs` to configure the cache

which generates <https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/templates/propeller/configmap.yaml#L50-L53|this cache.yaml>

```cache.yaml: |
    cache:
      max_size_mbs: {{ .Values.flytepropeller.cacheSizeMbs }}
      target_gc_percent: 70```
But for me that didn't enable caching because `storage` is missing.
Adding

```configmap:
  core:
    storage:
      cache:
        max_size_mbs: 5000
        target_gc_percent: 70```
to my `values.yaml` enabled the caching.

And for your workload please use a bigger propeller

Great, thanks. Anyway I've opened <https://github.com/flyteorg/flyte/pull/5739> to see if this is indeed a bug in the helm chart.