For our integration test we would also need an image with kubectl and helm installed, not just helm.
Maybe the charts image can provide different kubectl versions, which then can be targeted via creating a link as first step
You can add a helper script that each workflow calls in order to set the correct symlink for the versions that it needs.
That would also make sense for helm, because Helm v3 is at the moment is stored in the charts image as helm and Helm v4 as helmv4 which mean we would need to adapt our CI to use a different binary for for different versions.
For our integration test we would also need an image with
kubectlandhelminstalled, not just helm.Maybe the charts image can provide different
kubectlversions, which then can be targeted via creating a link as first stepYou can add a helper script that each workflow calls in order to set the correct symlink for the versions that it needs.
That would also make sense for helm, because Helm v3 is at the moment is stored in the charts image as
helmand Helm v4 ashelmv4which mean we would need to adapt our CI to use a different binary for for different versions.