Support deploying unikernels via TLS endpoint #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Firobe
force-pushed
the
deploy-tls
branch
4 times, most recently
from
7524fb9 to
0adff55
Compare
Firobe
changed the title
Closed
Given a TLS config, support deploying to a remote TLS albatross endpoint instead of a local socket. This has no effect on the publication and collection of IPs via the iptables daemon, which only works with a local socket.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Given a TLS config, support deploying to a remote TLS albatross endpoint instead of a local socket.
This has no effect on the publication and collection of IPs via the iptables daemon, which only works with a local socket.