Skip to content
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

[Kubernetes] Flaky test - field "kubernetes.labels.kubernetes_io/metadata_name" is undefined #9625

Closed
andrewkroh opened this issue Apr 16, 2024 · 1 comment · Fixed by #9630
Labels
flaky-test Unstable or unreliable test cases. Integration:kubernetes Kubernetes Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Comments

@andrewkroh
Copy link
Member

Builds on the main branch under v8.14.0 are failing because of these errors from the Kubernetes integration.

Owner: @elastic/obs-cloudnative-monitoring

system test: default in kubernetes.state_namespace

one or more errors found in documents stored in metrics-kubernetes.state_namespace-ep data stream: [0] field "kubernetes.labels.kubernetes_io/metadata_name" is undefined

https://buildkite.com/elastic/integrations/builds/10450

@andrewkroh andrewkroh added Integration:kubernetes Kubernetes flaky-test Unstable or unreliable test cases. Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] labels Apr 16, 2024
@MichaelKatsoulis
Copy link
Contributor

This is happening due to the addition of kubernetes metadata(lebels and annotations) in state_namespace metricset. The extra fields need to be defined in the base-fields.yml of state_namespace data stream like the rest of the data streams.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Unstable or unreliable test cases. Integration:kubernetes Kubernetes Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants