vector: kube API server certificate validation failure due to hostname mismatch

Using the kafka output in a lab environment, the customer is seeing TLS 'hostname mismatch' errors when vector tries to connect to a kafka broker.

From the attached information (logforwarderissue.tgz) it does appear that the certificates are valid, however we are unable to reproduce the failure in a stand-alone setting.

Need to determine if this is a

1. vector bug - upgrade or provide upstream fix to vector
2. problem with how the CLF configures vector - fix the config generator
3. problem with customer certificates - explain what is wrong and how to correct