This is a special update to the original Controlling Logs with Fluent Bit on Kubernetes article published previously that is no longer valid.
The issue requiring this update arose over last weekend when I discovered that Broadcom, who acquired VMWare, who were the custodians of the bitnami catalog, did something not so nice to all of us.
In this issue, they announced that the catalog would be moved in August 2025 to a legacy catalog in favor of a 'secure' catalog and no longer updated.
This meant that the current Logs Control Easy Install project, the workshop Controlling Logs with Fluent Bit on Kubernetes, and the original article had to all be updated. I spent this last weekend and most of this week bringing all three of these artifacts up to date with a new application workload to replace the use of Ghost CMS.
Let's take a look at what these changes meant to the original article and provide you with a new guide, using Fluent Bit to get control of logs on a Kubernetes cluster.