docs: fix filename-access example

[yukinakanaka]

Fixes: #2334

A demo pod called xwing doesn't seem to have vi now. This may be because of the image update: #2311, cilium/cilium#31373.

So, I propose creating a new busybox pod instead of xwing.

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	0f6c97d
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/6624bedf2f47fd0008a60c15
😎 Deploy Preview	https://deploy-preview-2335--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[yukinakanaka]

You can see the preview here: https://deploy-preview-2335--tetragon.netlify.app/docs/use-cases/filename-access/#examples

[mtardy]

Thanks a lot, that works fine, I don't mind not using the star wars deployments for this example! I just added a nit to change file-access-pod to file-access just to avoid the "file-access-pod Pod" stutter!

Another thing is that we could put the tetra getevents after the creation of the pod so that people are not confused with all the events that will appear at the pod creation. We can still put it before if we really want it but we should make a note on what are all those events.

This is mostly nits, and correct things the tutorial was not respecting even before (saying Pod instead of pod), so we can merge this anyway if you don't feel like the fix are worth it!

[yukinakanaka]

Thank you for your kind review! I fixed up my commit by following your suggestion.

• Change the pod name to file-access from file-access-pod.
• Use Pod instead of pod.

Another thing is that we could put the tetra getevents after the creation of the pod so that people are not confused with all the events that will appear at the pod creation.

That's true. I put tetra getevents after the creation of pod.

[mtardy]

Thanks a lot!!