Use system helm instead the packaged one

[ogarcia]

What would you like to be added:
A new config entry to set the path to helm binary.

Why is this needed:
Because you can provide more tiny application that don't need to include a 47MB binary.

Environment you are Lens application on:

• Kubernetes distribution: AKS
• Desktop OS: Arch Linux

[Nokel81]

Do you mean a setting similar to the one for kubectl or an option for not bundling helm3 with Lens?

[ogarcia]

Now I'm building package without helm using this:

make node_modules
make build-extensions
yarn dist:dir

But the only method that I found to avoid to have a copy of helm with lens is make a symlink into resources/helm3/helm3 of my /usr/bin/helm. I think that an option like the one for kubectl is a great solution.

You can see my hack in Arch Linux pkgbuild.

[clain23]

Using built-in helm on M1 mac results an error:

/Applications/Lens.app/Contents/Resources/helm3/helm3: Bad CPU type in executable

Standalone helm works fine.

[Nokel81]

@jakolehm Can you investigate the "bad CPU type" issue?

[ogarcia]

This is caused because M1 has ARM architecure and in you must package the x86_64 binary in Lens.

[Nokel81]

@ogarcia Yes, but in #3700 shouldn't have introduced it