I want to use exportTo field, which comes in istio 1.1 (https://preliminary.istio.io/docs/reference/config/networking/v1alpha3/destination-rule/) to define DestinationRules.
Currently, it provides “.” - current namespace and “*” - all namespace options.
My questions are:
- What is preventing us to use values other than the above?
- Is anyone already working on this change, if so what is the expected timeline?
As mentioned here this will not be available in 1.1.0, but hopefully will be ready a future 1.1.x release. I’m not sure if anyone has started on the implementation yet.
Thanks a lot David.
Are you aware of any work for restricting Destinationrule definition for a service to be defined only in the namespace the service exists (and not where it is being consumed)
Combining the above with exportTo feature will give service owners complete control over DestinationRules for their services across the mesh.
I’m not aware for DestinationRules but you can use the
Sidecar resource in 1.1.0 to control what ingress and egress services are available for each sidecar proxy. Pre-release docs: https://preliminary.istio.io/docs/reference/config/networking/v1alpha3/sidecar/