Skip to content

Conversation

@casualjim
Copy link
Contributor

@casualjim casualjim commented Dec 1, 2025

I have a nats cluster but it uses tls-first and a custom CA, with these changes the host and operator can communicate with it.

This was done by copilot, so I understand if you don't like these changes.

  • Understand the codebase and identify affected areas
  • Add --nats-tls-ca and --nats-tls-first flags to runtime-operator (Go)
  • Add --nats-tls-ca, --nats-tls-first, and --nats-creds flags to wash host command (Rust)
  • Update the connect_nats function in washlet to support TLS options
  • Build and test the changes
  • Run code review and address feedback
  • Fix CryptoProvider panic by using ring consistently across all TLS dependencies

@casualjim casualjim requested a review from a team as a code owner December 1, 2025 05:32
Copilot AI and others added 6 commits December 1, 2025 09:01
…-operator

Co-authored-by: casualjim <456109+casualjim@users.noreply.github.com>
Co-authored-by: casualjim <456109+casualjim@users.noreply.github.com>
…perator

Co-authored-by: casualjim <456109+casualjim@users.noreply.github.com>
Co-authored-by: casualjim <456109+casualjim@users.noreply.github.com>
Co-authored-by: casualjim <456109+casualjim@users.noreply.github.com>
@casualjim casualjim force-pushed the copilot/fix-nats-tls-configuration branch from be3b6dd to 3fcb088 Compare December 1, 2025 17:02
@lxfontes lxfontes moved this to Todo in wash v2 release Jan 7, 2026
@lxfontes lxfontes moved this from Todo to In Progress in wash v2 release Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

1 participant