Skip to content

read only index stored in aws s3 bucket #795

Open
@chrislin22

Description

As I understand, ChartMuseum supports AWS S3 as a backend for storing charts and the index.yaml file in the same S3 bucket.

The challenge we are facing is that we have multiple ChartMuseum instances sharing the same AWS S3 bucket as their backend. Is there any plan to support a setup where one instance handles indexing and stores the index.yaml in the S3 bucket, while all other instances simply read the index file?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions