Argo-cd: Remove support for kustomize 1 entirely
Is your feature request related to a problem? Please describe.
Most developers are using K2 these days, and getting confused because we auto-detect Kustomize based on whether or not there are the apiVersion/kind fields in kustomization.yaml.
How can we default this correctly?
Describe the solution you'd like
TBD
Describe alternatives you've considered
TBD
Additional context
enhancement
alexec
>All comments
Rather than trying to support both / work on making kustomize 2 the default, I propose we just begin deprecation process for kustomize v1, including eventually removing the UI and spec fields specific to v1.
jessesuen
on 8 May 2019
👍3
Was this page helpful?
0 / 5 - 0 ratings
Related issues
jessesuen
路
24Comments
niqdev
路
23Comments
tschonnie
路
31Comments
StianOvrevage
路
23Comments
eroji
路
24Comments
Most helpful comment
Rather than trying to support both / work on making kustomize 2 the default, I propose we just begin deprecation process for kustomize v1, including eventually removing the UI and spec fields specific to v1.