NickLarsenNZ opened a new issue, #24219: URL: https://github.com/apache/superset/issues/24219
The helm hook job is not uniquely named, and gets replaced if multiple releases are deployed in the same namespace. #### How to reproduce the bug ```sh helm repo add superset https://apache.github.io/superset helm repo update helm upgrade --install my-release superset/superset --namespace default ``` ### Expected results All resources to be prefexed with `my-release-` ### Actual results The `superset-init-db` hook Job is not prefixed with `my-release-`. #### Screenshots <img width="802" alt="image" src="https://github.com/apache/superset/assets/10092581/1b336c29-a5c3-4aee-b562-f143d464f4e9";> ### Environment - browser type and version: N/A - superset version: `2.1.0` (Helm Chart `0.10.0`) - python version: N/A - node.js version: N/A - any feature flags active: N/A ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [x] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [x] I have reproduced the issue with at least the latest released version of superset. - [x] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context None -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
