superset helm should use charts.appversion, not dockerize

[mpechner-akasa]

Bug description

helm/superset/values.yaml
Change valuefile:
initImage:
repository: apache/superset
tag: dockerize
pullPolicy: IfNotPresent

change template so tag is "{{ .Charts.ApppVersion }}-dockerize"

I ran into image caching when update to 0.14.2 and the dockerize image was version 4.1.1.

Not a dockerhub image. But we use ECR dockerhub proxy and it is an issue.

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• 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.

[mpechner-akasa]

I'lll be happy to do the PR if you agree this is an issue

[rusackas]

PRs always welcome, of course! I'm no helm expert, so I've assigned @villebro who knows more about the best practices here.

[mpechner-akasa]

Standard is not to use a tag like latest or dockerize due to caching.
Set version of the various components in Charts.xml, then in the helm chart templates make use of these variables.

Again, once you look and decide this should be done, I'll be happy to get it done.
Not big on Random PRs when a main contributor has not agreed.

[mpechner]

@villebro if I do the PR, will it be accepted?

[mistercrunch]

@mpechner-akasa yes, happy to review/merge if the solution works. Sounds like there are newer/better patterns instead of dockerize, happy to review/merge the fix to dockerize or some other solution that replaces it.

[mpechner-akasa]

Thank you will get it done in the next couple of months. I tend to only work on these on the weekends. i had a keda issue I am trying to work on.

[mistercrunch]

Related -> #23103 which mentions concerns around dockerize and numerous CVEs.

I asked Claude for input as to whether those issues are still ongoing -> https://claude.ai/share/b1476d0d-ff02-4c9e-8e6e-7984b7092010

Seems dockerize is an somewhat viable state for us to keep using, but we want to consider alternatives.

[mpechner-akasa]

Not saying to not use dockerize. just adding a version to the tag dockerize so pod caching does not cause an issue of a pod not being replaced.

[rusackas]

Is there still interest in carrying this forward with a PR? Sorry, I'm no helm guru, but would love to either find a way to make this actionable or close it out :D