The kubectl docs on kustomize prominently discuss bases, though this was deprecated a year ago.

/priority backlog
@seans3 @pwittrock @monopole any thoughts on this one? Do we remove that page from the kubectl book?
Need to update Kustomize first
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
Has anything happened regarding this issue?
Bases are still even used on the main readme -

Very unclear what the suggested method is given this comment
Bases was deprecated in version/v2.1. but still works in v2 series and moving ../../bases to resources causes issues.
https://kubernetes-sigs.github.io/kustomize/blog/2019/06/18/v2.1.0/#resources-expanded-bases-deprecated
I think some of the problem here is that the version of kustomize included in kubectl (2020-11-20 v1.19.0) is old and so people are still running into this (I know i did) and the docs on the kubernetes site still refer to using bases because that is the version included in kubectl https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/#bases-and-overlays
Looks like it may get updated in kubectl 1.20 https://kubectl.docs.kubernetes.io/faq/kustomize/#kubectl-doesnt-have-the-latest-kustomize-when-will-it-be-updated
The latest version of the docs available at https://kubectl.docs.kubernetes.io/guides/config_management/components/ make more sense as these are for v3 but this requires that you use a standalone version of kustomize
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
I don't think this issue is stale or rotten, it's just a lack of updates.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-contributor-experience at kubernetes/community.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Maybe this issue is worth reopening? I see "bases" is deprecated, but I'm curious what else I might be missing.
Most helpful comment
Bases was deprecated in version/v2.1. but still works in v2 series and moving
../../basesto resources causes issues.https://kubernetes-sigs.github.io/kustomize/blog/2019/06/18/v2.1.0/#resources-expanded-bases-deprecated
I think some of the problem here is that the version of kustomize included in kubectl (2020-11-20 v1.19.0) is old and so people are still running into this (I know i did) and the docs on the kubernetes site still refer to using bases because that is the version included in kubectl https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/#bases-and-overlays
Looks like it may get updated in kubectl 1.20 https://kubectl.docs.kubernetes.io/faq/kustomize/#kubectl-doesnt-have-the-latest-kustomize-when-will-it-be-updated
The latest version of the docs available at https://kubectl.docs.kubernetes.io/guides/config_management/components/ make more sense as these are for v3 but this requires that you use a standalone version of kustomize