istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove old note about Istio 1.1 (#4857) 

In 1.3 documentation I don't think we need a warning about 1.1 anymore
This commit is contained in:
John Howard 2019-08-27 13:30:53 -07:00 committed by Istio Automation
parent fbb6d6a893
commit dc05694f8a
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/en/docs/tasks/traffic-management/egress/egress-control/index.md
View File

@ -61,15 +61,6 @@ service entry defined within the mesh.
without controlling access to external services.
You can then decide to [configure access to external services](#controlled-access-to-external-services) later.
{{< warning >}}
In versions prior to Istio 1.1.4, `ALLOW_ANY` only worked on ports with no HTTP services or
service entries defined within the mesh.
External hosts using the same port as any internal HTTP service
fell back to a blocking-by-default behavior.
Because some ports, such as port 80, have HTTP services inside Istio by default,
prior to Istio 1.1.4 you couldn't call external services on any of those ports either.
{{< /warning >}}
1. To see this approach in action you need to ensure that your Istio installation is configured
with the `global.outboundTrafficPolicy.mode` option set to `ALLOW_ANY`. Unless you explicitly
set it to `REGISTRY_ONLY` mode when you installed Istio, it is probably enabled by default.