-
Notifications
You must be signed in to change notification settings - Fork 210
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
Extend upgrade test for IPsec key rotation test #1798
Extend upgrade test for IPsec key rotation test #1798
Conversation
5a7d270
to
ade1392
Compare
ade1392
to
6e8bd3f
Compare
6e8bd3f
to
3505a5d
Compare
bba7135
to
c533f45
Compare
c533f45
to
47d20f3
Compare
CI failed on "Clean up EKS":
|
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.
Nice PR! I can't wait to have those tests automated 😅
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't wait to see this in action! A few nits.
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.
It looks great!
Just need to fix the commit history and we should be good to merge on my side :-)
This commit generalizes upgrade test so ipsec key rotation test can work on that with little extension. Basically it's just some rename works with no logic change, something like moving "--include-upgrade-test" to "--include-conn-disrupt-test". Signed-off-by: Zhichuan Liang <[email protected]>
4ed0089
to
ae905f0
Compare
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.
Thanks!
ae905f0
to
d0769e2
Compare
This commit adds a new scenario for checking IPsec xfrm errors as a part of conn disrupt test. It compares the current xfrm status with previous record. In detail, the test consists of 3 steps: 1. Run "cilium-cli connectivity test --conn-disrupt-test-setup --include-conn-disrupt-test" to deploy connectivity sensitive pods, then record the current restart counts and xfrm error counts. 2. Perform IPsec key rotation. This part can be done in the ci-e2e. 3. Run "cilium-cli connectivity test --include-conn-disrupt-test" to check restart counts and xfrm error counts again, test fails if any diff found. Signed-off-by: Zhichuan Liang <[email protected]>
d0769e2
to
3303538
Compare
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.
Approving on behalf of CLI. I think the flag replacement is reasonable.
This PR extends upgrade test, so IPsec key rotation interruption test can base on the same workflow.
The expected test flow is:
Partially Fixes: cilium/cilium#26350
Signed-off-by: Zhichuan Liang [email protected]