Currently all cAdvisor flags are exposed through the cAdvisor binary. Many of the flags are irrelevant, or provide more controls than we want to give. Additionally, once we separate most cAdvisor functionality out of kubelet, most of thees flags will no longer make sense.

Open questions about the deprecation:

• Which flags are existing customers using? We should probably send a survey to various kubernetes groups to find out.
• Can we simply make the backwards incompatible change of removing the flags, or do we need to create "dummy" deprecated flags for each one in kubelet?

Prerequisite for #18770

@kubernetes/goog-node