-
Notifications
You must be signed in to change notification settings - Fork 119
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
SRIOV provider: Deploy default CNI #644
SRIOV provider: Deploy default CNI #644
Conversation
Skipping CI for Draft Pull Request. |
/test check-up-kind-1.19-sriov |
5108c22
to
427c6ce
Compare
/test check-up-kind-1.19-sriov |
/test check-up-kind-1.19-sriov |
9a9367d
to
427c6ce
Compare
Test SRIOV provider with kindnet CNI instead of Calico and run conformance tests. Signed-off-by: Or Mergi <[email protected]>
Test SRIOV provider with kindnet CNI instead of Calico and run conformance tests. Signed-off-by: Or Mergi <[email protected]>
Test SRIOV provider with kindnet CNI instead of Calico and run conformance tests. Signed-off-by: Or Mergi <[email protected]>
Test kubevirt SRIOV tests when deploying KinD default CNI plugin, 'kindnet', instead of Calico. Signed-off-by: Or Mergi <[email protected]>
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.
Very nice!
427c6ce
to
10ff3e6
Compare
10ff3e6
to
39b4f0e
Compare
Test SRIOV provider with kindnet CNI instead of Calico and run conformance tests. Signed-off-by: Or Mergi <[email protected]>
Test SRIOV provider with kindnet CNI instead of Calico and run conformance tests. Signed-off-by: Or Mergi <[email protected]>
@EdDev I addressed you review comment could you please take another look? |
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.
Does this change mean we do not deploy dual-stack anymore on the SR-IOV lane? I could not understand that part from the commit message.
And if not, does kindnet
support it (so we can add it)?
Yes its single stack now,
In general kindnet supports dual-stack |
If it is easily addable, then can we do it now? It is not a must, but it will be nicer so we will not need to think about it in the future. |
With the new Kind API its pretty straight forward https://kind.sigs.k8s.io/docs/user/configuration/#networking |
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!
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.
ohh, what about ./cluster-up/cluster/kind/manifests/kube-calico.yaml.in
?
EDIT: Also ./cluster-up/cluster/kind/manifests/kube-calico.diff.in
While back then we decided to deploy Calico CNI on KinD providers in order to create dual-stack cluster for DEV and CI env's. As for today we managed to enable dual-stack clusters using our VM based providers, and eventually removed the IPV6 KinD based provider. Though we still deploy old version of Calico on Kind infra providers. We should use the default KinD CNI 'kindnet' instead, it will reduce complexity of the setup and maintenance. Signed-off-by: Or Mergi <[email protected]>
39b4f0e
to
9a80eeb
Compare
@EdDev Done |
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!
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.
@ormergi Thank you!
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enp0s3 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 |
``` 2c2862b cnao, Bump CNAO to 0.58.0 on all providers (kubevirt/kubevirtci#664) ba05421 cluster-provision, Prefetch cdi images (kubevirt/kubevirtci#660) 71d8ce5 Bump k8s providers (kubevirt/kubevirtci#661) 0007793 cdi, Bump cdi to 1.36.0 on k8s-1.21 (kubevirt/kubevirtci#659) 9c1261b Kind infra providers: Deploy default CNI (kubevirt/kubevirtci#644) ``` Signed-off-by: Or Shoval <[email protected]>
While back then we decided to deploy Calico CNI on KinD providers
in order to create dual-stack cluster for DEV and CI env's.
As for today we managed to enable dual-stack clusters using our
VM based providers, and eventually removed the IPV6 KinD based provider.
Though we still deploy old version of Calico on the SRIOV lane provider.
We should use the default KinD CNI 'kindnet' instead,
it will reduce complexity of the setup and maintenance.
Signed-off-by: Or Mergi [email protected]