I am not sure if this is intentional or not, but a InfluxDB 2.x node is unable to use custom certificates unless I uncheck TLS verification, which is undesirable. It is possible, however, to include the certificate chain with an InfluxDB v1.x node using a custom TLS config.
Unless this by design: Is it possible to include a way to specify a custom TLS configuration with InfluxDB v2.x nodes to achieve parity with InfluxDB v1.x nodes?
I am not sure if this is intentional or not, but a InfluxDB 2.x node is unable to use custom certificates unless I uncheck TLS verification, which is undesirable. It is possible, however, to include the certificate chain with an InfluxDB v1.x node using a custom TLS config.
Unless this by design: Is it possible to include a way to specify a custom TLS configuration with InfluxDB v2.x nodes to achieve parity with InfluxDB v1.x nodes?