Loki 3.x helm chart pushing to s3 properly?

Grafana Installation
1

Hi there.

I’ve been trying to migrate from loki-stack helm chart into grafana’s helm chart for loki 3.x.
I’m intending to use S3 for any kind of persistance, and not rest on PVC or Local Storage since everything else is ephemeral.

I’ve been successfuly doing so with the current loki-stack helm chart under loki 2.x, but when switching over to loki 3.x in grafana’s helm chart provisioning, there seems to exist an issue with S3 pusher part, which is only pushing repetitively index/index_20213/fake/1746497079574863599-compactor-1746480224109-1746496018802-3934612e.tsdb.gz (switching over to the new date parameters) and deleting the previous one, no other files seems to be uploded above the one mentioned.

This is my current configuration of Loki’s chart, can you help me troubleshoot what’s wrong?

deploymentMode: SingleBinary

loki:
  commonConfig:
    replication_factor: 2

  storage:
    bucketNames:
      chunks: $bucketname
      ruler: $bucketname
      admin: $bucketname
    type: s3
    s3:
      bucketnames: $bucketname
      region: us-east-1
      s3ForcePathStyle: false
      insecure: false

  storage_config:
    tsdb_shipper:
      active_index_directory: /var/loki/index
      cache_location: /var/loki/index_cache
      cache_ttl: 24h

  auth_enabled: false

  schemaConfig:
    configs:
      - from: 2020-10-24
        store: boltdb-shipper
        object_store: s3
        schema: v11
        index:
          prefix: index_
          period: 24h
      - from: "2025-04-08"   # migration to new loki helm chart
        index:
          period: 24h
          prefix: index_
        object_store: s3
        schema: v13
        store: tsdb

singleBinary:
  enabled: true
  persistence:
    enabled: true

read:
  enabled: false
write:
  enabled: false
backend:
  enabled: false
gateway:
  enabled: false
chunksCache:
  enabled: false
resultsCache:
  enabled: false
2

I came across too many different references, official one refers to snippets that do not work with actual 3.4 helm charts, but the key seems to be located at whether using thanos config format.

Anyone else faced similar issues when upgrading from previous loki versions with existing persistance on S3 only and nothing local?