Closed Franr closed 10 months ago
Even if this could be seen as nice to have, for the moment the current supported kubectl versions cover our main use cases (https://github.com/binbashar/le-docker-leverage-toolbox/blob/191d6505a35d2e0370ba684074ae539462af9998/Dockerfile#L6C28-L7C1).
We'll close this issue till customer projects or the community require it. This will give more space to work on more urgent fixes and features.
Describe the Feature
Decide whether if we set/hardcode the Kubernetes version at `build.env or we let Leverage dynamically discover and manage it.
Expected Behavior
In both cases, Leverage must know with which version it has to deal, thus, automatically select a proper client.
Use Case
There are many Kubernetes versions out there, that require different client versions. We need to somehow deal with (most of) them all.
Describe Ideal Solution
The ideal solution is to make this as transparent as possible, so the final user don't have to think nor care about which client version they have to use.