Difference between revisions of "Service mesh"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 18: | Line 18: | ||
== See also == | == See also == | ||
* {{Service mesh}} | * {{Service mesh}} | ||
| + | * {{Kubernetes networking}} | ||
* {{containers}} | * {{containers}} | ||
[[Category:containers]] | [[Category:containers]] | ||
Revision as of 13:08, 23 August 2020
wikipedia:Service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between microservices, often using a sidecar proxy.
- AWS App Mesh (2019)
Related terms
- Traefik (2015)
See also
- Service mesh: Istio, Linkerd, Consul, containerpilot, AWS App Mesh, Kiali, INNOQ, Kuma, Kong Mesh
- Kubernetes networking: network policies, Network Policy Providers, CNI, Calico, flannel, Service mesh, Istio,
kube-proxy, coredns, AWS VPC CNI: vpc-cni, Kubernetes: Ingress controllers, IPVS, ServiceTypes:LoadBalancer, ClusterIP, NodePort, ExternalName, Endpoints, EndpointSlices, Kubernetes DNS,svc.cluster.local, Weave Net - Containers, OCI: Docker (
dockerd),containerd,runc, Podman, buildah, skopeo, lxd, Container Registry, Service mesh, Windows Server containers, Containerpilot, CoreOS, CAdvisor, Containers networking, Container scanning, cosign, CRI, CRI-O,initContainers, Sidecar container, Container images, latest
Advertising:
