search

networkservicemesh / deployments-k8s

Apache License 2.0
41 stars 32 forks source link

Bug with kernel-chain-composition #12089

Open isZams opened 3 weeks ago

isZams commented 3 weeks ago

Hello everyone. I am experiencing a problem with the composition of endpoints where I am using the kernel interfaces. More precisely, I have a chain consisting of: nsc - suricata - squid - nse.

Here there are the file that i'm currently using: kernel-chain.zip

As you suggested in the past I am using the combination of the annotations to have two kernel interfaces within the pods in the middle of the chain. So each pod used to be a security function will have 3 containers: cmd-icmp-nse-responder, cmd-nsc and just the one for the security function. My problem is related to Squid's pod, where I cannot get the two interfaces I need. I test separately the 2 security functions and they works. Among the log logs of the cmd-nsc container I have this error, but I really don't know how I can solve it. Do you have any ideas? Thanks in advance for your help and your attention.

isZams commented 3 weeks ago

I noticed that the bug relates to the order in which the deployments are made, as it is as if there is a problem with the creation of the interfaces. By doing the single deployment of the pods in the chain, instead of using kustomization, I am able to achieve the desired result.

NikitaSkrynnik commented 3 weeks ago

Hello! Unfortunately the current Release is full and in progress now. We might consider this issue in the next release which will be started in July.