Skip to content

tonic tls config#1

Merged
michaeldjeffrey merged 6 commits intomainfrom
mj/tonic-tls-config
Jan 27, 2026
Merged

tonic tls config#1
michaeldjeffrey merged 6 commits intomainfrom
mj/tonic-tls-config

Conversation

@michaeldjeffrey
Copy link
Copy Markdown
Collaborator

From tonic 0.10.2 -> 0.14.2, tls configuration is no longer
automatic. Hopefully the fix is as simple as adding this line.

  • extra
    • getting a signing keypair from settings does not need to box it's error.
    • manual debian builds will only kick off when manually dispatched

The DockerCI job will push to packagecloud if there's a tag, this job is
here to be manually triggered only.
From tonic `0.10.2` -> `0.14.2`, tls configuration is no longer
automatic. Hopefully the fix is as simple as adding this line.

- extra: getting a signing keypair from settings does not need to box
it's error.
The load balancer terminates TLS, and forwards regular traffic to the
service.
Silly of me to think that adding the tls-native-roots would mean they
automatically apply when you make a TLS Config for clients.
@michaeldjeffrey michaeldjeffrey merged commit 97396d3 into main Jan 27, 2026
28 checks passed
@michaeldjeffrey michaeldjeffrey deleted the mj/tonic-tls-config branch January 27, 2026 20:27
michaeldjeffrey added a commit to helium/oracles that referenced this pull request Jan 30, 2026
A companion PR to helium/oracles-iot#1

Enable TLS for tonic clients with enabled roots that are chosen from the features enabled when including tonic.
(currently "tls-native-roots")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants