Summary

The Java driver does not support the tlsCertificateKeyFile and tlsCAFile connection string parameters (JAVA-3066) and instead uses a "trust store" to keep TLS secrets. Currently the Kind testing setup expectes to be able to specify TLS secrets via the connection string, so cannot properly configure the Java workload executor.

Set up a trust store for the Java driver via the workload exectuor script to allow it to connect to the Kind clusters that use test-specific TLS certs and CAs. See a guide for setting up a trust store here.

Motivation

Who is the affected end user?

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?