kubernetesListNamespacePod is the single most common event sent in telemetry by far, and responsible for a significant portion of our events. It doesn't really tell us anything (we had access to pods on a namespace) compared with other events like reading individual items or modifying them, and even logging the errors isn't giving anything useful: they are infrequent in comparison and the vast majority are obvious access errors like the namespace wasn't accessible. Instead of trying to limit or change what we log, it seems prudent to just remove it.
kubernetesListNamespaces isn't called nearly as much, but since it is the only other list* tracking it seems like it should be removed to be consistent.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
Part of #4970.
How to test this PR?
List Kubernetes pods in watch mode and confirm event is not sent to Segment.
What does this PR do?
kubernetesListNamespacePod is the single most common event sent in telemetry by far, and responsible for a significant portion of our events. It doesn't really tell us anything (we had access to pods on a namespace) compared with other events like reading individual items or modifying them, and even logging the errors isn't giving anything useful: they are infrequent in comparison and the vast majority are obvious access errors like the namespace wasn't accessible. Instead of trying to limit or change what we log, it seems prudent to just remove it.
kubernetesListNamespaces isn't called nearly as much, but since it is the only other list* tracking it seems like it should be removed to be consistent.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
Part of #4970.
How to test this PR?
List Kubernetes pods in watch mode and confirm event is not sent to Segment.