mistercrunch commented on issue #32733: URL: https://github.com/apache/superset/issues/32733#issuecomment-3071376017
Oh right, my comment assumed [wrongly] that it was a docker-compose-related issues where clearly the issue is about k8s/helm. > I think a good question to ask is: Is the superset team invested in Kubernetes instructions that work with a wide array of possible configurations, or only a single prototypical or example configuration? Totally fair. On the www.preset.io side (represents a fair % of the active/sponsored committers), we forked the helm chart a long time ago and aren't using the helm chart in the repo, so we're not actively maintaining it. The reality is that it's extremely difficult to support the variety of custom requirement everyone has in their own environments (different metadata database, need for different analytics database drivers, different MQ systems for Celery, different observability stacks, ...). All this becomes really hard to make fully configurable, especially given that Superset is a fairly complex collection of services that are individually highly configurable... My take, based on the activity in the repo, is that we should clarify a limited commitment on the "single prototypical or example configuration" (as you put it), or a simple/vanilla "reference implementation". Essentially assuming that you should probably just fork the helm chart and customize it to suit your needs. -- 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
