-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
ci: add tests for migration to CiliumEndpointSlice #32268
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
c7a29a6
to
018e95a
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.
Overall this looks great, thanks for taking this on! I left a few in-line suggestions. You may also want to add steps for merging the sysdumps together and updating the commit status (I believe this is needed in order to prevent skipped
from reporting as failed).
Could you also squash your commits?
Just realized I jumped the gun a bit and this is still marked as draft 😅 Feel free to retag me for review when it's ready |
No problem! Thank you for your feedback, I'll go through them and update accordingly :) |
This comment was marked as resolved.
This comment was marked as resolved.
d815d83
to
6e133bc
Compare
6e133bc
to
5927ca1
Compare
The connectivity test failures for client-egress-l7/pod-to-world/http-to-one.one.one.one, client-egress-l7-named-port/pod-to-world/http-to-one.one.one.one, pod-to-ingress-service/pod-to-ingress-service observed seem to be related to the Cilium Agent restart, rather than migration to CES. -> #32611 |
c79c251
to
d92778b
Compare
Hi @thorn3r, I think I'm ready for a re-review! :) |
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 work 😎 I left a couple small suggestions, but other than that it LGTM
1365756
to
538b222
Compare
0851d09
to
e185587
Compare
5c7340a
to
b0e0226
Compare
Thanks everyone for all the help and feedback :) I think I'm ready for another review now (cc @thorn3r) |
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.
LGTM! 🚢
63390c4
to
3ae3c8a
Compare
This commit adds CI to test that the migration from CiliumEndpoint to CiliumEndpointSlice does not disturb long-lived connections. A Kind cluster is set up without CiliumEndpointSlice enabled. Long-lived connections are set up. Then, CES is enabled, the operator is restarted and then the agent, after the CES CRD is created. Then, the connectivity test is run to ensure long-lived connections were not broken. Signed-off-by: jshr-w <shjayaraman@microsoft.com>
3ae3c8a
to
d97bd3f
Compare
/test |
@viktor-kurchenko @nbusseneau Hi, I think this PR is blocked on codeowner review from ci-structure, would you be able to help with this please? |
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.
LGTM, thank you!
uses: ./.github/actions/conn-disrupt-test | ||
with: | ||
job-name: ces-enable | ||
operation-cmd: | | ||
kubectl patch -n kube-system configmap cilium-config --type merge --patch '{"data":{"enable-cilium-endpoint-slice":"true"}}' | ||
|
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.
I believe the usage of conn-disrupt-test
needs adjustment for the changes in #32930.
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.
Yep, just mentioned the same: https://cilium.slack.com/archives/C069SNDMLA2/p1718286768251579
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.
The path filter should also be modified so that these changed are detected immediately.
migration test to fail. This PR updates the test to work with the updated test format. The inconsistency was not caught because of the path filters used in the test, so the path filters have been updated to exclude only Documentation/ and test/. Fixes: cilium#32268 Signed-off-by: jshr-w <shjayaraman@microsoft.com>
PR cilium#32930 introduced a change to the conn-disrupt test that caused this migration test to fail. This PR updates the test to work with the updated test format. The inconsistency was not caught because of the path filters used in the test, so the path filters have been updated to exclude only Documentation/ and test/. Fixes: cilium#32268 Signed-off-by: jshr-w <shjayaraman@microsoft.com>
PR cilium#32930 introduced a change to the conn-disrupt test that caused this migration test to fail. This PR updates the test to work with the updated test format. The inconsistency was not caught because of the path filters used in the test, so the path filters have been updated to exclude only Documentation/ and test/. Fixes: cilium#32268 Signed-off-by: jshr-w <shjayaraman@microsoft.com>
PR cilium#32930 introduced a change to the conn-disrupt test that caused this migration test to fail. This PR updates the test to work with the updated test format. The inconsistency was not caught because of the path filters used in the test, so the path filters have been updated to exclude only Documentation/ and test/. Fixes: cilium#32268 Signed-off-by: jshr-w <shjayaraman@microsoft.com>
PR #32930 introduced a change to the conn-disrupt test that caused this migration test to fail. This PR updates the test to work with the updated test format. The inconsistency was not caught because of the path filters used in the test, so the path filters have been updated to exclude only Documentation/ and test/. Fixes: #32268 Signed-off-by: jshr-w <shjayaraman@microsoft.com>
This PR adds CI to validate the migration path from CiliumEndpoint to CiliumEndpointSlice, by checking that the migration does not affect connectivity on a migrated cluster.
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
Fixes: #32057