While a number of problems with existing machinery are highlighted in the above doc, this
proposal is focused on the following two use-cases:
Enforcing flag precedence between values
specified on the command line and values from a config file, which is required to incrementally
migrate flags to a config file with backwards compatibility.
Preventing third-party code from implicitly registering flags
against a component's command-line interface, which is required for components to maintain
explicit control over their command-line interface.
Rather than require other components to copy and customize the Kubelet's relatively complex
solutions to these problems, we should put the common functionality in a library, legacyflags, to reduce
the burden on component owners.
This proposal recommends the approach in this example PR:
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.