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

Update kustomize in kubectl #818

Closed
dneilson opened this issue Feb 11, 2020 · 14 comments · Fixed by kubernetes/kubernetes#98946
Closed

Update kustomize in kubectl #818

dneilson opened this issue Feb 11, 2020 · 14 comments · Fixed by kubernetes/kubernetes#98946
Assignees
@monopole @seans3
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/cli Categorizes an issue or PR as relevant to SIG CLI.

Comments

@dneilson
Copy link

The documentation out there is not right for the version baked in kubectl at the moment.

It is incredibly frustrating attempting to use it :|

Can we have this updated so we can use more options to generating manifests?
@seans3
Copy link
Contributor

seans3 commented Feb 19, 2020

The current kustomize in kubectl is 2.0.3.
kustomize at head is above that.

/sig cli

@k8s-ci-robot k8s-ci-robot added the sig/cli Categorizes an issue or PR as relevant to SIG CLI. label Feb 19, 2020
@seans3
Copy link
Contributor

seans3 commented Feb 19, 2020

The current challenge with updating kustomize in kubectl is the different versions of common dependencies. This challenge will be solved when kubectl completely removed from core kubernetes.

@squaricdot squaricdot mentioned this issue Mar 30, 2020
Closed
@brianpursley
Copy link
Member

/kind documentation

@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Apr 29, 2020
@mool
Copy link

mool commented Apr 30, 2020

It would be great to have the latest kustomize version in kubectl :-)

@brianpursley
Copy link
Member

/remove-kind documentation

Sorry, I think I misclassified this. Sounds like this is not just a documentation thing.

@k8s-ci-robot k8s-ci-robot removed the kind/documentation Categorizes issue or PR as related to documentation. label Apr 30, 2020
@Gfeuillen
Copy link

+1 : the kubectl integration is one of the reasons we went for kustomize.

It would already be nice to be able to get the underlying kustomize version. @seans3 How did you arrive at this ?

@tylerauerbeck
Copy link

Are there any current plans to at least get kustomize on a 3.X release instead of remaining a full major release behind?

@mpreu mpreu mentioned this issue Jun 5, 2020
Closed
@nick-jones nick-jones mentioned this issue Jun 15, 2020
Closed
@Kampe
Copy link

Kampe commented Jun 24, 2020

The amount of issues present in 2.x.x is really annoying. Can we get this prioritized?

coro added a commit to rabbitmq/cluster-operator that referenced this issue Jul 9, 2020
@coro
Remove deprecated bases from kustomization files
28ce005 
`bases` is a deprecated section of the kustomize API, and is replaced by
`resources` in v2.1.0 onwards. Since we use kustomize 3.X, this moves
our kustomization yamls to the new accepted format.

This also moves our Makefile away from using `kubectl <apply/delete>
-k`, which uses kubectl's older, bundled version of Kustomize v2.0.3
(see [this issue](kubernetes/kubectl#818)).
@coro coro mentioned this issue Jul 9, 2020
Merged
@Numblesix
Copy link

Is there any update its pretty hard to follow examples (as nee starter) just to find out that the kustomize version shipped in kubectl/oc is pretty outdated :(

@soltysh soltysh mentioned this issue Jul 22, 2020
Closed
@eddiezane
Copy link
Member

/priority important-soon

Tied with #797

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 22, 2020
@eddiezane
Copy link
Member

/assign @seans3
/assign @monopole

@monopole
Copy link
Contributor

Tracking in the kustomize repo as kubernetes-sigs/kustomize#1500

@soltysh soltysh mentioned this issue Oct 30, 2020
Closed
@wtfiwtz wtfiwtz mentioned this issue Nov 4, 2020
Closed
@vitus133 vitus133 mentioned this issue Dec 13, 2020
Merged
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 15, 2020
@hoxu
Copy link

hoxu commented Dec 15, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 15, 2020
vitus133 added a commit to lack/cnf-features-deploy that referenced this issue Dec 20, 2020
@vitus133
Use standalone kustomize tool
35f207e 
Will download and use the standalone
kustomize tool instead of the one
integrated in the OC_TOOL

As of v3.7.0 Kustomize supports a special type of kustomization that allows one to define reusable pieces of configuration logic that can be included from multiple overlays.
Components come in handy when dealing with applications that support multiple optional features and you wish to enable only a subset of them in different overlays, i.e., different features for different environments or audiences.

It is not clear when kustomize 3.x will be integrated into the kubectl, current supported version is 2.x
The integration is tracked here: kubernetes/kubectl#818
vitus133 added a commit to lack/cnf-features-deploy that referenced this issue Dec 20, 2020
@vitus133
Use standalone kustomize tool
5d93be0 
    Will download and use the standalone
    kustomize tool instead of the one
    integrated in the OC_TOOL

    As of v3.7.0 Kustomize supports a special type of kustomization that allows one to define reusable pieces of configuration logic that can be included from multiple overlays.
    Components come in handy when dealing with applications that support multiple optional features and you wish to enable only a subset of them in different overlays, i.e., different features for different environments or audiences.

    It is not clear when kustomize 3.x will be integrated into the kubectl, current supported version is 2.x
    The integration is tracked here: kubernetes/kubectl#818
@NicolasT NicolasT mentioned this issue Jan 7, 2021
Closed
@dansiviter dansiviter mentioned this issue Jan 15, 2021
Closed
@monopole monopole mentioned this issue Feb 10, 2021
Merged
@alenkacz alenkacz mentioned this issue Feb 23, 2021
Merged
2 tasks
@dvaldivia dvaldivia mentioned this issue Apr 13, 2021
Merged
tiraboschi added a commit to tiraboschi/hyperconverged-cluster-operator that referenced this issue May 4, 2021
@tiraboschi
Make deploy/kustomize compatible with kustomize v3
7a43786 
Specify the namespace in the base kustomization.yml
but not in the base resources so that can be kustomized
by patches that don't specify the same namespace.

The kustomize version shipped with kubectl has been
recently updated, see: kubernetes/kubectl#818

This introduces an incompatibility when we try to apply
a patch that doesn't specify a namespace to a base
obejct that instead specifies it.

The simplest option to have it working at the same time
with kustomize 2.y and 3.y seems to set the namespace
only on the base kustomization.yml but not on the
base resources.
See:
kubernetes-sigs/kustomize#1351

Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
@tiraboschi tiraboschi mentioned this issue May 4, 2021
Merged
11 tasks
kubevirt-bot pushed a commit to kubevirt/hyperconverged-cluster-operator that referenced this issue May 4, 2021
@tiraboschi
Make deploy/kustomize compatible with kustomize v3 (#1319)
693df47 
Specify the namespace in the base kustomization.yml
but not in the base resources so that can be kustomized
by patches that don't specify the same namespace.

The kustomize version shipped with kubectl has been
recently updated, see: kubernetes/kubectl#818

This introduces an incompatibility when we try to apply
a patch that doesn't specify a namespace to a base
obejct that instead specifies it.

The simplest option to have it working at the same time
with kustomize 2.y and 3.y seems to set the namespace
only on the base kustomization.yml but not on the
base resources.
See:
kubernetes-sigs/kustomize#1351

Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@monopole monopole

@seans3 seans3

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade kustomize-in-kubectl to v4.0.5 monopole/kubernetes