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

Remove telemetry as it has not been upstreamed (#6813) 

* Remove telemetry as it has not been upstreamed

* Add jwt example
This commit is contained in:
mandarjog 2020-03-09 07:19:29 -07:00 committed by GitHub
parent 54e8fc03fc
commit ec20fa3215
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/blog/2020/wasm-announce/index.md
View File

@ -49,8 +49,8 @@ incentivized developers to upstream extensions into Envoy that were used by only
percentage of deployments, just to piggyback on its release mechanisms.
Over time some of the most performance-sensitive features of Istio have been upstreamed
into Envoy - [policy checks on traffic](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/rbac_filter),
and [telemetry reporting](/docs/reference/config/telemetry/metrics/), for example.
into Envoy - [policy checks on traffic](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/rbac_filter), and
[JWT authentication](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/jwt_authn_filter), for example.
Still, we have always wanted to converge on a single stack for extensibility that imposes fewer
tradeoffs: something that decouples Envoy releases from its extension ecosystem, enables
developers to work in their languages of choice, and enables Istio to reliably roll out new