Replace the Bitnami Fluentd Helm chart in the Teleport Cluster helmfile release

Overview

Bitnami will stop updating their fluentd container image on August 28th (see announcement), so it needs to be replaced before then.

We use the Bitnami Fluentd Helm chart in our teleport-cluster helmfile release to ship event logs to GCS.

While their fluentd Helm chart will continue to be maintained, its future remains uncertain and we wouldn't want to risk having to replace it on short notice again. Also the chart relies heavily on additional logic built into their container image, so we can't simply replace it with the official container image. It's also overkill for our use case

Proposed plan of action

• Update our custom fluentd container image to be based of the official container image instead
• Build a simple local Helm chart in the teleport-cluster helmfile release that creates a fluentd deployment using the new custom image above, with only the configuration we need for our purpose
• Replace the Bitnami Fluent Helm chart with the new chart above

Optional: if we upgrade our GKE clusters to v1.33 first, instead of building a custom Fluentd image, build only an image containing the Fluent GCS plugin alone, and mount it into the pod container as a volume: https://kubernetes.io/docs/tasks/configure-pod-container/image-volumes/

Exit Criteria

• The teleport-cluster helmfile release no longer uses the Bitnami Fluentd helm chart and container image