Support for Customizing Private Subnet Recognition in Egressd Metrics

[jacob-payu]

Our Kubernetes clusters operate on the 11.0.0.0/16 range, which is technically public but used as a private network (legacy issue). As a result, Egressd identifies all traffic as external, meaning destination labels like dst_namespace and dst_zone are missing from the metrics, and destination ip is always 0.0.0.0

Is there a way to configure Egressd to recognize this range as a private subnet? Alternatively, are there other solutions to address this?