Add some info about 1:1/1:n relationships

Author: mrueg

docs/design/metrics-best-practices.md

@@ -31,8 +31,9 @@ This way kube-state-metrics allows the user to have full control on how they wan
 ### Static object properties
 
 An object usually has a stable set of properties that do not change during its lifecycle in Kubernetes.
-This includes properties like name, namespace, uid etc.
+This includes properties like name, namespace, uid etc. that have a 1:1 relationship with the object.
 It is a good practice to group those together into an `_info` metric.
+If there is a 1:n relationship (e.g. a list of ports), it should be in a separate metric to avoid generating too many metrics.
 
 ### Dynamic object properties
 
@@ -41,8 +42,6 @@ These change during the lifecycle of the object.
 For example a pod can be in different states like "Pending", "Running" etc.
 These should be part of a "State Set" that includes labels that identify the object as well as the dynamic property.
 
-For example:
-
 ### Linked properties
 
 If an object contains a substructure that links multiple properties together (e.g. endpoint address and port), those should be reported in the same metric.