Sidecar InitContainers Support

Finout includes Prometheus metrics from both main containers and persistent initContainers, ensuring more accurate Kubernetes cost attribution by capturing resource usage beyond the primary workload.

Definitions:

• Main container – The primary application container within a pod, responsible for executing the workload’s core functionality.

• Sidecar InitContainer – A special type of Kubernetes initContainer introduced in Kubernetes v1.29, which can remain active for the entire pod lifecycle. This enables side processes such as logging or proxying to run continuously, unlike traditional initContainers that are always short-lived.

With this change, Finout’s exporter v1.30 added support for collecting initContainer resource request metrics for cost attribution. Prior to the exporter’s v1.30, these metrics were not included. While short-lived initContainers still have negligible cost impact, persistent initContainers (used as sidecars) are now accurately reflected in the cost calculation.

The updated cost data will appear in the Finout after 2 days.

Configuration Result:

After configuring the final step, the CronJob starts exporting data from Prometheus into your S3 bucket. After the integration, the Kubernetes cost data may take up to 24 hours to become available in your Finout account.

If this process fails, guidance is provided in the Finout console to help resolve the problem, or review the FAQs and Troubleshooting, as this will assist you to fix any errors easily.