docs: tetragon troubleshoot improve

[janvi01]

Improved doc around tetra bugtool, demo how to run it for all different installation k8s, container or systemd host installation.

Fixes #1974 second tick box.

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	dc65465
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/65ddcf86864d26000838e98b
😎 Deploy Preview	https://deploy-preview-2115--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.

[mtardy]

Thanks a lot for taking the time to do that, I have some remarks on the form, I hope it's not too much.

[mtardy]

Thanks a lot, to me it looks good! Could you squash your commits into one with only your first commit message? Thanks :)

[mtardy]

Hey, I saw you added a merge commit. Please use git rebase -i <your_first_branch_commit>^ then drop the merge commit and squash all the commits into the first one. Then you can just resync your main branch and when on your dev branch, just git rebase main.

[janvi01]

Thanks @mtardy quite confused about how to squash commit after the merge commit, it shows various commits to pick(that's probably of others who got in the merge commit)

git rebase -i <your_first_branch_commit>^ i.e. git rebase -i 7bf5737e16b71f62a794144f3ac5b6ec49c9a9ac shows me this, doesn't shows my merge commit

pick 393068fb docs: improve tetra bugtool installations
pick 728f22f2 docs: improve tetra bugtool installations
pick 4361285e docs: merge debugging tetragon tutorial with troubleshooting
pick cd1c898d docs: improve tetra bugtool installations

# Rebase 3b7eda5c..cd1c898d onto 3b7eda5c (4 commands)

[mtardy]

All right I did the fix for you, here are a few things to consider please on the content this time, sorry I didn't do everything at once. Please try to amend the existing commit with your changes or add commits and then squash them.

[janvi01]

@mtardy I did the required changes and amended the commit (apologies quite confused, how did I get others commits here).

[mtardy]

@mtardy I did the required changes and amended the commit (apologies quite confused, how did I get others commits here).

Thanks for taking the time to do the changes!

Sorry this time you'll need to cleanup your PR. Instead of opening a new PR like last time or me tidying up stuff, I think you should take some time to get more familiar with git and git rebase in particular, that will be really useful for you! :)

[janvi01]

@mtardy I squash the commits into a single one, but how to remove others' file changes. Apologies for the inconvenience.

[mtardy]

I'm going to merge that, I forced pushed again removing all the changes from other commits you merged into your initial commit.

While we really appreciate you taking the time to write documentation, please take a bit more time next time testing the commands you put in the documentation. Almost all of them were not working.

• the kubectl get pods -l app.kubernetes.io/name=tetragon label was wrong, with a space instead of the /
• the kubectl exec was missing the -c tetragon option
• the kubectl cp was missing the -c tetragon and the archive name was wrong.
• the docker cp had a wrong archive name.