Provide a ComponentConfig to tweak the Manager

[johnsonj]

Controllers would like to tweak the settings of the manager (eg, change logging verbosity) through a ComponentConfig.

Additionally, individual controllers may want to expose settings that relate to their usecase (eg, a whitelist of git repos an operator can pull from). I'm not sure if that's a usecase worth splitting off but we would like to use this for addon-operators

/cc @stealthybox @shawn-hurley @DirectXMan12

[DirectXMan12]

/kind feature

[DirectXMan12]

/priority important-longterm

[stealthybox]

Just to add context, ComponentConfig implies using API Machinery for the types used in a config file. (Not just unmarshalling a Yaml file into a Go struct)

More context in the component-base KEP:
https://github.com/luxas/enhancements/blob/f3005915981cf3e590dc0744ad0256cdf76970aa/keps/sig-cluster-lifecycle/0032-create-a-k8s-io-component-repo.md#part-1-componentconfig

[stealthybox]

I would imagine we would have some fields to configure the manager's SharedInformer?

[DirectXMan12]

Yeah, and the various other bits of the manager that can easily be configured with constant values (like metrics and webhook serving ports)

[stealthybox]

/wg component-standard

[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

[DirectXMan12]

/lifecycle frozen