I think it would be beneficial if there was a way to "blacklist" Kubernetes Pods from relating to it's Service Instance but instead populate a Dynamic CI Group.
The Problem:
Tag-Based Services with a lot of pods won't show the full relationships because there are too many relationships to show because there are so many pods.
Solution (theory):
If the pods are tagged appropriately to be mapped to the tag-based service, they would instead populate a dynamic CI group that is related to the tag-based service.
Solution (in practice):
My first suggestion: Stop discovering pods. (I'm having a hard time getting them to bite on this suggestion)
Next option: ???
