-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 test case for calico using etcd datastore #10722
Add test case for calico using etcd datastore #10722
Conversation
477c14f
to
4a517d9
Compare
4a517d9
to
e94f4a6
Compare
This was supposed to fail, damn it 😆 . @olevitt what are the trigger conditions precisely ? Checking network connectivity between 2 pods on different nodes ? |
The fail is that all calico-nodes get the same
|
- Spawning 2 pods in different nodes results in them getting allocated in the same IP range (note that this only applies to newly created pods, not existing pods at thé time of the upgrade)
-> that's probably this, I think not all the tests use several nodes, and I just grabbed the first template ^^.
|
e94f4a6
to
7b58222
Compare
7b58222
to
dbd152d
Compare
https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/5760969640 Yeah o/ think I got it. @floryut wdyt of a new CI layout to catch that kind of stuff ? See the "Add multinode ci layout" commit |
dbd152d
to
ed33870
Compare
/hold cancel |
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 @VannTen
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mzaian, VannTen, yankay The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Add multinode ci layout * Add test case for calico using etcd datastore
* Add multinode ci layout * Add test case for calico using etcd datastore
* CI: Document the 'all-in-one' layout + small refactoring (#10725) * Rename aio to all-in-one and document it ADTM. Acronyms don't tell much. * Refactor vm_count in tests provisioning * Add test case for calico using etcd datastore (#10722) * Add multinode ci layout * Add test case for calico using etcd datastore * Fix calico-node in etcd mode (#10438) * Calico : add ETCD endpoints to install-cni container * Calico : remove nodename from configmap in etcd mode --------- Co-authored-by: Olivier Levitt <[email protected]>
* Add multinode ci layout * Add test case for calico using etcd datastore
What type of PR is this?
/kind feature
What this PR does / why we need it:
To catch stuff like #10436
Special notes for your reviewer:
This should not be merged, this is to verify that current master fails with calico etcd.
#10438 should be rebased on top of this to check if does fix the failure.
/hold
Does this PR introduce a user-facing change?: