Difference between revisions of "Istio"
(2 intermediate revisions by the same user not shown) | |||
Line 27: | Line 27: | ||
* [[Install Istio]] https://istio.io/docs/setup/getting-started/#download | * [[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 Istio related questions on [[Stackoverflow]]: https://stackoverflow.com/questions/tagged/istio?tab=Votes | ||
+ | * Read [[Health Checking of Istio Services]] | ||
== Related terms == | == Related terms == | ||
Line 37: | Line 38: | ||
* [[Amazon EKS Workshop]] | * [[Amazon EKS Workshop]] | ||
* [[Rancher]] | * [[Rancher]] | ||
+ | * <code>[[istio-service-default:]]</code> | ||
== See also == | == See also == | ||
* {{istioctl}} | * {{istioctl}} | ||
+ | * {{istio.io}} | ||
* {{Istio}} | * {{Istio}} | ||
− | |||
− | |||
[[Category:Containers]] | [[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 --help
istio.io, sidecar.istio.io, networking.istio.io, traffic.sidecar.istio.io
- Istio, Istio Proxy, Linkerd and Consul Connect, Install Istio,
istioctl
, Istio versions,istioctl --help, istio.io
, Istio service entry,pilot-agent
Advertising: