mistercrunch commented on PR #27434: URL: https://github.com/apache/superset/pull/27434#issuecomment-2000763254
Thinking about it some more, knowing that docker-compose is designed (AFAIK) as a single-host solution, I don't think it's fair to call this "production" by any standard around high availability. Knowing that in most setting you'd grow a need for multi-host support, either to support HA or as usage/demand would grow to where it can't be served by a single host, I think trying to support production-type use cases with docker-compose is doing a disservice to people in the community. What i'd suggest as a stance for maintainers is: - docker-compose is great and supported for development use cases - here we aim for simplicity and reproducibility - we don't recommend that you'd use them OR modify them for production use cases - for production support, we recommend k8s and offer a helm chart. We also offer a variety of multi-platform docker images pointing to releases that you can use. We do not offer higher level construct like terraform scripts at this time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
