Currently, the Kubernetes exporter fetches all resources of the specified kinds from the Kubernetes API and applies filtering only after the data is retrieved, using the query selector in the integration config. This can result in large volumes of irrelevant data being fetched and processed, especially in clusters with thousands of pods and nodes.

Request:

Introduce support for API-level filtering (pre-fetch filtering) in the Kubernetes exporter, similar to how JQL is used in the Jira integration to filter issues at the source. This would allow users to specify filters (e.g., by namespace, resource type, or labels) that are applied directly in the API request, reducing the amount of data fetched and improving sync performance.