-
Notifications
You must be signed in to change notification settings - Fork 205
Use unique index for TestKubernetesJournaldInputOtel #11316
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
Use unique index for TestKubernetesJournaldInputOtel #11316
Conversation
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
michalpristas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved, data plane should be probably owner of this test though as it seems integration specific
That's a very good point @michalpristas. This test was created to ensure we can always ingest Journald logs when running Elastic Agent in a container, specially now that we depend on |
|
@Mergifyio backport 8.19 9.1 9.2 |
✅ Backports have been created
|
(cherry picked from commit efafc2a) # Conflicts: # testing/integration/k8s/journald_test.go
(cherry picked from commit efafc2a)
(cherry picked from commit efafc2a)
What does this PR do?
Use unique index for TestKubernetesJournaldInputOtel
Why is it important?
Closes #11220
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry in./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E test## Disruptive User ImpactHow to test this PR locally
Related issues
TestKubernetesJournaldInputOtel–Condition never satisfied#11220Questions to ask yourself