Open PranavBhatSF opened 1 month ago
What happens if you try ghcr.io/kube-logging/fluentd:v1.16-4.9-filters
instead of full?
Even with ghcr.io/kube-logging/fluentd:v1.16-4.9-filters we are seeing same issue.
We had this issue with the azure plugin and had to remove it because of the same reason. I'm not aware of a good resolution to this problem and would be good if someone could take a deeper look. To make things worse the underlying plugin is not maintained and the ruby library is already deprecated. We would need to look at a more future proof solution here that is based on the supported Rest API ideally.
Usecase
We need to push kubernetes pod logs to Azure, S3 or Splunk based on the configuration.
What we have done
Built a custom image with Fluentd image as base and included the required plugins. Dockerfile
Issue
Fluentd is pushing logs to S3 and Azure. But when we configure splunk as destination,
fluentd-configcheck
pod fails with the below error