Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

read only index stored in aws s3 bucket #795

Open
chrislin22 opened this issue Dec 12, 2024 · 0 comments
Open

read only index stored in aws s3 bucket #795

chrislin22 opened this issue Dec 12, 2024 · 0 comments

Comments

@chrislin22
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant