Skip to content

docs: adjust point about connection tracking #107

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.

Sign up for GitHub

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

Merged
ctrox merged 1 commit into from
Oct 25, 2025
Merged

docs: adjust point about connection tracking #107

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,10 +46,10 @@ important ones:
[activation sequence](#activation-sequence) for more details.
* All subsequent connections go directly to the application without any
proxying and performance impact.
* An eBPF probe is used to track the last TCP activity on the running
application. This helps zeropod delay checkpointing if there is recent
activity. This avoids too much flapping on a service that is frequently
used.
* The redirector eBPF program is also used to track the last TCP activity
targeting the running application. This helps zeropod delay checkpointing if
there is recent activity. This avoids too much flapping on a service that is
frequently used.
* To the container runtime (e.g. Kubernetes), the container appears to be
running even though the process is technically not. This is required to
prevent the runtime from trying to restart the container.
Expand Down