Difference between revisions of "Istio"
Tags: Mobile web edit, Mobile edit |
|||
| (59 intermediate revisions by 2 users not shown) | |||
| 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 [[policy]] system. | |
| + | Istio runs in different environments: [[on-premise]], cloud-hosted, [[Kubernetes]] or in virtual machines. | ||
| − | [[ | + | * <code>[[brew install istioctl]]</code> |
| + | == Features == | ||
| + | * [[Traffic management]]: Request routing, Fault Injection, Traffic Shifting, TCP traffic shifting, request timeouts, Circuit Breaking, Mirroring, [[Ingress]], [[Egress]] | ||
| + | * Security | ||
| + | * [[Observability]] | ||
| + | == History == | ||
| + | Istio was started by teams from [[Google]] and [[IBM]] in partnership with the [[Envoy]] team from [[Lyft]]. And it’s been developed fully in the open on [[GitHub]]. | ||
| + | |||
| + | == Architecture == | ||
| + | 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> | ||
| + | |||
| + | == News == | ||
| + | * December 2018, Istio launches as beta on [[GKE]]<ref>https://techcrunch.com/2018/12/11/google-launches-istio-on-gke/</ref> | ||
| + | |||
| + | |||
| + | == [[Istio versions]] == | ||
| + | |||
| + | == Activities == | ||
| + | * Read Istio vs. [[Linkerd]] vs. [[Consul Connect]] https://jpetazzo.github.io/2019/05/17/containers-microservices-service-meshes/ | ||
| + | * [[Install Istio]] https://istio.io/docs/setup/getting-started/#download | ||
| + | * Read Istio related questions on [[Stackoverflow]]: https://stackoverflow.com/questions/tagged/istio?tab=Votes | ||
| + | * Read [[Health Checking of Istio Services]] | ||
| + | |||
| + | == Related terms == | ||
| + | * [[Knative]] and [[Cloud Run]] ([[GCP]]) | ||
| + | * [[Red Hat OpenShift Service Mesh]] | ||
| + | * [[Envoy proxy]] | ||
| + | * [[Traefik]] | ||
| + | * Istio resources: [[Gateway]], [[Sidecar]] | ||
| + | * [[Kiali]] [[Service mesh]] observability and configuration | ||
| + | * [[Amazon EKS Workshop]] | ||
| + | * [[Rancher]] | ||
| + | * <code>[[istio-service-default:]]</code> | ||
== See also == | == See also == | ||
| − | * {{ | + | * {{istioctl}} |
| + | * {{istio.io}} | ||
| + | * {{Istio}} | ||
| + | |||
| + | [[Category:Containers]] | ||
Latest revision as of 11:02, 29 October 2024
wikipedia:Istio (2017-2018) Service mesh provides a way to control how microservices share data with one another. Istio includes APIs 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.
Contents
Features[edit]
- Traffic management: Request routing, Fault Injection, Traffic Shifting, TCP traffic shifting, request timeouts, Circuit Breaking, Mirroring, Ingress, Egress
- Security
- Observability
History[edit]
Istio was started by teams from Google and IBM in partnership with the Envoy team from Lyft. And it’s been developed fully in the open on GitHub.
Architecture[edit]
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.[1] Istio uses an extended version of the Envoy proxy. Envoy is proxy developed in C++[2]
News[edit]
Istio versions[edit]
Activities[edit]
- Read Istio vs. Linkerd vs. Consul Connect https://jpetazzo.github.io/2019/05/17/containers-microservices-service-meshes/
- Install Istio https://istio.io/docs/setup/getting-started/#download
- Read Istio related questions on Stackoverflow: https://stackoverflow.com/questions/tagged/istio?tab=Votes
- Read Health Checking of Istio Services
Related terms[edit]
- Knative and Cloud Run (GCP)
- Red Hat OpenShift Service Mesh
- Envoy proxy
- Traefik
- Istio resources: Gateway, Sidecar
- Kiali Service mesh observability and configuration
- Amazon EKS Workshop
- Rancher
istio-service-default:
See also[edit]
istioctl [ manifest | proxy-config | proxy-status | dashboard | analyze | authz | bug-report | experimental | operator ] istioctl --helpistio.io, sidecar.istio.io, networking.istio.io, traffic.sidecar.istio.io- Istio, istiod, Istio Proxy, Linkerd and Consul Connect, Install Istio,
istioctl, Istio versions,istioctl --help, istio.io, Istio service entry,pilot-agent
Advertising:
