Skip to content
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

Fix the design doc #3

Merged
merged 1 commit into from
Aug 20, 2024
Merged

Fix the design doc #3

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
7 changes: 4 additions & 3 deletions docs/design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ flowchart LR
linkStyle 0,1,2 stroke: indianred;

kubelet -- " b-1 create pod " --> natClient
kubelet -- " b-2 send CNI Add " --> cniPlugin
kubelet -- " b-2 send CNI Add/Del " --> cniPlugin
cniPlugin -- " b-3 send RPC call " --> ponad
ponad -- " b-4 get Egress resource " --> egress
ponad -- " b-4 get NAT Client Pod resource " --> pod
Expand All @@ -64,8 +64,9 @@ Users can create a NAT Pod with a Egress Custom Resource.
When a Egress resource is created, the Egress Controller creates a NAT Pod and a ClusterIP Service (`a-1`, `a-2`).

When a user want to send a request with NAT, the user creates a NAT client Pod with an annotation.
Ponad which is deployed as daemonset, watches Pod resources.
When a Pod with the annotation is created, Ponad configures the Pod to be routed to NAT Pod via the ClusterIP Service. (`b-1`, `b-2`, `b-3`, `b-4`).
Ponad which is deployed as daemonset, watches Pod resources.
When a Pod with the annotation is created, Ponad configures the Pod to be routed to NAT Pod via the ClusterIP Service.
When a NAT client Pod is deleted, Pona CNI plugin is received a CNI Del and Ponad removes the configuration and NAT Pod removes the configuration corresponding to the NAT client (`b-1`, `b-2`, `b-3`, `b-4`).

A request from a NAT client Pod is routed to the NAT Pod via the ClusterIP Service, and the NAT Pod performs SNAT and sends the request to the external host.

Expand Down
Loading