Tracking issue for kubeadm integration with kustomize

[timothysc]

This a FEATURE REQUEST?

A number of feature requests we've had over time have all centered around the idea plumbing through options into what eventually becomes the end-state of a pile of YAML. Some things make sense to expose as knobs, but other things don't.

The purpose of this issue is to explore the option and impact of what is would mean to add a kustomize step @ certain phases of YAML generation.

@neolit123 @fabriziopandini @luxas

design proposal (tracking issue/KEP): kubernetes/enhancements#1177

[luxas]

I'm not gonna have time to work on this quite yet, doing the other refactoring of the other components to use componentconfig first

[fabriziopandini]

This is indeed a good idea, even if currently the pile of yaml is super fragmented across the kubeadm code base, and not always managed consistently.

So it is important to decide since the beginning if we want kustomize applied selectively or if we should go for a deeper refactor: First generate all yamls, then kustomize, then apply to the cluster (kubeadm 2.0)

Another thing we should define is what kind of support is provided for Kustomized cluster (for join/upgrades)

[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

[neolit123]

/remove-lifecycle stale

[randomvariable]

This is also potentially part of #683 for some recommended options.

In particular there is a need to customise the static pod manifests created by kubeadm

[jfbai]

Is there any design proposal or PR for this feature request?

[fabriziopandini]

initial design proposal. https://docs.google.com/document/d/1SfZlCabOtu8BIzP_Q5sd5s8BhC75L8Wvz7aL-ce1Jhw/edit?usp=sharing

KEP
kubernetes/enhancements#1159

[neolit123]

@fabriziopandini i renamed the ticket and added kind/tracking issue.
please keep the OP updated with a list of PRs and TODO tasks.

[fabriziopandini]

done in 1.16
/close

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

done in 1.16
/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.