[07:30:10] <jayme>	 cdanis: source and destination EntityRule's allow for "selector" - which is probably what you want. But if it feels more natural to keep it in a basic network policy, you can also mix those with calico policies
[12:53:37] <cdanis>	 jayme: right so, I have an upstream chart that I don't want to modify so much, so I was considering reusing the templates that it uses to make its own k8s/v1 NetworkPolicy. which of course expand to yaml, not to the calico selector syntax
[12:54:04] <cdanis>	 probably I should just hardcode a selector that makes sense in our deployment though
[12:55:19] <jayme>	 otel and the policy to egress to k8s api?
[12:55:25] <cdanis>	 indeed
[13:00:42] <jayme>	 ah the helper templated render the whole matchLabels construct, I see
[13:01:30] <cdanis>	 yeah
[13:01:44] <jayme>	 but you can probaby still craft something with {{ include "opentelemetry-collector.name" . }}
[13:02:02] <cdanis>	 I asked a different expert last night and it suggested the following: https://i.imgur.com/T7kwpXs.png
[13:02:06] <jayme>	 duplicating opentelemetry-collector.selectorLabels a bit...but might be the easiest
[13:02:07] <cdanis>	 seems a little stinky though
[13:03:24] <jayme>	 urgh...that's the australien weather expert
[13:04:01] <cdanis>	 I'm not sure whether to call it stupidly clever or cleverly stupid, tbh
[13:04:21] <cdanis>	 but yeah I think mimicking opentelemetry-collector.selectorLabels makes the most sense
[13:06:13] <jayme>	 that should be easy enough given it's only filtering on two labels really