read only index stored in aws s3 bucket
Open
- Dominant language
- Go
- Stars
- 3.8k
- Forks
- 407
- PR merge metrics
- No merged PRs in 30d
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?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.