Skip to content
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

Bug with kernel-chain-composition #12089

Open
isZams opened this issue Jun 17, 2024 · 2 comments
Open

Bug with kernel-chain-composition #12089

isZams opened this issue Jun 17, 2024 · 2 comments

Comments

@isZams
Copy link

isZams commented Jun 17, 2024

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 isZams closed this as completed Jun 17, 2024
@isZams isZams reopened this Jun 18, 2024
@isZams
Copy link
Author

isZams commented Jun 18, 2024

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
Copy link
Collaborator

NikitaSkrynnik commented Jun 19, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants