mirror of https://github.com/istio/istio.io.git
Remove warning from referenced blogs (#5168)
This commit is contained in:
parent
c8ac8eb91c
commit
3aa2f16d0f
|
@ -7,7 +7,6 @@ attribution: Frank Budinsky
|
||||||
keywords: [traffic-management,canary]
|
keywords: [traffic-management,canary]
|
||||||
aliases:
|
aliases:
|
||||||
- /blog/canary-deployments-using-istio.html
|
- /blog/canary-deployments-using-istio.html
|
||||||
target_release: 0.7
|
|
||||||
---
|
---
|
||||||
|
|
||||||
{{< tip >}}
|
{{< tip >}}
|
||||||
|
|
|
@ -5,7 +5,6 @@ description: Attacks involving egress traffic and requirements for egress traffi
|
||||||
publishdate: 2019-05-22
|
publishdate: 2019-05-22
|
||||||
attribution: Vadim Eisenberg (IBM)
|
attribution: Vadim Eisenberg (IBM)
|
||||||
keywords: [traffic-management,egress,security]
|
keywords: [traffic-management,egress,security]
|
||||||
target_release: 1.1
|
|
||||||
---
|
---
|
||||||
|
|
||||||
This is part 1 in a new series about secure control of egress traffic in Istio that I am going to publish.
|
This is part 1 in a new series about secure control of egress traffic in Istio that I am going to publish.
|
||||||
|
|
|
@ -6,7 +6,6 @@ last_update: 2019-09-05
|
||||||
subtitle:
|
subtitle:
|
||||||
attribution: Megan O'Keefe (Google), John Howard (Google), Mandar Jog (Google)
|
attribution: Megan O'Keefe (Google), John Howard (Google), Mandar Jog (Google)
|
||||||
keywords: [performance,scalability,scale,benchmarks]
|
keywords: [performance,scalability,scale,benchmarks]
|
||||||
target_release: 1.2
|
|
||||||
---
|
---
|
||||||
|
|
||||||
Service meshes add a lot of functionality to application deployments, including [traffic policies](/docs/concepts/what-is-istio/#traffic-management), [observability](/docs/concepts/what-is-istio/#observability), and [secure communication](/docs/concepts/what-is-istio/#security). But adding a service mesh to your environment comes at a cost, whether that's time (added latency) or resources (CPU cycles). To make an informed decision on whether a service mesh is right for your use case, it's important to evaluate how your application performs when deployed with a service mesh.
|
Service meshes add a lot of functionality to application deployments, including [traffic policies](/docs/concepts/what-is-istio/#traffic-management), [observability](/docs/concepts/what-is-istio/#observability), and [secure communication](/docs/concepts/what-is-istio/#security). But adding a service mesh to your environment comes at a cost, whether that's time (added latency) or resources (CPU cycles). To make an informed decision on whether a service mesh is right for your use case, it's important to evaluate how your application performs when deployed with a service mesh.
|
||||||
|
|
|
@ -206,4 +206,4 @@ other = "Description"
|
||||||
other = "Level"
|
other = "Level"
|
||||||
|
|
||||||
[target_release]
|
[target_release]
|
||||||
other = "This blog post was written a while ago and assumed Istio %v. Be aware that there have been many improvements to Isito since then and so some of this content may now be outdated."
|
other = "This blog post was written assuming Istio %v, so some of this content may now be outdated."
|
||||||
|
|
Loading…
Reference in New Issue