Is [this](https://repo1.dso.mil/big-bang/product/packages/tempo/-/blob/main/chart/values.yaml?ref_type=heads#L217-218) port exclusion absolutely necessary? I'm wondering if it just needs a postRenderer to add the appProtocol similar to [this guy](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/templates/tempo/_postrenderers.tpl?ref_type=heads#L1-10) so istio will be happy. It looks there is a network policy that is hard coded to [true](https://repo1.dso.mil/big-bang/product/packages/tempo/-/blob/main/chart/values.yaml?ref_type=heads#L54), however, the netpol shouldn't be needed at all. A better fix would be to use the selector value for its inbound route so it generates the proper network and authorization policy. Currently, it now has two network policies when that inbound route is enabled and one has the wrong selector as a result of its current configuration (When the selector is not specified, it defaults to using the name of the route (tempo-query)). If it were named tempo instead of tempo-query, it would have just worked, but I think it may be too late for that option now. Reference: https://repo1.dso.mil/big-bang/product/packages/bb-common/-/blob/main/docs/routes/README.md?ref_type=heads#quick-start