SecureComms: Add support daemonConfig #2065
Open
+330
−158
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
davidhadas
force-pushed
the
secComms_daemonConfig
branch
from
c04060f
to
fb0eee2
Compare
davidhadas
force-pushed
the
secComms_daemonConfig
branch
from
fb0eee2
to
540bcff
Compare
|
/hold |
davidhadas
force-pushed
the
secComms_daemonConfig
branch
from
540bcff
to
2a572ab
Compare
|
/unhold |
davidhadas
force-pushed
the
secComms_daemonConfig
branch
4 times, most recently
from
f464fe6
to
aadaddc
Compare
davidhadas
force-pushed
the
secComms_daemonConfig
branch
2 times, most recently
from
688ee74
to
88f14cd
Compare
|
cc: @bpradipt |
| flags.StringVar(&secureCommsOutbounds, "secure-comms-outbounds", "", "WN Outbound tags for secure communication tunnels") | ||
| flags.StringVar(&secureCommsPpInbounds, "secure-comms-pp-inbounds", "", "PP Inbound tags for secure communication tunnels") | ||
| flags.StringVar(&secureCommsPpOutbounds, "secure-comms-pp-outbounds", "", "PP Outbound tags for secure communication tunnels") | ||
| flags.StringVar(&secureCommsKbsAddr, "secure-comms-kbs", "kbs-service.trustee-operator-system:8080", "Address of a Trustee Service for Secure-Comms") |
davidhadas
force-pushed
the
secComms_daemonConfig
branch
2 times, most recently
from
2dc05eb
to
4dbf850
Compare
Support configuring the APF Secure Comms from the CAA side including: - WN public Key - PP private key - Activating Secure Comms - inbouns and outbounds of th PP This is useful for activating Secure Comms from the CAA and without Trustee. It can be used for Testing without producing dedicated podvms which activate Secure Comms and set Inbounds/Outbounds by default. It can also be used for non-Coco peerpods. Signed-off-by: David Hadas <david.hadas@gmail.com>
davidhadas
force-pushed
the
secComms_daemonConfig
branch
from
4dbf850
to
de4bd7c
Compare
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.
See:
Support configuring the APF Secure Comms from the CAA side including:
This is useful for activating Secure Comms from the CAA and without Trustee. It can be used for Testing without producing dedicated podvms which activate Secure Comms and set Inbounds/Outbounds by default. It can also be used for non-Coco peerpods.