Proposal: Config API design patterns as ICDNs


I’d like to propose adopting a light-weight process for creating Config Design Notes for capturing the design patterns we want to enable in Istio (i.e. how to use namespaces, label selections, expressions etc.)

This is based on the API Improvement Process, internally used in Google to drive a similar process. PTAL.