-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add types and proposal for k8s to kyaml migration. #2886
Add types and proposal for k8s to kyaml migration. #2886
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: monopole The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
"sigs.k8s.io/kustomize/api/resource" | ||
) | ||
|
||
// DepProvider is a dependency provider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the docs here :)
So close! This is going to be great when kubectl and use the latest kustomize. |
/lgtm |
Thanks Phil. I'm pining for a code base built on a decent dependency injection framework. :) |
In service of #1500 and #2506
Purpose of PR is defined in the header comment to api/krusty/internal/provider/depprovider.go
tl/dr: introduce a flag
--enable_kyaml
, which when true, switches all remaining code pathsfrom
k8s.io/api*
packages tokyaml
packages. The methods on the kyaml side that stillneed implementations are marked with TODO. I think this is an upper-bound on the work.
I'll look into dropping some features to reduce the size of the API surface that needs
implementation (especially the
vars
feature and theReplacementTransformer
).