Description of problem:

In the resolver caching mechanism (implemented via SRVKP-8880) causes the global cache configuration to take precedence over specific resolver configurations. Even when a specific resolver (e.g., bundleresolver-config) is configured with a shorter TTL, the system defaults to the resolver-cache-config global TTL value.

Prerequisites (if any, like setup, operators/versions):

OSP 1.21

Pipelines v1.6.0

Steps to Reproduce

• Configure Global TTL: Set the global resolver-cache-config TTL to 10m.
  YAML
  pipeline:
  options:
  configMaps:
  resolver-cache-config:
  data:
  max-size: "1000"
  ttl: 10m
• Configure Specific Resolver TTL: Set the bundleresolver-config (or git-resolver) TTL to a shorter duration, e.g., 5m.
  YAML
  configMaps:
  bundleresolver-config:
  data:
  max-size: "1000"
  ttl: 5m
• Trigger a PipelineRun: Execute a pipeline using the bundle resolver.

• Check the expiration timestamp assigned to the cached object.

Actual results:

{"severity":"info","timestamp":"2026-01-09T06:18:31.844Z","logger":"controller","caller":"cache/cache.go:96","message":"Adding to cache","commit":"b69b57da43d37038b1447b346ad96a88b29d3ccb","knative.dev/traceid":"81041876-c449-4cf5-a5af-815cc9be7c85","knative.dev/key":"test/bundles-204049d476c25be4ca9f163dea91115b","key":"73bb02fbf3fe71bcfb897949a29c9a7c9621e113009bbc65033979f85e73c810","expiration":600}

Expected results:

expiration:300

Reproducibility (Always/Intermittent/Only Once):

Always

 *