You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: