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.

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

Remove dependence on k8s.io/apimachinery and related k/k libs #2506

Closed
monopole opened this issue May 20, 2020 · 4 comments · Fixed by #3568
Closed

Remove dependence on k8s.io/apimachinery and related k/k libs #2506

monopole opened this issue May 20, 2020 · 4 comments · Fixed by #3568
Assignees
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@monopole
Copy link
Contributor

monopole commented May 20, 2020

kustomize api depends on k/k/apimachinery in api/k8sdeps and api/internal/k8sdeps.

This dependency must be removed to update the kustomize functionality built into kubect (currently lagging the standalone kustomize).

As an ancillary benefit, kustomize will rebase on (and coevolve with) the kyaml libraries

This issue blocks #1500

@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

monopole added a commit to monopole/kustomize that referenced this issue Nov 25, 2020
The implementations in WNode are supposed to be thin,
as it will be removed once kubernetes-sigs#2506 closes.

The change also makes some addjustments for the
upcoming flip of the enable_kyaml flag, pointing to
issue kubernetes-sigs#3271.
@modevops
Copy link

modevops commented Feb 3, 2021

any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants