Open
Description
What would you like to be added?
Test that analyzes Kubernetes traffic to drive work on robustness tests.
Example test: #20181
Why is this needed?
Given the large API surface of Etcd I would like to introduce a method to track what is currently used by Kubernetes. This may help improve tests by better simulating actual traffic, alert about novel use cases, and in some cases highlight the potential to reduce the used API surface.
Related to #15820
Doc with more information and discussion: https://docs.google.com/document/d/1dd5dRk53VN89nHTEapMYNrbhIxK9wB52vsnuqwQi8LI/edit?usp=sharing
/cc @serathius