-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Unknown
-
None
-
Component/s: Astrolabe, Containerized Testing
-
None
-
Not Needed
Summary
The .NET Kind test tasks currently (as of this PR) run with an insecure TLS configuration (i.e. tlsInsecure=true) because the .NET driver doesn't support loading TLS and CA certificates using the tlsCertificateKeyFile and tlsCAFile connection string parameters. Update the .NET AstrolabeWorkloadExecutor and/or the .NET workload executor script to support loading TLS and CA certificates during Kind test tasks.
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?
- depends on
-
DRIVERS-2419 Add Linux build for C#/.NET driver to Astrolabe to test with Kind
- Closed
- related to
-
DRIVERS-2420 Update Java workload executor in Astrolabe to support TLS secrets
- Closed