proposal for ipsec e2e test #1401
Conversation
|
@xiaojiangao123: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Welcome @xiaojiangao123! It looks like this is your first PR to kmesh-net/kmesh 🎉 |
There was a problem hiding this comment.
Pull Request Overview
This PR proposes adding documentation for developing end-to-end tests for the IPsec functionality in Kmesh, detailing test scenarios and environment requirements.
- Introduces a new IPsec E2E testing proposal document in Chinese.
- Outlines three core test scenarios: basic connectivity, key update, and failure recovery.
- Specifies the test environment requirements and includes detailed testing steps.
|
Can you tell us about your thinking at this week's meeting? |
docs/proposal/ipsec_e2e_zh..md
Outdated
|
|
||
| ###### 测试步骤 | ||
|
|
||
| - 在不同节点部署httpbin和sleep应用 |
There was a problem hiding this comment.
Do you have to redeploy sleep and httpbin every step?
docs/proposal/ipsec_e2e_zh..md
Outdated
| @@ -0,0 +1,113 @@ | |||
| --- | |||
There was a problem hiding this comment.
FYI:
Design doc of Kmesh E2E framework: https://github.com/kmesh-net/kmesh/blob/main/docs/proposal/e2e.md
User guide: https://kmesh.net/en/docs/developer/e2e-guide/
and all test cases should be added in https://github.com/kmesh-net/kmesh/tree/main/test/e2e
You can write new test cases based on existing ones.
There was a problem hiding this comment.
Also English doc is prefered
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
|
||
|
|
||
| #### 3. Offload Authorization Test Scenarios | ||
| Apply the corresponding security policies (ALLOW/DENY) and routing strategies, and verify connectivity. Tests can be conducted at workload, namespace, and global scopes. |
There was a problem hiding this comment.
offload Authorization only support port and IP address.
The remaining Authorization types are handled in user space.
There was a problem hiding this comment.
In the project description of OSPP, there is a requirement for E2E testing excluding IP and port authentication.
There was a problem hiding this comment.
Yes. Kmesh supports these types of Authorization through offload authorization and user space Authorization.
Just a note that there is a difference between offload Authorization and User space Authorization in Kmesh's Authorization.
|
If you want to do this project, go to #1408 and leave a comment under it to let people know you are doing something on it. The mentor will |
LiZhenCheng9527
added
the
documentation
|
Adding label Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
The lack of end-to-end (e2e) testing for the IPsec functionality and offload Authorization in Kmesh.
Does this PR introduce a user-facing change?:
NONE