[receiver/k8sobjectsreceiver]: support exclude_namespaces to exclude namespace from being watched

[KyriosGN0]

Description

This PR introduces a new parameter to the receiver config, called ignore_namespaces its array of string that specify which namespaces should be excluded from being watched at all (can be a regex expression)
the option in my opinion should not be used together with the Namespaces option, as one is allowlist and the other is denylist

Link to tracking issue

Fixes #36217

Testing

ran a kind cluster, deployed otel collector configured with this receiver and a debug exporter, created pods in a namespace that is in the deny list and saw that they are not being pulled/watched and that pods in other namespaces are pulled/watched

[atoulme]

Please add a changelog and check the CI

[KyriosGN0]

@atoulme Thanks, added the required file for changelog

[ChristianCiach]

I am not a maintainer or anything, so my opinion carries little weight. But I think the name {{something}}_deny_list is really strange and sticks out like a sore thumb. It's like naming a namespace field namespace_string. I think ignore_namespaces would be a lot more idiomatic.

Edit: Other components, like the filelog receiver, seem to use the include/exclude naming pattern. So how about exclude_namespaces?

[dmitryax]

I agree with @ChristianCiach.

Please also use https://github.com/open-telemetry/opentelemetry-collector/blob/main/filter/config.go. So the user config could be

exclude_namespaces:
  - regexp: kube-*

[atoulme]

Moving to draft while you address the feedback - please mark ready to review once done.

[KyriosGN0]

hey @dmitryax, i have addressed you comments, thanks!

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[KyriosGN0]

Not stale
Waiting for review

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[KyriosGN0]

not stale, i will rebase in the next 2 days probably

[KyriosGN0]

/rerun

[otelbot]

Thank you for your contribution @KyriosGN0! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. If you are getting started contributing, you can also join the CNCF Slack channel #opentelemetry-new-contributors to ask for guidance and get help.

[odubajDT]

Hey, there is an ongoing refactoring of this component and some of the functionality was moved to internal/k8sinventory with this PR. Would you @KyriosGN0 b interested in adapting the internal library as well and afterwards using the adapted internal code in the k8sobjectsreceiver?

There is an already PR with adapted code using the k8sinventory lib (without your changes) here. I would gladly step back from the PR in case you would be interested in bringing it to the line.

Thanks!

[KyriosGN0]

here

hey @odubajDT this sounds really interesting, but i don't have the bandwith for that right now