-
Notifications
You must be signed in to change notification settings - Fork 391
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
Add job to run e2e test with traffic encrytion mode as WireGuard #7086
base: main
Are you sure you want to change the base?
Conversation
/test-kind-e2e-wireGuard |
1 similar comment
/test-kind-e2e-wireGuard |
/test-kind-e2e-wireguard |
as WireGuard Signed-off-by: Pulkit Jain <[email protected]>
b92cf6a
to
b5af7ac
Compare
@@ -74,7 +75,8 @@ Run K8s e2e community tests (Conformance & Network Policy) or Antrea e2e tests o | |||
--proxyall Enable proxyAll to test AntreaProxy. | |||
--build-tag Custom build tag for images. | |||
--docker-user Username for Docker account. | |||
--docker-password Password for Docker account." | |||
--docker-password Password for Docker account. | |||
--traffic-mode Traffic Encryption mode." |
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.
Seems like traffic mode net new in this PR, is that right? Perhaps we can specify the only supported parameter (unless there are others?)
--traffic-mode Traffic Encryption mode." | |
--traffic-mode Traffic Encryption mode: Only `wireGuard` is supported" |
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.
@petertran-avgo , ipsec encryption is also supported however it needs additional kernel module on k8 node as prerequisites, it could be preferred to keep description generic to provide future e2e tests for ipsec.
Add job to run e2e test with traffic encrytion mode as WireGuard.
Fixes #7075.