Add cronjob metadata by default

[ChrsMark]

What does this PR do?

1. Makes metadata from cronjob objects available by default
2. Adds cronjob.name for Pods handled by a Job but are actually created because of a CronJob: https://github.com/elastic/beats/pull/30637/files#diff-e127eb943d1a3edae0a9f12cc7c3849874a256ae557242bf1473a1a28654fe64R101

Why is it important?

In order to make metadata addition for cronjob objects by default.

Related issues

• Closes Revisit how metadata are added for jobs/cronjobs #29771

cc: @MichaelKatsoulis

[botelastic]

This pull request doesn't have a Team:<team> label.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
[](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-03-09T20:06:58.934Z&rangeTo=2022-03-09T20:26:58.934Z&transactionName=BUILD Beats/beats/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=84498d316bc7fafbd42bc2369465ce4c&transactionId=cc5e4aa2841fc490)

Expand to view the summary

Build stats

• Start Time: 2022-03-09T20:16:58.934+0000

• Duration: 121 min 12 sec

Test stats 🧪

Test	Results
Failed	0
Passed	42437
Skipped	3708
Total	46145

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[MichaelKatsoulis]

Maybe we should be a bit more specific here of what they need to remove. Why not add an example with the specific part of the cluster role they need to remove?

[MichaelKatsoulis]

LGTM

[ChrsMark]

Trying to isolate the CI failures at #30685. Something is really weird here.

[ChrsMark]

Waiting for #30732 to see if an upgrade fixes things.

[ChrsMark]

Something is odd with the way we test on the CI as described at #30733. For now we can disable metadata addition for state_cronjob tests. I will file a separate issue for this so as to keep it tracked. For reference, the metricset is indirectly tested about this functionality under integrations repo so we can claim that it is safe to skip metadata here for now.

@MichaelKatsoulis let me know what you think about this.

[MichaelKatsoulis]

@MichaelKatsoulis let me know what you think about this.

Although it is a dirty workaround, it does not seem to be another way.

So +1