New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node: Add WireguardPubKey to ToCiliumNode #16420
Merged
aanm
merged 2 commits into
cilium:master
from
gandro:pr/gandro/wireguard-in-tociliumnode
Jun 8, 2021
Merged
node: Add WireguardPubKey to ToCiliumNode #16420
aanm
merged 2 commits into
cilium:master
from
gandro:pr/gandro/wireguard-in-tociliumnode
Jun 8, 2021
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
gandro
added
area/encryption
Impacts encryption support such as IPSec, WireGuard, or kTLS.
release-note/misc
This PR makes changes that have no direct user impact.
labels
Jun 3, 2021
test-me-please |
aanm
requested changes
Jun 3, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add the entry:
/pkg/node @cilium/agent
to the CODEOWNERS file? Thanks
This ensures the WireGuard public key is preserved when coverting a nodeTypes.Node object to a CiliumNode CRD. This conversion is currently only used for attaching external workloads (which has no support for WireGuard at the moment), but it might be used for other reasons in the future, therefore we should ensure that it propagates all information correctly. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
gandro
force-pushed
the
pr/gandro/wireguard-in-tociliumnode
branch
from
June 7, 2021 08:33
3d0c39e
to
45e71d1
Compare
test-me-please Edit: GitHub Image builder wasn't triggered. Had to close/reopen the PR. |
aanm
approved these changes
Jun 7, 2021
test-me-please |
christarazi
approved these changes
Jun 7, 2021
gandro
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jun 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/encryption
Impacts encryption support such as IPSec, WireGuard, or kTLS.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
This ensures the WireGuard public key is preserved when converting a
nodeTypes.Node
object to aCiliumNode
CRD. This conversion is currentlyis only used for attaching external workloads (which has no support for
WireGuard at the moment anyways), but it might be used in other places in the
future, therefore we should ensure that it propagates all information
correctly.
I discovered this while validating WireGuard support in Clustermesh.
This PR does not fix any outstanding bugs.