EgressRules are created in specific namespaces, rather than being namespace-less resources, but they currently apply globally. This is confusing to users who believe these rules are scoped to their namespace.
For example, one team creating an EgressRule. Other teams end up, unknowingly, using that egress, but don't notice because things seem to be working. If that first team decides they no longer need that rule, and they delete it, every other team is now unable to communicate to that external system.
Istio version: 0.5.1
EgressRules are created in specific namespaces, rather than being namespace-less resources, but they currently apply globally. This is confusing to users who believe these rules are scoped to their namespace.
For example, one team creating an EgressRule. Other teams end up, unknowingly, using that egress, but don't notice because things seem to be working. If that first team decides they no longer need that rule, and they delete it, every other team is now unable to communicate to that external system.
Istio version: 0.5.1