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.

Sign up for GitHub

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

Jump to bottom

Implement backwards-compatible "legacy" helm deployer #6720

Closed
tejal29 opened this issue Oct 13, 2021 · 1 comment
Closed

Implement backwards-compatible "legacy" helm deployer #6720

tejal29 opened this issue Oct 13, 2021 · 1 comment
Assignees
@MarlonGamez
Labels
2.0.0 Issues related to the 2.0.0 release kind/todo implementation task/epic for the skaffold team planning/H1-2022
Milestone
2.0.0-alpha2

Comments

@tejal29
Copy link
Contributor

tejal29 commented Oct 13, 2021 •
edited by nkubala
Loading

Relates to #5673

We need to implement a backwards-compatible legacy helm deployer on the v2 feature branch for users who rely on helm-specific functionality (e.g. helm upgrade or helm list) in their deploy workflows.

See responses to this survey for motivation.
@tejal29 tejal29 added this to the unplanned milestone Oct 13, 2021
@tejal29 tejal29 added area/V2 planning/Q4-21 Q4 2021 planning kind/todo implementation task/epic for the skaffold team labels Oct 13, 2021
@tejal29 tejal29 modified the milestones: unplanned, v1.35.0 Oct 13, 2021
@nkubala nkubala modified the milestones: v1.35.0, 2.0.0-alpha Nov 15, 2021
@nkubala nkubala changed the title Legacy helm support: a user can continue to use helm install or helm upgrade Implement backwards-compatible "legacy" helm deployer Nov 15, 2021
@nkubala nkubala added 2.0.0 Issues related to the 2.0.0 release and removed area/V2 labels Nov 15, 2021
@tejal29 tejal29 added planning/H1-2022 and removed planning/Q4-21 Q4 2021 planning labels Dec 15, 2021
@tejal29 tejal29 mentioned this issue Feb 15, 2022
Merged
4 tasks
@MarlonGamez MarlonGamez self-assigned this Jun 1, 2022
@MarlonGamez
Copy link
Contributor

I believe this is resolved by #7190, so closing this for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MarlonGamez MarlonGamez

Labels
2.0.0 Issues related to the 2.0.0 release kind/todo implementation task/epic for the skaffold team planning/H1-2022
Projects
None yet
Milestone
2.0.0-alpha2
Development

No branches or pull requests
3 participants
@tejal29 @nkubala @MarlonGamez