Ah good catch, thanks - will do.
We should probably also build a newer kubectl image to avoid violating the [version skew policy]([url](https://kubernetes.io/releases/version-skew-policy/#kubect…
Ok thanks for clarifying - it may be worth discussing this with the team to ensure everyone is aware, as this is a different strategy to rancher/charts which resets the version for each rancher…
This looks good but we'll need to bump the package version and build a new downloader/chart version
I'm also wondering if now is the time to consider if we can move away from maintaining…
@nbelouin since this will be the first chart release for 3.3 do we expec this to be %%CHART_MAJOR%%.0.0 until the release happens?
Note for other reviewers - I think this is a mistake introduced via 1048591769 - @nbelouin I guess that was from some debugging?