kubernetes-sigs / kustomize

Customization of kubernetes YAML configurations

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Update kustomize version that's shipped in kubectl?

pascalgn opened this issue · comments

Not sure where the right repository is for this, maybe here, maybe https://github.com/kubernetes/kubectl, maybe https://github.com/kubernetes/kubernetes?

Kubernetes has just released v1.16.0-beta.2 and so far I haven't seen anything about a new kustomize version in the changelogs. I think if we want to have an updated version shipped in kubectl 1.16, we need to do something in the near future.

Are there any plans for updating the kustomize version that's integrated into kubectl?

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

commented

It was mentioned in #1267 (comment) that the intention is for each kubectl release to use the latest kustomize version.

Is this issue the correct place to be tracking progress on this?

Just for context: the mismatch in functionality is a proving bit inconvenient for us when we're trying to build automation around kustomize.

See also: #1424

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

commented

/remove-lifecycle rotten

commented

Not sure if I'm supposed to marking this issue as fresh. My apologies if not.

From my perspective I think this is still an issue and some guidance would be appreciated as we're attempting to use kustomize in automation.

Sounds like from the discussion in kubernetes/kubernetes#85146 that there might be a different approach proposed here?

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

Any update on this?

commented

/remove-lifecycle stale

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

/remove-lifecycle stale

We are working on this.

Another umbrella issue about removing apimachinery and related libraries. #2506

Update: targetting kubectl release v1.21, code freeze.

Per: https://www.kubernetes.dev/resources/release/

Tuesday, February 9th: Week 5 - Enhancements Freeze
Tuesday, March 9th: Week 9 - Code Freeze

The best way to help on this issue is use and report bugs in the latest standalone version of kustomize in the 3.9 series - e.g. v3.9.2.

This instance of the kustomize CLI uses the same kustomize libraries which will be linked into kubectl via normal import mechanisms; we're shaking some final bugs.

Kustomize releases every two weeks, while kubectl releases at most once a qtr.