Kustomize install libs

[stealthybox]

Discussed on the addon-operators call, the group would like to see a standalone binary from this repo capable of using some ComponentConfig to prepare several kustomize directories for application to the cluster.

This binary is a POC that can be used to implement installer/management functionality into tools like kops/kubeadm/eksctl as well as many other tools that went unmentioned/unrepresented.

The decision on kustomize is heavily inspired by the ability to overlay arbitrary patches without requiring deps external to the k8s org.
It is also already built into kubectl which helps simplify the POC.

We expect to shell out to kubectl for simplicity of maintenance as its sophisticated apply behavior cannot easily be replicated at this point in time. (see serviside-apply)

The config should allow users to select a kustomize base for installing their operator.
CoreDNS operator is a good starting point.
Users should be able to specify versioned/packaged patch sets.

This is accomplished with a package ref that can start by loading the kustomize base/overlay from a git ref or local file-system location.
Further work may allow loading from other sources.

/kind feature

[fejta-bot]

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

[stealthybox]

/lifecycle active

[fejta-bot]

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]

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]

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

[k8s-ci-robot]

@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.