Expected Behavior

Users should be able to configure cache_ttl_seconds and cache_mode for file-based registries, similar to how it works for DB-based registries.

Current Behavior

The Feast Operator CRD does not support configuring cache_ttl_seconds and cache_mode registry settings when using file-based registry persistence. These settings are important for controlling registry caching behavior and are supported by the Feast Python SDK, but cannot be set via the operator CRD for file-based registries.

This works fine for when using a database-backed registry (SQL or Snowflake), you can configure cache_ttl_seconds and cache_mode via secrets. This works because DB-based registry configurations pass through all secret parameters via DBParameters in the operator's RegistryConfig struct.

There's no mechanism to pass additional registry configuration parameters.

Possible Solution

Option 1: Add fields to RegistryFilePersistence

spec:
  services:
    registry:
      local:
        persistence:
          file:
            path: s3://bucket/registry.db
            cache_ttl_seconds: 60
            cache_mode: sync

Option 2: Add a generic config field

spec:
  services:
    registry:
      local:
        persistence:
          file:
            path: s3://bucket/registry.db
            config:
              cache_ttl_seconds: 60
              cache_mode: sync