Hey there,
in the documentation under Notes on index.yaml it says that chartmuseum should recognize if a chart is added/delete to the s3 bucket. In our use case the CD pipelines push helm charts directly to the s3 bucket and we only use chartmuseum to access these helm charts in a k8s cluster. Our problem is that the new charts are not recognized by chartmuseum and the index.yaml updates only if the pod is restarted.

Here are our values for the chartmuseum helm chart

env:
      open:
        STORAGE: amazon
        STORAGE_AMAZON_BUCKET: "*****"
        STORAGE_AMAZON_PREFIX: "******"
        STORAGE_AMAZON_REGION: "eu-central-1"
        DEBUG: true
      existingSecret: chartmuseum-s3
      existingSecretMappings:
        AWS_ACCESS_KEY_ID: ******
        AWS_SECRET_ACCESS_KEY:  ******
      securityContext:
        enabled: true
        fsGroup: 65534

Is there any magic trick to enable this because it would be a deal breaker for us