[DRIVERS-2428] Update .NET workload executor in Astrolabe to support TLS secrets Created: 31/Aug/22 Updated: 27/Sep/22 Resolved: 27/Sep/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Astrolabe, Containerized Testing |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Matt Dale | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Epic Link: | DRIVERS-718 | ||||||||||||||||
| Driver Changes: | Not Needed | ||||||||||||||||
| Quarter: | FY23Q1 | ||||||||||||||||
| Description |
SummaryThe .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. MotivationWho 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? |
| Comments |
| Comment by James Kovacs [ 27/Sep/22 ] |
|
The .NET/C# Driver already has EG tests that convert and install TLS certificates in the appropriate places for various operating systems. Thus we already test secure TLS configuration in EG. We are considering adding PEM file support in CSHARP-4336 due to Microsoft adding support for PEM files in .NET 5. We can leave the Astrolabe .NET/C# test suite using insecure for the time being as we are testing secure TLS configuration elsewhere. |