You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: