kainz commented on issue #32733:
URL: https://github.com/apache/superset/issues/32733#issuecomment-3070386484
> Anyone here interested in opening a PR to resolve this? If not, I think we
might just call the question answered and close the Issue as "not planned"
> Best solution/workaround is to checkout the branch related to the image
you're working with/on.
I believe there is a root problem here in that if you are *not* building a
custom image, the standard images do not work with the helm chart. I can dig a
bit later (tomorrow, probably) and produce a reproduction with a better
illustration of the issue.
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?
If the answer is to support the generic case, either the docs should be
adjusted, or the 'lean' image should have uv added.
- For the docs side, is a different distributed image a better fit than the
lean image?
- On the image adjustment side, is the cost of adding uv to the 'lean'
image untenable for some reason?
If the answer is to only support the specific case, whatever that case is,
and its narrower applicability should be noted in the documentation, I believe.
--
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
