DEV Community

Discussion on: Pod-to-pod network delays in AKS

Collapse
 
alancdias7 profile image
Alan

Hello good afternoon.

Thanks for sharing knowledge.

I am following the deployment script, however, when running the command to check the application pod, the ksniff de pod is not created.

I checked on the internet and found a reference saying I should add the following parameter to the command: --socket /run/k3s/containerd/containerd.sock

This caused the ksniff pod to be created, but ksniff cannot mount the volume.

Did you do something different from what is in the publication to make the solution fit to be used in AKS?

Collapse
 
deyanp profile image
Deyan Petrov • Edited

What does kubectl get events say?

I dont remember anymore, but must have dilligently described what I did ...

Collapse
 
alancdias7 profile image
Alan

Thanks for answering.

Executing the command without entering the parameter --socket /run/k3s/containerd/containerd.sock the error presented is: ctr: container "ksniff"" in namespace "k8s.io": not found

Inserting this parameter the pod is deployed, however, the volume is not mounted and reports the error: Unable to attach or mount volumes: unmounted volumes=[container-socket], unattached volumes=[container-socket host default-token-7tfcb] : timed out waiting for the condition

I opened a support request in the Ksniff project, but so far I haven't had any feedback.

github.com/eldadru/ksniff/issues/132

Thread Thread
 
deyanp profile image
Deyan Petrov

I am not sure what command you are sending ..

I see in your github issue this:

kubectl sniff -p nginx -n sniff --socket /run/k3s/containerd/containerd.sock -v

maybe you should try rearranging the parameters, and making sure nginx is the pod name (and the pod really exists), and sniff is the namespace name (and it really exists) ...

kubectl sniff POD-NAME -n POD-NAMESPACE-NAME -p

Not sure why you would need the --socket stuff ...