Multus/service mesh(istio, linkerd and so on) Interworking #982
Labels
Comments
ormergi
added a commit
to ormergi/kubevirtci
that referenced
this issue
Dec 13, 2022
Since Multus v4 it expects CNI net conf file to exist at '/etc/cni/net.d' but isitio generates then at '/etc/cni/multus/net.d'. Copy istio CNI net conf to where multus expects on cluster-up in order to enable deploying both Isitio and Multus until proper solution is available, tracking issue [1] [2]. [1] kubevirt#906 [2] k8snetworkplumbingwg/multus-cni#982 Signed-off-by: Or Mergi <[email protected]>
ormergi
added a commit
to ormergi/kubevirtci
that referenced
this issue
Dec 13, 2022
Since Multus v4 it expects CNI net conf file to exist at '/etc/cni/net.d' but isitio generates then at '/etc/cni/multus/net.d'. Copy istio CNI net conf to where multus expects on cluster-up in order to enable deploying both Isitio and Multus v4 until proper solution is available, tracking issue [1] [2]. [1] kubevirt#906 [2] k8snetworkplumbingwg/multus-cni#982 Signed-off-by: Or Mergi <[email protected]>
ormergi
added a commit
to ormergi/kubevirtci
that referenced
this issue
Dec 13, 2022
Since Multus v4 it expects CNI net conf file to exist at '/etc/cni/net.d' but isitio generates then at '/etc/cni/multus/net.d'. Copy istio CNI net conf to where multus expects on cluster-up in order to enable deploying both Isitio and Multus v4 until proper solution is available, tracking issue [1] [2]. [1] kubevirt#906 [2] k8snetworkplumbingwg/multus-cni#982 Signed-off-by: Or Mergi <[email protected]>
kubevirt-bot
pushed a commit
to kubevirt/kubevirtci
that referenced
this issue
Dec 14, 2022
Since Multus v4 it expects CNI net conf file to exist at '/etc/cni/net.d' but isitio generates then at '/etc/cni/multus/net.d'. Copy istio CNI net conf to where multus expects on cluster-up in order to enable deploying both Isitio and Multus v4 until proper solution is available, tracking issue [1] [2]. [1] #906 [2] k8snetworkplumbingwg/multus-cni#982 Signed-off-by: Or Mergi <[email protected]> Signed-off-by: Or Mergi <[email protected]>
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
revive |
|
Hi, is there any plan to fix this? |
|
Hi, is there a workaround or planned fix for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently multus and service mesh, istio, linkerd, open service mesh, does not have interworking appropriately. This issue is parent issue to track the issue.
The Goal
Service mesh with secondary network
Currently each service mesh does not recognize secondary network (as far as I know of). Kubernetes Network Plumbing WG is still working on how to integrate service mesh with multus for a while and it is not concluded yet. @plwhite, @dougbtv and @nicklesimba are working on that.
Current activities:
Service Mesh and Multi-Network enhancements proposal
Provide consistent install/interworking method (e.g. net-attach-def usage)
Currently some service mesh provides a way to interworking with multus, however, these methods are different, not unified. Some method provides a method which is not appropriate way and it could be improved by design.
#971 is the one of the issue.
Hence we need to come up with a optimized way (from multus point of view) and try to propagate to various service mesh projects.
The text was updated successfully, but these errors were encountered: