Fix ServiceEntry example in concepts/traffic-management (#11398)

* Fix ServiceEntry example in concepts/traffic-management (#11396)

This change replaces the incorrect mTLS egress example with a simpler,
valid example that adjusts the TCP connection timeout.

Page: Documentation / Concepts / Traffic Management
Section: Service entry example
URL: https://istio.io/latest/docs/concepts/traffic-management/#service-entry-example

* Revert apiVersion change in DestinationRule example

Change back to v1alpha3 to be consistent with rest of page

Co-authored-by: John Howard <howardjohn@google.com>

Co-authored-by: John Howard <howardjohn@google.com>
This commit is contained in:
merusso 2022-06-15 05:34:14 -05:00 committed by GitHub
parent 3ee0ecaa76
commit ac3967eb8d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 7 deletions

View File

@ -557,8 +557,8 @@ fully or use a wildcard prefixed domain name.
You can configure virtual services and destination rules to control traffic to a
service entry in a more granular way, in the same way you configure traffic for
any other service in the mesh. For example, the following destination rule
configures the traffic route to use mutual TLS to secure the connection to the
`ext-svc.example.com` external service that we configured using the service entry:
adjusts the TCP connection timeout for requests to the `ext-svc.example.com`
external service that we configured using the service entry:
{{< text yaml >}}
apiVersion: networking.istio.io/v1alpha3
@ -568,11 +568,9 @@ metadata:
spec:
host: ext-svc.example.com
trafficPolicy:
tls:
mode: MUTUAL
clientCertificate: /etc/certs/myclientcert.pem
privateKey: /etc/certs/client_private_key.pem
caCertificates: /etc/certs/rootcacerts.pem
connectionPool:
tcp:
connectTimeout: 1s
{{< /text >}}
See the