-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick #25169 to 7.x: Fix k8s svc selectors mapping #25175
Conversation
(cherry picked from commit 86f00e4)
Pinging @elastic/integrations (Team:Integrations) |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errorsExpand to view the tests failures
|
Test | Results |
---|---|
Failed | 1 |
Passed | 46706 |
Skipped | 5169 |
Total | 51876 |
Genuine test errors
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Build&Test / filebeat-build / TestFilestreamTruncate – github.com/elastic/beats/v7/filebeat/input/filestream
Cherry-pick of PR #25169 to 7.x branch. Original message:
What does this PR do?
This PR fixes the mapping of k8s service.selectors introduced at #23730
Why is it important?
Mapping is not what we actually report. Field is set at
kubernetes.selectors.*
while we definekubernetes.servcie.selectors.*
in the mapping. There is no reason to have it specific for services since it can be added for other resources too in the future like deployments. In this we can store underkubernetes.selectors.*
like what we do forlabels
andannotations
.