Kustomize: create examples/docs for using kustomize library functions

Created on 27 Jun 2018 · 11Comments · Source: kubernetes-sigs/kustomize

some examples to show how to use kustomize as library. Examples are like applying a patch, applying a name reference substitution

kindocumentation lifecyclrotten

Source

Liujingfang1

👍2

Most helpful comment

@BenTheElder Yes, it does. If you want to apply kustomize build to a directory, you can try

kt, _:= target.NewKustTarget(rootLoader, fSys, "")
allResources, err := kt.MakeCustomizedResMap()
if err != nil {
   return err
}
// Output the objects.
res, err := allResources.EncodeAsYaml()
if err != nil {
    return err
}
if o.outputPath != "" {
    return fSys.WriteFile(o.outputPath, res)
}
// Write output to file
_, err = out.Write(res)

It is the same function calls as in kustomize build https://github.com/kubernetes-sigs/kustomize/blob/master/pkg/commands/build.go#L117

Liujingfang1 on 1 Oct 2018

👍3

All 11 comments

Does kustomize support usage as a library? I'm very interested in this for configuration in sigs.k8s.io/kind

BenTheElder on 29 Sep 2018

@BenTheElder Yes, it does. If you want to apply kustomize build to a directory, you can try

kt, _:= target.NewKustTarget(rootLoader, fSys, "")
allResources, err := kt.MakeCustomizedResMap()
if err != nil {
   return err
}
// Output the objects.
res, err := allResources.EncodeAsYaml()
if err != nil {
    return err
}
if o.outputPath != "" {
    return fSys.WriteFile(o.outputPath, res)
}
// Write output to file
_, err = out.Write(res)

It is the same function calls as in kustomize build https://github.com/kubernetes-sigs/kustomize/blob/master/pkg/commands/build.go#L117

Liujingfang1 on 1 Oct 2018

👍3

I've got something wrapping the build cobra command now for anyone else wanting to embed kustomize build as a library: https://github.com/kubernetes-sigs/kind/pull/77

BenTheElder on 26 Oct 2018

👍1

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

fejta-bot on 26 Apr 2019

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

fejta-bot on 26 May 2019

/remove-lifecycle rotten
I think what I actually need is just some unstructured patching code, currently these types (kubeadm config) aren't known as structured types to kustomize anyhow.

It would be nice if this logic could be re-used and had documentation :sweat_smile:

BenTheElder on 14 Jun 2019

I also did some work on this here. It eschews the need for the external kustomize command, and even supports virtual patches.

akutz on 22 Jul 2019

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

fejta-bot on 20 Oct 2019

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

fejta-bot on 19 Nov 2019

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-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 19 Dec 2019

@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-testing, kubernetes/test-infra and/or fejta.
/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.