helm/helm-mapkubeapis

Question: Removal of Helm v2 support?

hickeyma opened this issue · 6 comments

Helm v2.17.0 was the final release of Helm v2 in October 2020. Helm v2 is unsupported since November 2020, as detailed in Helm 2 and the Charts Project Are Now Unsupported.

Helm v2 uses an older version of Kubernetes Go client which is incompatible with Kubernetes Go Client 1.18+. helm-mapkubeapis calls Helm v2 storage APIs which in turn call Kubernetes Go client APIs. This means that the plugin is restricted to using Helm v3.1.3 (last Helm v3 release which uses Kubernetes Go Client pre 1.18) which was released in April 2020.

Is it time to drop support for Helm v2 in this plugin as Helm v2 is no longer supported? The benefit is that we can update to the latest dependencies.

I agree support for v2 should be dropped.

The plugin even has older versions tagged if anyone needs to use it with v2 and an old kubernetes.

I think it is important for this plugin to keep up with the latest helm versions.

Thanks @hickeyma for bringing this up.

I agree, this is a fine time to remove v2 support. If someone needs it they can get an older version of the plugin.

I am OK with this

I support this as well, agree with Marc and Matt's reasons above.

@hickeyma quick question, are you thinking we’ll also drop support for https://github.com/helm/helm-2to3, or in “Recommended Prior to Migration (https://github.com/helm/helm-2to3#recommended-prior-to-migration)” suggest an alternative approach to mapkubeapis plugin?

quick question, are you thinking we’ll also drop support for https://github.com/helm/helm-2to3, or in “Recommended Prior to Migration (https://github.com/helm/helm-2to3#recommended-prior-to-migration)”%E2%80%9D) suggest an alternative approach to mapkubeapis plugin?

No, not stopping support yet for https://github.com/helm/helm-2to3 as folks are possibly still migrating or even using Helm v2. If someone needs the mapkubeapis Helm v2 capability, they can use release v0.2.0 of the plugin.