-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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_logs
source seems to fail to annotate when pod names are reused
#13467
Comments
Hello. Any updates here? We are suffering :( |
Hi @r0b3r4 ! Unfortunately not yet, but it is on our backlog. We are also happy to help guide a contribution if someone has the time and ability to address it. |
Hello, Error
is happened here vector/src/sources/kubernetes_logs/mod.rs Line 498 in c402e6e
and
or here
Second variant is more suitable And i think it's happened because stored information about pod is deleted with event vector/src/kubernetes/reflector.rs Line 38 in c402e6e
After pod is deleted (some one wrote that problem is appear when the pod scale down and up and it's name is the same) event It's just my opinion based on my investigation of the problem. |
comment:
I think it won't work
he looks like this
and when we try
the method at work will not be based on the data of this field |
Thanks @sillent . It does appear to be the case that the |
Maybe we should consider having our own metadata cache based on uid instead of changing the event order of |
I have steps to reproduce the problem. Hope it helps. Arch: x86_64
|
Any news :)? |
See my comment here, but in summary version 0.25.0 seems to contain a temporary or partial fix to this issue. I wasn't able to locate anything mentioning this in the release notes for this version, so some people may have missed it. After upgrading to this version a couple weeks ago, I haven't had any annotation issues. |
The only thing that confuses me that fix somehow connected with non-related options. As i understand this might works only like temporary kludge, right? version >=0.25.x +
|
@r0b3r4 The config options were only helpful in the linked issue for me, while upgrading to version |
It seams we are having a related problem to this issue. In our case we are not using stateful sets but Pods directly which reuse names in the same namespace over time. My assumption is that #21303 is a draft at the moment for discussion. Potentially it is enough to only store the uid in favor of name and namespace? EDIT: |
Thanks for taking a look at this @scMarkus ! The PR you put together would have been roughly what I expected so I'm surprised it didn't work for you 🤔 |
A note for the community
Problem
Vector seems to fail to annotate logs from the
kubernetes_logs
source when pod names are reused. I didn't reproduce this, but there are a few comments (in the references section) that seem to indicate this is the case.One hypothesis is that
vector/src/sources/kubernetes_logs/pod_metadata_annotator.rs
Line 100 in aee1984
uid
as well (underextra
) rather than just name and namespace.Configuration
No response
Version
vector 0.22.3
Debug Output
No response
Example Data
No response
Additional Context
No response
References
annotation_failed
errors #12909 (comment)The text was updated successfully, but these errors were encountered: