Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HelmDeployer should detect helm version (2 or 3) #3438

Closed
oke-py opened this issue Dec 24, 2019 · 9 comments
Closed

HelmDeployer should detect helm version (2 or 3) #3438

oke-py opened this issue Dec 24, 2019 · 9 comments

Comments

@oke-py
Copy link
Contributor

oke-py commented Dec 24, 2019

Expected behavior

New function to detect helm version should be added to pkg/skaffold/deploy/helm.go.

Actual behavior

Helm version is assumed as v2.x.
Some helm command syntax changed in 3.x, and so, some skaffold function does not work as expected.

Information

This is the prerequisite for #3386 and #3387.

area/deploy
deploy/helm3

Steps to reproduce the behavior

N/A

@oke-py
Copy link
Contributor Author

oke-py commented Dec 24, 2019

I'm trying this.

@KhaledSakr
Copy link

I think a better solution for #3386 would be to always use helm upgrade --install since that seems to be the desired behaviour anyway. We shouldn't need to reimplement something in skaffold that is already supported by helm.

@ktarplee
Copy link

ktarplee commented Jan 3, 2020

This is partially implemented here

See #2142

@oke-py
Copy link
Contributor Author

oke-py commented Jan 4, 2020

@ktarplee Thank you for information.
If I understand correctly, detecting helm version is not desired and helm3 deployer should be implemented.

@ktarplee
Copy link

ktarplee commented Jan 5, 2020 via email

@tejal29
Copy link
Member

tejal29 commented Jan 15, 2020

@ktarplee Thanks. Supporting Helm3 is our high on our priority list. Sorry this taking longer.

We do want to make sure, we give users plenty of time to upgrade their app helm2 to helm3. We will change the default to helm3 as per our SLA.

@tejal29 tejal29 added kind/feature-request priority/p1 High impact feature/bug. labels Jan 15, 2020
@ErwinSteffens
Copy link

Any update v3 support? We love the tool, but this is a serious hurdle in adopting it.

@nkubala
Copy link
Contributor

nkubala commented Feb 28, 2020

@ErwinSteffens this was fixed with #3738! we'll ship it with the v1.5.0 release.

@nkubala nkubala closed this as completed Feb 28, 2020
@ErwinSteffens
Copy link

@ErwinSteffens this was fixed with #3738! we'll ship it with the v1.5.0 release.

Awesome, we will check it out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants