-
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): vector 0.44 seems that it fails to watch some pods or log change #22235
Comments
Hi @titaneric, do you suspect that this PR #21905 introduced a regression? |
Yes, I have updated the issue, and I found that the #21905 did change the behaviour in my environment |
I find the root cause of this issue. I notice that vector call the k8s api server with the following request
Notice that it queries the pods with
I think the query filter's result is NOT what we expected. |
A note for the community
Problem
Hi, I had updated the vector to 0.44 in our cluster, and I noticed that it failed to watch some pod's log file change.
Original log event
Failed log event
Notice that it does detect some files, but it only detect very little logs instead ALL logs.
I am still trying to figure out what's the difference between these logs, and I will update this issue once I find out it.
Our initial vector's version is 0.42.0, and I also try 0.43.1 and it works fine.
Configuration
Version
0.44.0-distroless-libc
Debug Output
Example Data
No response
Additional Context
Kubernetes version: 1.24
Worker node info:
helm chart version: 0.37.0
References
I have done some study to the change between 0.43.1 and 0.44.0, and I notice that there is a PR #21905 which have updated the
kubernetes_logs
source. I checkout tov0.44.0
and removed that commit from the git history, rebuild the binary and docker, and deploy it to our cluster. Unfortunately, it works. As a result, I highly suspect there is some breaking change introduced to the #21905.My git repo: https://github.com/titaneric/vector/tree/feat/vector-debug
Updated:
I checkout to
cd87af9152
(the one commit before #21905) and verify it works, and I checkout to92d869a59c
(the commit of #21905)) and it does emit the logs I posted in this issue.The text was updated successfully, but these errors were encountered: