[ACTION REQUIRED] Decommissioning of 'kube-fluentd-operator’ image

TL;DR: Chainguard intends to stop building kube-fluentd-operator, which is no longer being maintained upstream.

What is changing?

Chainguard will stop building the ‘kube-fluentd-operator’ container image in our catalog on January 28, 2026. 

Why is Chainguard making this change?

While there has been no official statement of depreciation from upstream, we have noticed a lack of updates, and despite attempts have received no communications from maintainers.

The last GitHub release tag was cut back in February 2024. Since then there has been a series of commits to the main branch through March 2025. However, the project has been inactive since March 2025, with no responses to our GitHub issues. A lack of updates and releases compromises the long-term security posture of the software, which is in conflict with Chainguard’s offerings.

How will this affect me?

We’ll continue to rebuild the most recent release of the application for customers with existing access to the image until the planned change date. Thereafter, we will stop further rebuilds of the image.

What do I need to do?

Customers should consider migrating to an alternative solution by January 26, 2026. While it’s not a direct replacement, Fluent Operator offers similar features and is available in our image catalog. To support your transition, we will sync over Fluent Operator to your registry.

Need help or have questions?

We're here to help - visit our support portal at support.chainguard.dev.

- Chainguard Team