Matt Bolt

Hey @fcomte Thanks for filing the issue. We are currently only tracking `egress` traffic in the the application currently, but I believe there are plans to eventually support ingress costs....

@SapientGuardian Thanks for the report. Because the network-costs pods do not use any provider specific code, it's not currently an option for the implementation to hook in the ALB IPs,...

> The internal IP addresses for the ALB also exist within these subnets. Those ip addresses get classified as being in-zone when that is the case and cross-zone when they're...

Hey @shaikatz Can I just get you to verify that the configmap has the expected contents? ```bash $ kubectl get cm -n kubecost network-costs-config -o yaml ```

I dropped this config into the network costs, and it does look like the classification component is working correctly. I ran several tests across multiple of the configured region/zones and...

The classification mapping isn't used by the source, the source uses it's host node labels to determine region and zone: ie: ``` apiVersion: v1 kind: Node metadata: annotations: ... labels:...

Yeah, the difference in naming there is definitely what would cause that issue. With respect to the UI, I will need to look into how we're sending the data (it's...

@shaikatz Definitely a frontend UI label bug. We'll get that taken care of ASAP. Thanks for the feedback!

> > The labels are: > > ``` > > failure-domain.beta.kubernetes.io/zone=us-east-1a > > failure-domain.beta.kubernetes.io/region=us-east-1 > > ``` > > > > > > Which follows what written in Kubernetes [docs](https://kubernetes.io/docs/reference/kubernetes-api/labels-annotations-taints/#failure-domainbetakubernetesiozone)...

> Just a note for the discussion. Same zone traffic incurs a cross-zone charge if it traverses a VPC boundary. (actually, 2 charges, in and out) > > Based on...