[receiver/k8sobjects] move k8sobjects receiver to beta

[omrozowicz-splunk]

Component(s)

receiver/k8sobjects

Describe the issue you're reporting

Proposal

I'd like to discuss what it takes to mark k8sobjects receiver as beta. It's already over 6 months available, and only small enhancements were added during the last 3 months - no breaking changes. Some customers are reluctant to use it because of its alpha status. The only currently open issue/enhancement request is about adding e2e tests #18395

[github-actions]

Pinging code owners:

• receiver/k8sobjects: @dmitryax @hvaghani221

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

Would it be possible to close #18395 first?

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/k8sobjects: @dmitryax @hvaghani221

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[TylerHelmuth]

I would also like to close these first since they are related to the configuration:

• [receiver/k8sobjects] Add configuration option to specify ingesting the initial state on a watch #24902
• [receiver/k8sobjects] Allow specifying whether DELETE actions should be ingested during a watch #24904

[TylerHelmuth]

The k8sobjects receiver has had a lot of work done this summer that pushes it closer to beta. I feel once the e2e test that @jinja2 is implementing is finished we can call this receiver beta.