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.

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

When gateway nat is enabled, track the source ip and pod #1358

Closed
oilbeater opened this issue Mar 4, 2022 · 0 comments
Closed

When gateway nat is enabled, track the source ip and pod #1358

oilbeater opened this issue Mar 4, 2022 · 0 comments
Assignees
Labels
feature New network feature monitoring

Comments

@oilbeater
Copy link
Collaborator

Feature request

When gateway enabled nat( distributed/centralized gateway in default vpc and eip/nat-gateway in custom vpc), outside of the cluster can only see the natted ip not the source pod ip. In some scenario user has the requirement to track the source ip or pod. Kube-OVN need to provide a record of the translation.

Use case

Kubernetes users usually deploy database outside the Kubernetes cluster, on the database side can only see the natted ip. When audition or debugging, database admin need to know who visit the database

@oilbeater oilbeater added feature New network feature monitoring labels Mar 4, 2022
lut777 added a commit to lut777/kube-ovn that referenced this issue Apr 13, 2022
lut777 added a commit that referenced this issue Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New network feature monitoring
Projects
None yet
Development

No branches or pull requests

2 participants