Use NamespaceAwareResourceMetaGenerator for all generic kubernetes resources

[tetianakravchenko]

What does this PR do?

Add namespace metadata to all namespaced resources such as deployment, replicates, jobs, cronjob, statefulset and daemonset, etc.

related PR - elastic/elastic-agent-autodiscover#33

Note: after this change all labels of the namespace, where the resource is running, will be added to resource

Why is it important?

#33108

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Related Add resource metadata in all possible Kubernetes module metricsets #33144

Use cases

Screenshots

Memory usage of metricbeat after introducing this change comparing to the main branch:

namespace labels on statefulset resource:

persistentvolume - nothing changed as this resource is not namespaced

Logs

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b k8s-metricsets-add-resource-meta upstream/k8s-metricsets-add-resource-meta
git merge upstream/main
git push upstream k8s-metricsets-add-resource-meta

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @tetianakravchenko? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-12-07T08:48:59.721+0000

• Duration: 129 min 20 sec

Test stats 🧪

Test	Results
Failed	0
Passed	24485
Skipped	1805
Total	26290

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the 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!)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b k8s-metricsets-add-resource-meta upstream/k8s-metricsets-add-resource-meta
git merge upstream/main
git push upstream k8s-metricsets-add-resource-meta

[gizas]

@tetianakravchenko how about this lint errors? https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html#running-linter can this help?

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b k8s-metricsets-add-resource-meta upstream/k8s-metricsets-add-resource-meta
git merge upstream/main
git push upstream k8s-metricsets-add-resource-meta

[tetianakravchenko]

/package

[tetianakravchenko]

Regarding failing golangci-lint: I can't reproduce those error and locally I am getting only warnings:

 mage llc
WARN [linters context] bodyclose is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649.
WARN [linters context] nilerr is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649.
WARN [linters context] noctx is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649.
WARN [linters context] structcheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649.
WARN [linters context] wastedassign is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649.

used the same go verions as in project:

go version
go version go1.18.8 darwin/amd64

that seems to be related to some of the golangci/golangci-lint-action@v3 dependencies

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b k8s-metricsets-add-resource-meta upstream/k8s-metricsets-add-resource-meta
git merge upstream/main
git push upstream k8s-metricsets-add-resource-meta

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b k8s-metricsets-add-resource-meta upstream/k8s-metricsets-add-resource-meta
git merge upstream/main
git push upstream k8s-metricsets-add-resource-meta

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.2% Duplication