-
Notifications
You must be signed in to change notification settings - Fork 0
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
Containerd log format does not work properyl with current fluentd config #1399
Comments
@QuentinBisson do you know how to solve this issue? |
This requires us to upgrade the fluent-bit app in the fluent logshipping app and to add the new cri parser that exists upstream and configure it for the specific kubernetes versions |
This worked for or customer FYI
|
@giantswarm/team-phoenix do we have a way to know if we are usign docker or CRI? Either a kubernetes version, or smth else? Otherwise we will have to enforce customer configuration |
Thanks I'll see if I can access that using helm .Capabilities, otherwise, can I assume versions 18+ are using containerd? |
yes |
Fixed by giantswarm/fluent-logshipping-app#93 |
Is your feature request related to a problem? Please describe.
Since we have switched from docker-shim to containerd the log format has changed and now the logs are processed by EFK weirdly in fluentd logging app.
Describe the solution you'd like
We need to change fluentd collector to parse the new format correctly
fluent/fluentd-kubernetes-daemonset#412
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: