What are you experiencing? What are you expecting to happen?
Today, the Logging Stack 5.8 or higher permits to create ClusterLogForwarder resource to deploy/configure Vector daemonset in order to collect and forward logs to backends like Loki, Elasticsearch, Kafka and others.

In our context, hundreds user projects, we would like to have generic ClusterLogForwarder configuration to any project using vector to vector :

• user project deploys a Vector helm chart with its custom configuration (add/del label, any parsing, ...) and then forward them to its destination backend (any kind supported by Vector).
• cluster admin configures the ClusterLogForwarder resource to forward logs to the user project Vector, using Vector output type, without any custom configuration except the url.

 Vector documentation:

• source: https://vector.dev/docs/reference/configuration/sources/vector/
• sink : https://vector.dev/docs/reference/configuration/sinks/vector/

In conclusion, is it possible to support vector ouput type to ClusterLogForwarder ?

Define the value or impact to you or the business
This feature would simplify admin tasks when endusers want to forward logs with custom configuration to their Logging backend.