one big pain point is that k8s handle inbound (initiated by entity outside of cluster) and outbound connection (initiated by pod) differently and separately, it

one big pain point is that k8s handle inbound (initiated by entity outside of cluster) and outbound connection (initiated by pod) differently and separately, it is difficult to using same public IP address for inbound dst and outbound source, such symmetric is needed for certain applications. I know there is work around for this case, e.g. only uses a single public IP for both inbound and outbound for whole cluster on aks, or use dedicate node, but these workarounds are just workarounds, all have issues.