Avoid hardcoding the helm version #3

New Issue

jonny · 2020-12-15T03:34:02Z

jonny commented

2020-12-15 03:34:02 +00:00

At the moment the helm client is downloaded as part of the container image creation. Ideally the helm client should be delivered via a python library - however there doesn't appear to be a mature python helm library available.

Options here are:

Download multiple helm clients and offer a selection of the installed clients, with an option to download a version that is missing.
Use a check within k8s to determine the helm client to use, and then download this in the background and use it.
Ask the user to provide the helm version to use - possibly from a predefined list (or a lookup elsewhere?)

If performing a download beforehand, this will increase the size of the container image, which is not ideal - especially as it will essentially be unused space.

At the moment the helm client is downloaded as part of the container image creation. Ideally the helm client should be delivered via a python library - however there doesn't appear to be a mature python helm library available. Options here are: - Download multiple helm clients and offer a selection of the installed clients, with an option to download a version that is missing. - Use a check within k8s to determine the helm client to use, and then download this in the background and use it. - Ask the user to provide the helm version to use - possibly from a predefined list (or a lookup elsewhere?) If performing a download beforehand, this will increase the size of the container image, which is not ideal - especially as it will essentially be unused space.

jonny self-assigned this 2020-12-15 03:34:02 +00:00

jonny added the

enhancement

label 2020-12-15 03:38:10 +00:00

jonny commented

2020-12-18 09:22:55 +00:00

Not sure this is necessary for helm3 ... a version record doesn't appear to be held int he secret for the deployment. Might just be a case of ensuring the latest helm3 version is beng used.

Sign in to join this conversation.