Fix doc note since we switched authorization mechanism in 1.9 (#10266)

This commit is contained in:
Paul Banks 2021-05-20 16:28:38 +01:00 committed by GitHub
parent 4e420df7ae
commit 8233328e48
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -497,9 +497,9 @@ definition](/docs/connect/registration/service-registration) or
overridden by the Connect TLS certificates and validation context. This overridden by the Connect TLS certificates and validation context. This
means there is no way to override Connect's mutual TLS for the public means there is no way to override Connect's mutual TLS for the public
listener. listener.
- Every `FilterChain` will have the `envoy.ext_authz` filter prepended to the - Every `FilterChain` will have the `envoy.filters.{network|http}.rbac` filter
filters array to ensure that all inbound connections are authorized by prepended to the filters array to ensure that all inbound connections are
Connect. authorized by Connect. Before Consul 1.9.0 `envoy.ext_authz` was inserted instead.
- `envoy_local_cluster_json` - Specifies a complete [Envoy - `envoy_local_cluster_json` - Specifies a complete [Envoy
cluster](https://www.envoyproxy.io/docs/envoy/v1.10.0/api-v2/api/v2/cds.proto#cluster) cluster](https://www.envoyproxy.io/docs/envoy/v1.10.0/api-v2/api/v2/cds.proto#cluster)
to be delivered in place of the local application cluster. This allows to be delivered in place of the local application cluster. This allows