Bug description
The bug is that hostAliases is not added to superset init job in helm deployment. According to comment the hostAliases should be added to all pods in the deployment, but that isn't the case for the pod doing the initialization (init in the helm chart). I would assume that it is unintended, as it makes certain use cases (custom networking, Google cloud sql proxy) practically impossible to use.
Expected behavior: hostAliases are added also the the init job pod
That is currently not the case on the current master. If needed I could also try to provide a patch for that.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.