read only index stored in aws s3 bucket

[chrislin22]

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?

[scbizu]

Is it #545 ?

[chrislin22]

Not too sure - Ideally, will be one chartm do the index and store directly inside the s3 and all other chartm read fro it?

[scbizu]

AFAIK Currently not , but you can do sth tricky to block the other CM server's w API at L7 proxy maybe , but it still has the similar issue like #545 like if your's w is OK but r cannot read the correct version of chart .