Add NATS TLS configuration options to wash host and runtime-operator #183
+103
−117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
--nats-tls-caand--nats-tls-firstflags to runtime-operator (Go)--nats-tls-ca,--nats-tls-first, and--nats-credsflags towash hostcommand (Rust)connect_natsfunction in washlet to support TLS options