-
Notifications
You must be signed in to change notification settings - Fork 922
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
kubectl kustomize versioning #797
Comments
/cc @kubernetes/sig-cli-feature-requests |
Regardless of the future of |
Please close and reopen this on kustomize. |
great filed as kubernetes-sigs/kustomize#2142. though i think the change has to happen in this repo, since it's about what subcommands are registered? https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/kustomize/kustomize.go#L59 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/sig cli |
/assign |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/priority important-soon |
FYI: updating the FAQ with this: kubernetes-sigs/kustomize#2749 TLDR: This is blocked on either moving kubectl into its own repo, or changing its dependencies. ETA k8s ~1.20. The adoption of go modules in the kubernetes/kubernetes repo broke the update process for kustomize. 2 pieces of work are underway which will allow kustomize to be updated in kubectl:
Once either of these issues is resolved we will then update kubectl with the latest kustomize version. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
kubectl apply -k doesnt work with kustomization.yaml with generators and transformers. Any help |
update: the built in kustomize doesn't work with generators and transfomers plugins (as per mentioned in one of the open questions). As I was trying it within azure environment, I reckon the best place to install kustomize and set the path in azure is https://www.kubeflow.org/docs/other-guides/kustomize/ ... solved my issue. thanks |
RE: Version Upgrade for those whom stumble across this: |
Looks like @natasha41575 is this something y'all can take on? |
will discuss with @monopole |
Let's track this at kubernetes-sigs/kustomize#1424 /close |
Expected behavior:
should print information about the version of Kustomize templates that
kubectl kustomize
acceptsActual behavior
doesn't work.
The kubectl command only accepts kustomize version 2+, but the main kustomize repo is on version 3+. This has caused some confusion for our users, because they thought that they should be using the "new way" of preferring
kubectl kustomize
overkustomize
Obviously, we could work around this by keeping a map from kubectl versions to compatible kustomize versions, but it would be nice if we could get this info from
kubectl kustomize
Relatedly, what's the plan for upgrading
kubectl
to kustomize 3?The text was updated successfully, but these errors were encountered: