docs: Tetragon troubleshoot improve #2101
Conversation
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Hey, welcome to Tetragon. Thanks for the taking the time to contribute! Just for you to know I'm sorry but I just touched the troubleshooting guide yesterday in #2097, you might want to rebase your PR on main to make sure everything looks good :) |
mtardy
added
area/documentation
Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
This is a breaking change but this metric is for internal use only so it should not be too bad. Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>
Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>
Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>
It was discussed that this guide was redundant with the getting started guides. It might get reused as an independent blog post. Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>
Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
This section was removed by cilium#2097. Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Improve suid binary example, and rename titles to note privileges escalation. Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@gmail.com>
|
@mtardy I just rebased this PR to main and force-pushed. |
|
It seems there's a bit of confusion about git rebase. When you use git rebase, you're essentially taking the commits from one branch and placing them on top of another branch. For example, let's say you have a feature branch where you've been working on some changes and want to incorporate the latest changes from the main branch into your feature branch. Instead of merging main into your feature branch, you should rebase your feature branch onto main. This means you're taking each commit you've made in your feature branch, saving them aside temporarily, updating your feature branch to match the current state of main, and then applying each of your commits on top of the updated main. This makes your feature branch a linear extension of main, which can often result in a cleaner and more understandable history. Here you imported some commits from main to your branch, it looks more like a merge commit but with every individual commit. I would drop all the commits you imported from the main branch on your branch. Then sync main and do a |
|
I think I should create a new PR, I took the rebase in another way. |
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.