Which is the correct option to forward logs from Tanzu Kubernetes Grid clusters to Elastic, Kafka, Splunk or an HTTP endpoint?

Tanzu Kubernetes Grid (TKG) integrates with external logging solutions by deploying a log forwarder onto the Kubernetes clusters. The officially documented and recommended method is to deploy Fluent Bit, a lightweight and extensible log processor and forwarder. Once deployed as a DaemonSet on the cluster, Fluent Bit can be configured with various output plugins to collect logs from all nodes and containers and forward them to a wide range of backends, including Elastic (Elasticsearch), Kafka, Splunk, and generic HTTP endpoints, as specified in the question.

A. Log forwarding in Tanzu Kubernetes Grid is not an automatic, zero-configuration feature. An administrator must explicitly deploy and configure a log forwarding agent.
B. The kubectl logs command is a CLI tool for manually viewing or streaming logs from a specific pod. It is not a scalable, persistent, or cluster-wide log forwarding solution.
C. This option is incorrectly phrased. Fluent Bit is deployed on the TKG cluster to forward logs to a backend like vRealize Log Insight (now Aria Operations for Logs), not as a plugin to it.

1. VMware Tanzu Kubernetes Grid 1.6 Documentation

Deploy Fluent Bit for Log Forwarding. This section explicitly states

"Fluent Bit is a lightweight log processor and forwarder. You can deploy it on Tanzu Kubernetes clusters to set up a logging backend for your workloads. After you have deployed Fluent Bit on a cluster

you can configure it to forward logs to a logging provider

for example

Elasticsearch

Kafka

Splunk

or an HTTP endpoint."

Source: VMware Tanzu Kubernetes Grid 1.6 Documentation

Section: "Integrating Tanzu Kubernetes Grid with Logging

Monitoring

and Alerting Solutions".

2. VMware Tanzu Kubernetes Grid 2.4 Documentation

About Logging and Monitoring in TKG. This document reinforces the concept of integrating with external solutions

stating

"Tanzu Kubernetes Grid does not deploy with an in-cluster logging or monitoring solution by default. You must integrate your Tanzu Kubernetes clusters with an external logging and monitoring solution..." It then provides guidance on deploying agents like Fluent Bit.

Source: VMware Tanzu Kubernetes Grid 2.4 Documentation

Section: "Logging and Monitoring".