You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our Generator implementation (SimpleTCGenerator) Generates TC filters for all supported protocols
ipv4
ipv6
VLAN ipv4
VLAN ipv6
QinQ ipv4
QinQ ipv6
We should look into how to reduce the number of filters generated for a given Rule.
some thoughts
if bridge is not in QinQ mode, should we generate QinQ related filters ? (need to check bridge behaves in this case) - as we only support accelerated bridge CNI ATM.
should we limit VLAN/QinQ related filters to rules that originate from IPBlock only ?
a more static approach: config knobs which determines the protocols that multi-network-policy-tc will handle (enforce for only what is specified)
The text was updated successfully, but these errors were encountered:
What would you like to be added?
Currently our Generator implementation (SimpleTCGenerator) Generates TC filters for all supported protocols
We should look into how to reduce the number of filters generated for a given Rule.
some thoughts
The text was updated successfully, but these errors were encountered: