Plumb additional TLS configuration

[zalegrala]

No description provided.

[zalegrala]

Testing this out doesn't seem to work correct. I have the following, but I don't think the new TLS values are being used. Any pointers?

const client = new tracing.Client({
  endpoint: 'https://ingest.trace.svc.cluster.local:4317',
  exporter: tracing.EXPORTER_OTLP,
  insecure: false,
  tls_server_name: 'tempo.trace.svc.cluster.local',
  tls_ca_file: '/tls/ca.crt',
  tls_cert_file: '/tls/tls.crt',
  tls_key_file: '/tls/tls.key',
  headers: { 'X-Scope-OrgID': randomOrg },
})

[mapno]

WDYT of directly vendoring the otel TLS config block?

[zalegrala]

Ah yes, good idea.

[zalegrala]

I was able to validate these changes. The json tags on the config object are not honored, and instead, the default translation is required. This means that instead of the json tag of server_name_override on the go struct, the name of the struct is matched, and so just server_name is used. Additionally, to specify the CAFile where the struct has ca_file, users need to specify c_a_file.