-
Notifications
You must be signed in to change notification settings - Fork 208
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
check: add third client scheduled on a different node #2183
Conversation
78c8eb8
to
76f9005
Compare
76f9005
to
56ea409
Compare
56ea409
to
e27002a
Compare
e27002a
to
fabaf27
Compare
9d7fedd
to
8ee57b2
Compare
8ee57b2
to
199b4a8
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.
Why is a third client needed?
as I added on the commit message, for some upcoming tests we will need a new client scheduled on a different node than the first 2 clients (and these 2 clients always run on the same node, as client2 uses pod affinity to run on the same node as client1) |
63e29ee
to
667ede1
Compare
for some upcoming tests we will need a new client scheduled on a different node than the first 2 clients. This commit adds this new client. Signed-off-by: Gilberto Bertin <[email protected]>
667ede1
to
fdf7787
Compare
fdf7787
to
b43f0b2
Compare
Signed-off-by: Gilberto Bertin <[email protected]>
b43f0b2
to
99970b5
Compare
eks is failing due to a timeout, link to the green workflow after bumping it and running the workflow from PR https://github.com/cilium/cilium-cli/actions/runs/7220606369/job/19673889321?pr=2183 |
for some upcoming tests we will need a new client scheduled on a different node than the first 2 clients. This commit adds this new client.