Editing Istio
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | [[wikipedia:Istio]] (2017-2018) [[Service mesh]] provides a way to control how [[microservices]] share data with one another. Istio includes [[API]]s that let it integrate into any [[logging]] platform, [[telemetry]] or | + | [[wikipedia:Istio]] (2017-2018) [[Service mesh]] provides a way to control how [[microservices]] share data with one another. Istio includes [[API]]s that let it integrate into any [[logging]] platform, [[telemetry]] or policy system. |
| − | Istio runs in different environments: [[on-premise]], cloud-hosted, [[Kubernetes]] or in virtual machines | + | Istio runs in different environments: [[on-premise]], cloud-hosted, in [[Kubernetes]] or in virtual machines, |
| − | |||
| − | |||
== Features == | == Features == | ||
| Line 14: | Line 12: | ||
== Architecture == | == Architecture == | ||
| − | Istio’s architecture is divided into the | + | Istio’s architecture is divided into the data plane and the control plane. In the data plane, Istio support is added to a service by deploying a [[sidecar proxy]] within your environment. This [[sidecar]] proxy sits alongside a microservice and routes requests to and from other proxies. Together, these proxies form a mesh network that intercepts network communication between microservices. The control plane manages and configures proxies to route traffic. The control plane also configures components to enforce policies and collect telemetry.<ref>https://www.redhat.com/en/topics/microservices/what-is-istio</ref> |
Istio uses an extended version of the [[Envoy]] proxy. Envoy is proxy developed in [[C++]]<ref>https://istio.io/docs/ops/deployment/architecture/</ref> | Istio uses an extended version of the [[Envoy]] proxy. Envoy is proxy developed in [[C++]]<ref>https://istio.io/docs/ops/deployment/architecture/</ref> | ||
| Line 21: | Line 19: | ||
| − | == [[ | + | == Versions == |
| + | * 1.5 (5 March 2020) https://istio.io/news/releases/1.5.x/announcing-1.5/ | ||
| + | ** 1.5.1 | ||
| + | ** 1.5.2 | ||
| + | ** 1.5.3 | ||
| + | ** 1.5.4 | ||
| + | * 1.4 (14 November 2019) https://istio.io/news/releases/1.4.x/announcing-1.4/ | ||
| + | |||
| + | * 1.0 (31 July 2018) https://istio.io/news/releases/1.0.x/announcing-1.0/ | ||
| + | ** [[JWT]] Authentication | ||
| + | |||
| + | |||
| + | * 0.1 (24 May 2017) | ||
== Activities == | == Activities == | ||
| Line 29: | Line 39: | ||
== Related terms == | == Related terms == | ||
| − | * [[Knative]] | + | * [[Knative]] |
* [[Red Hat OpenShift Service Mesh]] | * [[Red Hat OpenShift Service Mesh]] | ||
| + | * <code>[[istioctl]]</code> | ||
* [[Envoy proxy]] | * [[Envoy proxy]] | ||
* [[Traefik]] | * [[Traefik]] | ||
* Istio resources: [[Gateway]], [[Sidecar]] | * Istio resources: [[Gateway]], [[Sidecar]] | ||
| − | |||
| − | |||
| − | |||
== See also == | == See also == | ||
| − | * {{ | + | * {{K8s}} |
| − | |||
| − | |||
* {{Service mesh}} | * {{Service mesh}} | ||
[[Category:Containers]] | [[Category:Containers]] | ||
Advertising:
