Learn how to set up a cost-effective Kubernetes logging pipeline using Fluent-bit and Fluentd with Helm charts. The solution combines short-term log storage in Elasticsearch (1-month retention) with long-term archiving in AWS S3 (6-month retention) to optimize costs. Fluent-bit acts as a lightweight log collector on Kubernetes nodes, while Fluentd aggregates and forwards logs to multiple destinations. The guide includes complete Helm configuration files and deployment commands for both components, plus best practices for secure log transfer, resource management, and retention policies.
Table of contents
Introduction: Why K8s Log Fluentd is CriticalFluent-bit vs Fluentd: Roles in K8s LoggingInstalling Fluent-bit Helm Chart for K8s LogsInstalling Fluentd Helm Chart for Aggregation & ForwardingInstalling Fluentd Helm Chart for forwarding Logs to Elastic Search as well as S3Cost Optimization with Elasticsearch + S3Best Practices for K8s Log Fluentd PipelinesHow Devtron Makes This EasierFAQSubscribe to our NewsletterSort: