Superset - Possibility define a custom image, ressources and to create a route instead of an ingress in a openshift context

[djadeau]

Hello Onyxia team,

I was facing problems to deploy a superset instance in an openshift cluster.

• in the UI, it was not possible to define a custom image
• It was not possible to define ressources. The superset worker requires more resources than the other components
• In our openshift instance, we have to define a route instead of an ingress to access to the superset UI. The superset helm templace seems to ignore the route block in the yaml.

I can contribute to improve this helm in order to address those issues. Before I start, do you have recommendations or suggestions in the way to implement it?

Thank you.

[ihiverlet]

Hi,
Thank you for opening the issue ! Contributions are always welcome :)
I'll suppose you are familiar with onyxia related charts, tell me if it's not the case. Regarding your needs you mainly need to modify the values.schema.json file.

For the first point, what do you think about offering a text field to specify the image name, along with a list to indicate whether to pull the image from a registry ?

Maybe the route template from library-chart can be used here as we already have a dependency to library-chart. For inspiration, you can look at our vscode-python chart for Route creation and the corresponding vaules.schema.json

Finally, the chart version needs to be bumped to release it.

Please tell me if you have any question

[djadeau]

Hello!
Yes, I'm familiar with Onyxia, our team has already published some changed because we run it on Openshift.

Yep, the text field to specify the image name and the registry is a good way !

Thank you !