istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
istio.io/archive/v1.3/docs/concepts/deployment-models/index.html

276 lines
86 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!doctype html><html lang=en itemscope itemtype=https://schema.org/WebPage><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge"><meta name=viewport content="width=device-width,initial-scale=1,shrink-to-fit=no"><meta name=theme-color content=#466BB0><meta name=title content="Deployment Models"><meta name=description content="Describes the system models that impact your overall Istio depolyment."><meta name=keywords content=microservices,services,mesh,single-cluster,multiple-clusters,control-plane,tenancy,networks,identity,trust,single-mesh,multiple-meshes><meta property=og:title content="Deployment Models"><meta property=og:type content=website><meta property=og:description content="Describes the system models that impact your overall Istio depolyment."><meta property=og:url content=/v1.3/docs/concepts/deployment-models/><meta property=og:image content=/v1.3/img/istio-whitelogo-bluebackground-framed.svg><meta property=og:image:alt content="Istio Logo"><meta property=og:image:width content=112><meta property=og:image:height content=150><meta property=og:site_name content=Istio><meta name=twitter:card content=summary><meta name=twitter:site content=@IstioMesh><title>Istioldie 1.3 / Deployment Models</title><script async src="https://www.googletagmanager.com/gtag/js?id=UA-98480406-2"></script><script>window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments);}
gtag('js',new Date());gtag('config','UA-98480406-2');</script><link rel=alternate type=application/rss+xml title="Istio Blog" href=/v1.3/blog/feed.xml><link rel=alternate type=application/rss+xml title="Istio News" href=/v1.3/news/feed.xml><link rel=alternate type=application/rss+xml title="Istio Blog and News" href=/v1.3/feed.xml><link rel="shortcut icon" href=/v1.3/favicons/favicon.ico><link rel=apple-touch-icon href=/v1.3/favicons/apple-touch-icon-180x180.png sizes=180x180><link rel=icon type=image/png href=/v1.3/favicons/favicon-16x16.png sizes=16x16><link rel=icon type=image/png href=/v1.3/favicons/favicon-32x32.png sizes=32x32><link rel=icon type=image/png href=/v1.3/favicons/android-36x36.png sizes=36x36><link rel=icon type=image/png href=/v1.3/favicons/android-48x48.png sizes=48x48><link rel=icon type=image/png href=/v1.3/favicons/android-72x72.png sizes=72x72><link rel=icon type=image/png href=/v1.3/favicons/android-96x96.png sizes=96xW96><link rel=icon type=image/png href=/v1.3/favicons/android-144x144.png sizes=144x144><link rel=icon type=image/png href=/v1.3/favicons/android-192x192.png sizes=192x192><link rel=manifest href=/v1.3/manifest.json><meta name=apple-mobile-web-app-title content=Istio><meta name=application-name content=Istio><link rel=stylesheet href="https://fonts.googleapis.com/css?family=Work+Sans:400|Chivo:400|Work+Sans:500,300,600,300italic,400italic,500italic,600italic|Chivo:500,300,600,300italic,400italic,500italic,600italic"><link rel=stylesheet href=/v1.3/css/all.css><script src=/v1.3/js/themes_init.min.js></script></head><body class="language-unknown archive-site"><script>const branchName="release-1.3";const docTitle="Deployment Models";const iconFile="\/v1.3/img/icons.svg";const buttonCopy='Copy to clipboard';const buttonPrint='Print';const buttonDownload='Download';</script><script src="https://www.google.com/cse/brand?form=search-form" defer></script><script src=/v1.3/js/all.min.js data-manual defer></script><header><nav><a id=brand href=/v1.3/><span class=logo><svg viewBox="0 0 300 300"><circle cx="150" cy="150" r="146" stroke-width="2" /><path d="M65 240H225L125 270z"/><path d="M65 230l60-10V110z"/><path d="M135 220l90 10L135 30z"/></svg></span><span class=name>Istioldie 1.3</span></a><div id=hamburger><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#hamburger"/></svg></div><div id=header-links><span title="Learn how to deploy, use, and operate Istio.">Docs</span>
<a title="Posts about using Istio." href=/v1.3/blog/2019/proxy/>Blog</a>
<a title="Timely news about the Istio project." href=/v1.3/news/2019/announcing-1.2-eol/>News</a>
<a title="Frequently Asked Questions about Istio." href=/v1.3/faq/>FAQ</a>
<a title="Get a bit more in-depth info about the Istio project." href=/v1.3/about/>About</a><div class=menu><button id=gearDropdownButton class=menu-trigger title="Options and settings" aria-label="Options and Settings" aria-controls=gearDropdownContent><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#gear"/></svg></button><div id=gearDropdownContent class=menu-content aria-labelledby=gearDropdownButton role=menu><a tabindex=-1 role=menuitem class=active id=light-theme-item>Light Theme</a>
<a tabindex=-1 role=menuitem id=dark-theme-item>Dark Theme</a><div role=separator></div><a tabindex=-1 role=menuitem id=syntax-coloring-item>Color Examples</a><div role=separator></div><h6>Other versions of this site</h6><a tabindex=-1 role=menuitem onclick="navigateToUrlOrRoot('https://istio.io/docs\/concepts\/deployment-models\/');return false;">Current Release</a>
<a tabindex=-1 role=menuitem onclick="navigateToUrlOrRoot('https://preliminary.istio.io/docs\/concepts\/deployment-models\/');return false;">Next Release</a>
<a tabindex=-1 role=menuitem href=https://archive.istio.io>Older Releases</a></div></div><button id=search-show title="Search this site" aria-label=Search><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#magnifier"/></svg></button></div><form id=search-form name=cse role=search><input type=hidden name=cx value=013699703217164175118:iwwf17ikgf4>
<input type=hidden name=ie value=utf-8>
<input type=hidden name=hl value=en>
<input type=hidden id=search-page-url value=/v1.3/search>
<input id=search-textbox class=form-control name=q type=search aria-label="Search this site">
<button id=search-close title="Cancel search" type=reset aria-label="Cancel search"><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#cancel-x"/></svg></button></form></nav></header><main class=primary><div id=sidebar-container class="sidebar-container sidebar-offcanvas"><nav id=sidebar aria-label="Section Navigation"><div class=directory><div class=card><button class="header dynamic" id=card32 title="Learn about the different parts of the Istio system and the abstractions it uses." aria-controls=card32-body><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#concepts"/></svg>Concepts</button><div class="body default" aria-labelledby=card32 role=region id=card32-body><ul role=tree aria-expanded=true class=leaf-section aria-labelledby=card32><li role=none><a role=treeitem title="Introduces Istio, the problems it solves, its high-level architecture and design goals." href=/v1.3/docs/concepts/what-is-istio/>What is Istio?</a></li><li role=none><a role=treeitem title="Describes the various Istio features focused on traffic routing and control." href=/v1.3/docs/concepts/traffic-management/>Traffic Management</a></li><li role=none><a role=treeitem title="Describes Istio's authorization and authentication functionality." href=/v1.3/docs/concepts/security/>Policies and Security</a></li><li role=none><a role=treeitem title="Describes the telemetry and monitoring features provided by Istio." href=/v1.3/docs/concepts/observability/>Observability</a></li><li role=none><a role=treeitem title="Introduces performance and scalability for Istio." href=/v1.3/docs/concepts/performance-and-scalability/>Performance and Scalability</a></li><li role=none><span role=treeitem class=current title="Describes the system models that impact your overall Istio depolyment.">Deployment Models</span></li></ul></div></div><div class=card><button class="header dynamic" id=card49 title="Instructions for installing the Istio control plane on Kubernetes and adding virtual machines into the mesh." aria-controls=card49-body><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#setup"/></svg>Setup</button><div class=body aria-labelledby=card49 role=region id=card49-body><ul role=tree aria-expanded=true aria-labelledby=card49><li role=none><a role=treeitem title="Download, install, and try out Istio." href=/v1.3/docs/setup/getting-started/>Getting Started</a></li><li role=treeitem aria-label="Platform Setup"><button aria-hidden=true></button><a title="How to prepare various Kubernetes platforms before installing Istio." href=/v1.3/docs/setup/platform-setup/>Platform Setup</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Instructions to setup an Alibaba Cloud Kubernetes cluster for Istio." href=/v1.3/docs/setup/platform-setup/alicloud/>Alibaba Cloud</a></li><li role=none><a role=treeitem title="Instructions to setup an Azure cluster for Istio." href=/v1.3/docs/setup/platform-setup/azure/>Azure</a></li><li role=none><a role=treeitem title="Instructions to setup Docker Desktop for Istio." href=/v1.3/docs/setup/platform-setup/docker/>Docker Desktop</a></li><li role=none><a role=treeitem title="Instructions to setup a Google Kubernetes Engine cluster for Istio." href=/v1.3/docs/setup/platform-setup/gke/>Google Kubernetes Engine</a></li><li role=none><a role=treeitem title="Instructions to setup an IBM Cloud cluster for Istio." href=/v1.3/docs/setup/platform-setup/ibm/>IBM Cloud</a></li><li role=none><a role=treeitem title="Instructions to setup a Gardener cluster for Istio." href=/v1.3/docs/setup/platform-setup/gardener/>Kubernetes Gardener</a></li><li role=none><a role=treeitem title="Instructions to setup MicroK8s for use with Istio." href=/v1.3/docs/setup/platform-setup/microk8s/>MicroK8s</a></li><li role=none><a role=treeitem title="Instructions to setup minikube for Istio." href=/v1.3/docs/setup/platform-setup/minikube/>Minikube</a></li><li role=none><a role=treeitem title="Instructions to setup an OpenShift cluster for Istio." href=/v1.3/docs/setup/platform-setup/openshift/>OpenShift</a></li><li role=none><a role=treeitem title="Instructions to setup an OKE cluster for Istio." href=/v1.3/docs/setup/platform-setup/oci/>Oracle Cloud Infrastructure</a></li></ul></li><li role=treeitem aria-label=Install><button aria-hidden=true></button><a title="Choose the guide that best suits your needs and platform." href=/v1.3/docs/setup/install/>Install</a><ul role=group aria-expanded=false><li role=none><a role=treeitem title="Instructions to install Istio in a Kubernetes cluster for evaluation." href=/v1.3/docs/setup/install/kubernetes/>Quick Start Evaluation Install</a></li><li role=none><a role=treeitem title="Install and configure Istio for in-depth evaluation or production use." href=/v1.3/docs/setup/install/helm/>Customizable Install with Helm</a></li><li role=none><a role=treeitem title="Install and configure Istio using the Istio Operator CLI." href=/v1.3/docs/setup/install/operator/>Operator CLI-based Installation [Experimental]</a></li><li role=treeitem aria-label="Multi-cluster Installation"><button aria-hidden=true></button><a title="Configure an Istio mesh spanning multiple Kubernetes clusters." href=/v1.3/docs/setup/install/multicluster/>Multi-cluster Installation</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Install an Istio mesh across multiple Kubernetes clusters with replicated control plane instances." href=/v1.3/docs/setup/install/multicluster/gateways/>Replicated control planes</a></li><li role=none><a role=treeitem title="Install an Istio mesh across multiple Kubernetes clusters with a shared control plane and VPN connectivity between clusters." href=/v1.3/docs/setup/install/multicluster/shared-vpn/>Shared control plane (single-network)</a></li><li role=none><a role=treeitem title="Install an Istio mesh across multiple Kubernetes clusters using a shared control plane for disconnected cluster networks." href=/v1.3/docs/setup/install/multicluster/shared-gateways/>Shared control plane (multi-network)</a></li></ul></li></ul></li><li role=treeitem aria-label=Upgrade><button aria-hidden=true></button><a title="Information on upgrading Istio." href=/v1.3/docs/setup/upgrade/>Upgrade</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Important changes to consider when upgrading to Istio 1.3." href=/v1.3/docs/setup/upgrade/notice/>1.3 Upgrade Notice</a></li><li role=none><a role=treeitem title="Upgrade the Istio control plane and data plane independently." href=/v1.3/docs/setup/upgrade/steps/>Upgrade Steps</a></li></ul></li><li role=treeitem aria-label="More Guides"><button aria-hidden=true></button><a title="More information on additional setup tasks." href=/v1.3/docs/setup/additional-setup/>More Guides</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Prepare your Kubernetes pods and services to run in an Istio-enabled cluster." href=/v1.3/docs/setup/additional-setup/requirements/>Pods and Services</a></li><li role=none><a role=treeitem title="Describes the built-in Istio installation configuration profiles." href=/v1.3/docs/setup/additional-setup/config-profiles/>Installation Configuration Profiles</a></li><li role=none><a role=treeitem title="Install the Istio sidecar in application pods automatically using the sidecar injector webhook or manually using istioctl CLI." href=/v1.3/docs/setup/additional-setup/sidecar-injection/>Installing the Sidecar</a></li><li role=none><a role=treeitem title="Install and use Istio with the Istio CNI plugin, allowing operators to deploy services with lower privilege." href=/v1.3/docs/setup/additional-setup/cni/>Install Istio with the Istio CNI plugin</a></li></ul></li></ul></div></div><div class=card><button class="header dynamic" id=card72 title="How to do single specific targeted activities with the Istio system." aria-controls=card72-body><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#tasks"/></svg>Tasks</button><div class=body aria-labelledby=card72 role=region id=card72-body><ul role=tree aria-expanded=true aria-labelledby=card72><li role=treeitem aria-label="Traffic Management"><button aria-hidden=true></button><a title="Tasks that demonstrate Istio's traffic routing features." href=/v1.3/docs/tasks/traffic-management/>Traffic Management</a><ul role=group aria-expanded=false><li role=none><a role=treeitem title="This task shows you how to configure dynamic request routing to multiple versions of a microservice." href=/v1.3/docs/tasks/traffic-management/request-routing/>Request Routing</a></li><li role=none><a role=treeitem title="This task shows you how to inject faults to test the resiliency of your application." href=/v1.3/docs/tasks/traffic-management/fault-injection/>Fault Injection</a></li><li role=none><a role=treeitem title="Shows you how to migrate traffic from an old to new version of a service." href=/v1.3/docs/tasks/traffic-management/traffic-shifting/>Traffic Shifting</a></li><li role=none><a role=treeitem title="Shows you how to migrate TCP traffic from an old to new version of a TCP service." href=/v1.3/docs/tasks/traffic-management/tcp-traffic-shifting/>TCP Traffic Shifting</a></li><li role=none><a role=treeitem title="This task shows you how to setup request timeouts in Envoy using Istio." href=/v1.3/docs/tasks/traffic-management/request-timeouts/>Request Timeouts</a></li><li role=none><a role=treeitem title="This task shows you how to configure circuit breaking for connections, requests, and outlier detection." href=/v1.3/docs/tasks/traffic-management/circuit-breaking/>Circuit Breaking</a></li><li role=none><a role=treeitem title="This task demonstrates the traffic mirroring/shadowing capabilities of Istio." href=/v1.3/docs/tasks/traffic-management/mirroring/>Mirroring</a></li><li role=treeitem aria-label=Ingress><button aria-hidden=true></button><a title="Controlling ingress traffic for an Istio service mesh." href=/v1.3/docs/tasks/traffic-management/ingress/>Ingress</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Describes how to configure an Istio gateway to expose a service outside of the service mesh." href=/v1.3/docs/tasks/traffic-management/ingress/ingress-control/>Ingress Gateways</a></li><li role=none><a role=treeitem title="Expose a service outside of the service mesh over TLS or mTLS using file-mounted certificates." href=/v1.3/docs/tasks/traffic-management/ingress/secure-ingress-mount/>Secure Gateways (File Mount)</a></li><li role=none><a role=treeitem title="Expose a service outside of the service mesh over TLS or mTLS using the secret discovery service (SDS)." href=/v1.3/docs/tasks/traffic-management/ingress/secure-ingress-sds/>Secure Gateways (SDS)</a></li><li role=none><a role=treeitem title="Describes how to configure SNI passthrough for an ingress gateway." href=/v1.3/docs/tasks/traffic-management/ingress/ingress-sni-passthrough/>Ingress Gateway without TLS Termination</a></li><li role=none><a role=treeitem title="Demonstrates how to obtain Let's Encrypt TLS certificates for Kubernetes Ingress automatically using Cert-Manager." href=/v1.3/docs/tasks/traffic-management/ingress/ingress-certmgr/>Kubernetes Ingress with Cert-Manager</a></li></ul></li><li role=treeitem aria-label=Egress><button aria-hidden=true></button><a title="Controlling egress traffic for an Istio service mesh." href=/v1.3/docs/tasks/traffic-management/egress/>Egress</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Describes how to configure Istio to route traffic from services in the mesh to external services." href=/v1.3/docs/tasks/traffic-management/egress/egress-control/>Accessing External Services</a></li><li role=none><a role=treeitem title="Describes how to configure Istio to perform TLS origination for traffic to external services." href=/v1.3/docs/tasks/traffic-management/egress/egress-tls-origination/>Egress TLS Origination</a></li><li role=none><a role=treeitem title="Describes how to configure Istio to direct traffic to external services through a dedicated gateway." href=/v1.3/docs/tasks/traffic-management/egress/egress-gateway/>Egress Gateways</a></li><li role=none><a role=treeitem title="Describes how to configure an Egress Gateway to perform TLS origination to external services." href=/v1.3/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/>Egress Gateways with TLS Origination</a></li><li role=none><a role=treeitem title="Describes how to enable egress traffic for a set of hosts in a common domain, instead of configuring each and every host separately." href=/v1.3/docs/tasks/traffic-management/egress/wildcard-egress-hosts/>Egress using Wildcard Hosts</a></li><li role=none><a role=treeitem title="Describes how to configure SNI monitoring and apply policies on TLS egress traffic." href=/v1.3/docs/tasks/traffic-management/egress/egress_sni_monitoring_and_policies/>Monitoring and Policies for TLS Egress</a></li><li role=none><a role=treeitem title="Describes how to configure Istio to let applications use an external HTTPS proxy." href=/v1.3/docs/tasks/traffic-management/egress/http-proxy/>Using an External HTTPS Proxy</a></li></ul></li></ul></li><li role=treeitem aria-label=Security><button aria-hidden=true></button><a title="Demonstrates how to secure the mesh." href=/v1.3/docs/tasks/security/>Security</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Shows you how to use Istio authentication policy to setup mutual TLS and basic end-user authentication." href=/v1.3/docs/tasks/security/authn-policy/>Authentication Policy</a></li><li role=none><a role=treeitem title="Shows how to set up role-based access control for HTTP services." href=/v1.3/docs/tasks/security/authz-http/>Authorization for HTTP Services</a></li><li role=none><a role=treeitem title="Shows how to set up role-based access control for TCP services." href=/v1.3/docs/tasks/security/authz-tcp/>Authorization for TCP Services</a></li><li role=none><a role=treeitem title="Tutorial on how to configure the groups-base authorization and configure the authorization of list-typed claims in Istio." href=/v1.3/docs/tasks/security/rbac-groups/>Authorization for groups and list claims</a></li><li role=none><a role=treeitem title="Shows how to use Authorization permissive mode." href=/v1.3/docs/tasks/security/authz-permissive/>Authorization permissive mode</a></li><li role=none><a role=treeitem title="Shows you how to verify and test Istio's automatic mutual TLS authentication." href=/v1.3/docs/tasks/security/mutual-tls/>Mutual TLS Deep-Dive</a></li><li role=none><a role=treeitem title="Shows how operators can configure Citadel with existing root certificate, signing certificate and key." href=/v1.3/docs/tasks/security/plugin-ca-cert/>Plugging in External CA Key and Certificate</a></li><li role=none><a role=treeitem title="Shows how to enable Citadel health checking with Kubernetes." href=/v1.3/docs/tasks/security/health-check/>Citadel Health Checking</a></li><li role=none><a role=treeitem title="Shows how to enable SDS (secret discovery service) for Istio identity provisioning." href=/v1.3/docs/tasks/security/auth-sds/>Provisioning Identity through SDS</a></li><li role=none><a role=treeitem title="Configure which namespaces Citadel should generate service account secrets for." href=/v1.3/docs/tasks/security/ca-namespace-targeting/>Configure Citadel Service Account Secret Generation</a></li><li role=none><a role=treeitem title="Shows you how to incrementally migrate your Istio services to mutual TLS." href=/v1.3/docs/tasks/security/mtls-migration/>Mutual TLS Migration</a></li><li role=none><a role=treeitem title="Shows how to enable mutual TLS on HTTPS services." href=/v1.3/docs/tasks/security/https-overlay/>Mutual TLS over HTTPS</a></li></ul></li><li role=treeitem aria-label=Policies><button aria-hidden=true></button><a title="Demonstrates policy enforcement features." href=/v1.3/docs/tasks/policy-enforcement/>Policies</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="This task shows you how to enable Istio policy enforcement." href=/v1.3/docs/tasks/policy-enforcement/enabling-policy/>Enabling Policy Enforcement</a></li><li role=none><a role=treeitem title="This task shows you how to use Istio to dynamically limit the traffic to a service." href=/v1.3/docs/tasks/policy-enforcement/rate-limiting/>Enabling Rate Limits</a></li><li role=none><a role=treeitem title="Shows how to modify request headers and routing using policy adapters." href=/v1.3/docs/tasks/policy-enforcement/control-headers/>Control Headers and Routing</a></li><li role=none><a role=treeitem title="Shows how to control access to a service using simple denials or white/black listing." href=/v1.3/docs/tasks/policy-enforcement/denial-and-list/>Denials and White/Black Listing</a></li></ul></li><li role=treeitem aria-label=Telemetry><button aria-hidden=true></button><a title="Demonstrates how to collect telemetry information from the mesh." href=/v1.3/docs/tasks/telemetry/>Telemetry</a><ul role=group aria-expanded=false><li role=treeitem aria-label=Metrics><button aria-hidden=true></button><a title="Demonstrates the configuration, collection, and processing of Istio mesh metrics." href=/v1.3/docs/tasks/telemetry/metrics/>Metrics</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="This task shows you how to configure Istio to collect and customize metrics." href=/v1.3/docs/tasks/telemetry/metrics/collecting-metrics/>Collecting Metrics</a></li><li role=none><a role=treeitem title="This task shows you how to configure Istio to collect metrics for TCP services." href=/v1.3/docs/tasks/telemetry/metrics/tcp-metrics/>Collecting Metrics for TCP services</a></li><li role=none><a role=treeitem title="This task shows you how to query for Istio Metrics using Prometheus." href=/v1.3/docs/tasks/telemetry/metrics/querying-metrics/>Querying Metrics from Prometheus</a></li><li role=none><a role=treeitem title="This task shows you how to setup and use the Istio Dashboard to monitor mesh traffic." href=/v1.3/docs/tasks/telemetry/metrics/using-istio-dashboard/>Visualizing Metrics with Grafana</a></li></ul></li><li role=treeitem aria-label=Logs><button aria-hidden=true></button><a title="Demonstrates the configuration, collection, and processing of Istio mesh logs." href=/v1.3/docs/tasks/telemetry/logs/>Logs</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="This task shows you how to configure Istio to collect and customize logs." href=/v1.3/docs/tasks/telemetry/logs/collecting-logs/>Collecting Logs</a></li><li role=none><a role=treeitem title="This task shows you how to configure Envoy proxies to print access log to their standard output." href=/v1.3/docs/tasks/telemetry/logs/access-log/>Getting Envoy&#39;s Access Logs</a></li><li role=none><a role=treeitem title="This task shows you how to configure Istio to log to a Fluentd daemon." href=/v1.3/docs/tasks/telemetry/logs/fluentd/>Logging with Fluentd</a></li></ul></li><li role=treeitem aria-label="Distributed Tracing"><button aria-hidden=true></button><a title="This task shows you how to configure Istio-enabled applications to collect trace spans." href=/v1.3/docs/tasks/telemetry/distributed-tracing/>Distributed Tracing</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Overview of distributed tracing in Istio." href=/v1.3/docs/tasks/telemetry/distributed-tracing/overview/>Overview</a></li><li role=none><a role=treeitem title="Learn how to configure the proxies to send tracing requests to Jaeger." href=/v1.3/docs/tasks/telemetry/distributed-tracing/jaeger/>Jaeger</a></li><li role=none><a role=treeitem title="Learn how to configure the proxies to send tracing requests to Zipkin." href=/v1.3/docs/tasks/telemetry/distributed-tracing/zipkin/>Zipkin</a></li><li role=none><a role=treeitem title="How to configure the proxies to send tracing requests to LightStep." href=/v1.3/docs/tasks/telemetry/distributed-tracing/lightstep/>LightStep</a></li></ul></li><li role=none><a role=treeitem title="This task shows you how to visualize your services within an Istio mesh." href=/v1.3/docs/tasks/telemetry/kiali/>Visualizing Your Mesh</a></li><li role=none><a role=treeitem title="This task shows you how to configure external access to the set of Istio telemetry addons." href=/v1.3/docs/tasks/telemetry/gateways/>Remotely Accessing Telemetry Addons</a></li></ul></li></ul></div></div><div class=card><button class="header dynamic" id=card90 title="A variety of fully working example uses for Istio that you can experiment with." aria-controls=card90-body><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#examples"/></svg>Examples</button><div class=body aria-labelledby=card90 role=region id=card90-body><ul role=tree aria-expanded=true aria-labelledby=card90><li role=none><a role=treeitem title="Deploys a sample application composed of four separate microservices used to demonstrate various Istio features." href=/v1.3/docs/examples/bookinfo/>Bookinfo Application</a></li><li role=none><a role=treeitem title="Explains how to manually integrate Google Cloud Endpoints services with Istio." href=/v1.3/docs/examples/endpoints/>Install Istio for Google Cloud Endpoints Services</a></li><li role=treeitem aria-label="Mesh Expansion"><button aria-hidden=true></button><a title="Configure an Istio mesh spanning Kubernetes clusters, VMs and bare metals." href=/v1.3/docs/examples/mesh-expansion/>Mesh Expansion</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Integrate VMs and bare metal hosts into an Istio mesh deployed on Kubernetes." href=/v1.3/docs/examples/mesh-expansion/single-network/>Single-network Mesh Expansion</a></li><li role=none><a role=treeitem title="Integrate VMs and bare metal hosts into an Istio mesh deployed on Kubernetes with gateways." href=/v1.3/docs/examples/mesh-expansion/multi-network/>Multi-network Mesh Expansion</a></li><li role=none><a role=treeitem title="Illustrates how to expand the Bookinfo application's mesh with a raw VM service." href=/v1.3/docs/examples/mesh-expansion/bookinfo-expanded/>Bookinfo with Mesh Expansion</a></li></ul></li><li role=treeitem aria-label="Multicluster Service Mesh"><button aria-hidden=true></button><a title="Multicluster service mesh examples for Istio that you can experiment with." href=/v1.3/docs/examples/multicluster/>Multicluster Service Mesh</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Set up a multicluster mesh over two GKE clusters." href=/v1.3/docs/examples/multicluster/gke/>Google Kubernetes Engine</a></li><li role=none><a role=treeitem title="Example multicluster mesh over two IBM Cloud Private clusters." href=/v1.3/docs/examples/multicluster/icp/>IBM Cloud Private</a></li></ul></li></ul></div></div><div class=card><button class="header dynamic" id=card104 title="Hints, tips, tricks about running an Istio mesh." aria-controls=card104-body><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#guide"/></svg>Operations</button><div class=body aria-labelledby=card104 role=region id=card104-body><ul role=tree aria-expanded=true aria-labelledby=card104><li role=none><a role=treeitem title="Shows how to do health checking for Istio services." href=/v1.3/docs/ops/app-health-check/>Health Checking of Istio Services</a></li><li role=treeitem aria-label="Installation and Configuration"><button aria-hidden=true></button><a title="Describes important requirements, concepts, and considerations for installing and configuring Istio." href=/v1.3/docs/ops/setup/>Installation and Configuration</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Describes Istio's use of Kubernetes webhooks for automatic sidecar injection." href=/v1.3/docs/ops/setup/injection-concepts/>Automatic Sidecar Injection</a></li><li role=none><a role=treeitem title="Describes how to check which capabilities are allowed for your pods." href=/v1.3/docs/ops/setup/required-pod-capabilities/>Required Pod Capabilities</a></li><li role=none><a role=treeitem title="Provides a general overview of Istio's use of Kubernetes webhooks and the related issues that can arise." href=/v1.3/docs/ops/setup/webhook/>Dynamic Admission Webhooks Overview</a></li><li role=none><a role=treeitem title="Describes Istio's use of Kubernetes webhooks for server-side configuration validation." href=/v1.3/docs/ops/setup/validation/>Configuration Validation Webhook</a></li></ul></li><li role=treeitem aria-label="Traffic Management"><button aria-hidden=true></button><a title="Helps you manage the networking aspects of a running mesh." href=/v1.3/docs/ops/traffic-management/>Traffic Management</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="An introduction to Istio networking operational aspects." href=/v1.3/docs/ops/traffic-management/introduction/>Introduction to Network Operations</a></li><li role=none><a role=treeitem title="Provides specific deployment or configuration guidelines to avoid networking or traffic management issues." href=/v1.3/docs/ops/traffic-management/deploy-guidelines/>Avoiding Traffic Management Issues</a></li><li role=none><a role=treeitem title="Information on how to enable and understand Locality Load Balancing." href=/v1.3/docs/ops/traffic-management/locality-load-balancing/>Locality Load Balancing</a></li><li role=none><a role=treeitem title="Information on how to specify protocols." href=/v1.3/docs/ops/traffic-management/protocol-selection/>Protocol Selection</a></li></ul></li><li role=treeitem aria-label=Security><button aria-hidden=true></button><a title="Helps you manage the security aspects of a running mesh." href=/v1.3/docs/ops/security/>Security</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Use hardened container images to reduce Istio's attack surface." href=/v1.3/docs/ops/security/harden-docker-images/>Harden Docker Container Images</a></li><li role=none><a role=treeitem title="Learn how to extend the lifetime of the Istio self-signed root certificate." href=/v1.3/docs/ops/security/root-transition/>Extending Self-Signed Certificate Lifetime</a></li></ul></li><li role=treeitem aria-label=Telemetry><button aria-hidden=true></button><a title="Helps you manage telemetry collection and visualization in a running mesh." href=/v1.3/docs/ops/telemetry/>Telemetry</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="How to enable in-proxy generation of HTTP service-level metrics." href=/v1.3/docs/ops/telemetry/in-proxy-service-telemetry/>Generate Istio Metrics Without Mixer [Experimental]</a></li><li role=none><a role=treeitem title="Fine-grained control of Envoy statistics." href=/v1.3/docs/ops/telemetry/envoy-stats/>Envoy Statistics</a></li></ul></li><li role=treeitem aria-label=Troubleshooting><button aria-hidden=true></button><a title="Describes how to identify and resolve common problems in Istio." href=/v1.3/docs/ops/troubleshooting/>Troubleshooting</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Istio includes a supplemental tool that provides debugging and diagnosis for Istio service mesh deployments." href=/v1.3/docs/ops/troubleshooting/istioctl/>Using the istioctl command-line tool</a></li><li role=none><a role=treeitem title="Tools and techniques to address common Istio traffic management and network problems." href=/v1.3/docs/ops/troubleshooting/network-issues/>Network Problems</a></li><li role=none><a role=treeitem title="Tools and techniques to address common Istio authentication, authorization, and general security-related problems." href=/v1.3/docs/ops/troubleshooting/security-issues/>Security Problems</a></li><li role=none><a role=treeitem title="Resolve common problems with Istio's use of Kubernetes webhooks for automatic sidecar injection." href=/v1.3/docs/ops/troubleshooting/injection/>Sidecar Injection Problems</a></li><li role=none><a role=treeitem title="What to do if Citadel is not behaving properly." href=/v1.3/docs/ops/troubleshooting/repairing-citadel/>Repairing Citadel</a></li><li role=none><a role=treeitem title="Describes tools and techniques to diagnose Envoy configuration issues related to traffic management." href=/v1.3/docs/ops/troubleshooting/proxy-cmd/>Debugging Envoy and Pilot</a></li><li role=none><a role=treeitem title="Describes how to resolve Galley configuration problems." href=/v1.3/docs/ops/troubleshooting/validation/>Galley Configuration Problems</a></li><li role=none><a role=treeitem title="Diagnose problems where metrics are not being collected." href=/v1.3/docs/ops/troubleshooting/missing-metrics/>Missing Metrics</a></li><li role=none><a role=treeitem title="Dealing with Grafana issues." href=/v1.3/docs/ops/troubleshooting/grafana/>Missing Grafana Output</a></li><li role=none><a role=treeitem title="Fix missing traces in Zipkin." href=/v1.3/docs/ops/troubleshooting/missing-traces/>Missing Zipkin Traces</a></li><li role=none><a role=treeitem title="Shows you how to use istioctl describe to verify the configurations of a pod in your mesh." href=/v1.3/docs/ops/troubleshooting/istioctl-describe/>Understand your Mesh with istioctl describe</a></li><li role=none><a role=treeitem title="Describes how to use component-level logging to get insights into a running component's behavior." href=/v1.3/docs/ops/troubleshooting/component-logging/>Component Logging</a></li><li role=none><a role=treeitem title="Describes how to use ControlZ to get insight into individual running components." href=/v1.3/docs/ops/troubleshooting/controlz/>Component Introspection</a></li><li role=none><a role=treeitem title="Limitations for using Tcpdump in pods." href=/v1.3/docs/ops/troubleshooting/tcpdump-notes/>Tcpdump Limitations</a></li></ul></li></ul></div></div><div class=card><button class="header dynamic" id=card126 title="Detailed authoritative reference material such as command-line options, configuration options, and API calling parameters." aria-controls=card126-body><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#reference"/></svg>Reference</button><div class=body aria-labelledby=card126 role=region id=card126-body><ul role=tree aria-expanded=true aria-labelledby=card126><li role=treeitem aria-label=Configuration><button aria-hidden=true></button><a title="Detailed information on configuration options." href=/v1.3/docs/reference/config/>Configuration</a><ul role=group aria-expanded=false><li role=treeitem aria-label="Traffic Management"><button aria-hidden=true></button><a title="Describes how to configure HTTP/TCP routing features." href=/v1.3/docs/reference/config/networking/>Traffic Management</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Configuration affecting load balancing, outlier detection, etc." href=/v1.3/docs/reference/config/networking/v1alpha3/destination-rule/>Destination Rule</a></li><li role=none><a role=treeitem title="Customizing Envoy configuration generated by Istio." href=/v1.3/docs/reference/config/networking/v1alpha3/envoy-filter/>Envoy Filter</a></li><li role=none><a role=treeitem title="Configuration affecting edge load balancer." href=/v1.3/docs/reference/config/networking/v1alpha3/gateway/>Gateway</a></li><li role=none><a role=treeitem title="Configuration affecting service registry." href=/v1.3/docs/reference/config/networking/v1alpha3/service-entry/>Service Entry</a></li><li role=none><a role=treeitem title="Configuration affecting network reachability of a sidecar." href=/v1.3/docs/reference/config/networking/v1alpha3/sidecar/>Sidecar</a></li><li role=none><a role=treeitem title="Configuration affecting label/content routing, sni routing, etc." href=/v1.3/docs/reference/config/networking/v1alpha3/virtual-service/>Virtual Service</a></li></ul></li><li role=none><a role=treeitem title="Authentication policy for Istio services." href=/v1.3/docs/reference/config/istio.authentication.v1alpha1/>Authentication Policy</a></li><li role=none><a role=treeitem title="Resource annotations used by Istio." href=/v1.3/docs/reference/config/annotations/>Resource Annotations</a></li><li role=treeitem aria-label=Authorization><button aria-hidden=true></button><a title="Describes how to configure Istio's authorization features." href=/v1.3/docs/reference/config/authorization/>Authorization</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Describes the supported constraints and properties." href=/v1.3/docs/reference/config/authorization/constraints-and-properties/>Constraints and Properties</a></li><li role=none><a role=treeitem title="Configuration for Role Based Access Control." href=/v1.3/docs/reference/config/authorization/istio.rbac.v1alpha1/>RBAC</a></li></ul></li><li role=none><a role=treeitem title="Describes the options available when installing Istio using the included Helm chart." href=/v1.3/docs/reference/config/installation-options/>Installation Options</a></li><li role=none><a role=treeitem title="Details the Helm chart installation options differences between release-1.2 and release-1.3." href=/v1.3/docs/reference/config/installation-options-changes/>Installation Options Changes</a></li><li role=treeitem aria-label="Policies and Telemetry"><button aria-hidden=true></button><a title="Describes how to configure Istio's policy and telemetry features." href=/v1.3/docs/reference/config/policy-and-telemetry/>Policies and Telemetry</a><ul role=group aria-expanded=false><li role=none><a role=treeitem title="Describes the configuration model for Istio's policy enforcement and telemetry mechanisms." href=/v1.3/docs/reference/config/policy-and-telemetry/mixer-overview/>Mixer Configuration Model</a></li><li role=none><a role=treeitem title="Describes the base attribute vocabulary used for policy and control." href=/v1.3/docs/reference/config/policy-and-telemetry/attribute-vocabulary/>Attribute Vocabulary</a></li><li role=none><a role=treeitem title="Mixer configuration expression language reference." href=/v1.3/docs/reference/config/policy-and-telemetry/expression-language/>Expression Language</a></li><li role=treeitem aria-label=Adapters><button aria-hidden=true></button><a title="Mixer adapters allow Istio to interface to a variety of infrastructure backends for such things as metrics and logs." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/>Adapters</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Adapter to deliver metrics to Apache SkyWalking." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/apache-skywalking/>Apache SkyWalking</a></li><li role=none><a role=treeitem title="Adapter for Apigee's distributed policy checks and analytics." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/apigee/>Apigee</a></li><li role=none><a role=treeitem title="Adapter to enforce authentication and authorization policies for web apps and APIs." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/app-identity-access-adapter/>App Identity and Access</a></li><li role=none><a role=treeitem title="Adapter for circonus.com's monitoring solution." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/circonus/>Circonus</a></li><li role=none><a role=treeitem title="Adapter for cloudmonitor metrics." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/cloudmonitor/>CloudMonitor</a></li><li role=none><a role=treeitem title="Adapter for cloudwatch metrics." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/cloudwatch/>CloudWatch</a></li><li role=none><a role=treeitem title="Adapter to deliver metrics to a dogstatsd agent for delivery to DataDog." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/datadog/>Datadog</a></li><li role=none><a role=treeitem title="Adapter that always returns a precondition denial." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/denier/>Denier</a></li><li role=none><a role=treeitem title="Adapter that delivers logs to a Fluentd daemon." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/fluentd/>Fluentd</a></li><li role=none><a role=treeitem title="Adapter that extracts information from a Kubernetes environment." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/kubernetesenv/>Kubernetes Env</a></li><li role=none><a role=treeitem title="Adapter that performs whitelist or blacklist checks." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/list/>List</a></li><li role=none><a role=treeitem title="Adapter for a simple in-memory quota management system." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/memquota/>Memory quota</a></li><li role=none><a role=treeitem title="Adapter that implements an Open Policy Agent engine." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/opa/>OPA</a></li><li role=none><a role=treeitem title="Adapter that exposes Istio metrics for ingestion by a Prometheus harvester." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/prometheus/>Prometheus</a></li><li role=none><a role=treeitem title="Adapter for a Redis-based quota management system." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/redisquota/>Redis Quota</a></li><li role=none><a role=treeitem title="Adapter that sends metrics to SignalFx." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/signalfx/>SignalFx</a></li><li role=none><a role=treeitem title="Adapter to deliver logs and metrics to Papertrail and AppOptics backends." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/solarwinds/>SolarWinds</a></li><li role=none><a role=treeitem title="Adapter to deliver logs, metrics, and traces to Stackdriver." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/stackdriver/>Stackdriver</a></li><li role=none><a role=treeitem title="Adapter to deliver metrics to a StatsD backend." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/statsd/>StatsD</a></li><li role=none><a role=treeitem title="Adapter to locally output logs and metrics." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/stdio/>Stdio</a></li><li role=none><a role=treeitem title="Adapter to deliver metrics to Wavefront by VMware." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/wavefront/>Wavefront by VMware</a></li><li role=none><a role=treeitem title="Adapter to deliver tracing data to Zipkin." href=/v1.3/docs/reference/config/policy-and-telemetry/adapters/zipkin/>Zipkin</a></li></ul></li><li role=none><a role=treeitem title="Default Metrics exported from Istio through Mixer." href=/v1.3/docs/reference/config/policy-and-telemetry/metrics/>Default Metrics</a></li><li role=treeitem aria-label=Templates><button aria-hidden=true></button><a title="Mixer templates are used to send data to individual adapters." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/>Templates</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="A template that represents a single API key." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/apikey/>API Key</a></li><li role=none><a role=treeitem title="The Analytics template is used to dispatch runtime telemetry to Apigee." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/analytics/>Analytics</a></li><li role=none><a role=treeitem title="A template used to represent an access control query." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/authorization/>Authorization</a></li><li role=none><a role=treeitem title="A template that carries no data, useful for testing." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/checknothing/>Check Nothing</a></li><li role=none><a role=treeitem title="A template designed to report observed communication edges between workloads." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/edge/>Edge</a></li><li role=none><a role=treeitem title="A template that is used to control the production of Kubernetes-specific attributes." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/kubernetes/>Kubernetes</a></li><li role=none><a role=treeitem title="A template designed to let you perform list checking operations." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/listentry/>List Entry</a></li><li role=none><a role=treeitem title="A template that represents a single runtime log entry." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/logentry/>Log Entry</a></li><li role=none><a role=treeitem title="A template that represents a single runtime metric." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/metric/>Metric</a></li><li role=none><a role=treeitem title="A template that represents a quota allocation request." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/quota/>Quota</a></li><li role=none><a role=treeitem title="A template that carries no data, useful for testing." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/reportnothing/>Report Nothing</a></li><li role=none><a role=treeitem title="A template that represents an individual span within a distributed trace." href=/v1.3/docs/reference/config/policy-and-telemetry/templates/tracespan/>Trace Span</a></li></ul></li><li role=none><a role=treeitem title="Configuration state for the Mixer client library." href=/v1.3/docs/reference/config/policy-and-telemetry/istio.mixer.v1.config.client/>Mixer Client</a></li><li role=none><a role=treeitem title="Describes the rules used to configure Mixer's policy and telemetry features." href=/v1.3/docs/reference/config/policy-and-telemetry/istio.policy.v1beta1/>Rules</a></li></ul></li><li role=none><a role=treeitem title="Configuration for Istio control plane installation through the Operator." href=/v1.3/docs/reference/config/istio.operator.v1alpha12.pb/>Operator Installation</a></li><li role=none><a role=treeitem title="Configuration affecting the service mesh as a whole." href=/v1.3/docs/reference/config/istio.mesh.v1alpha1/>Service Mesh</a></li></ul></li><li role=treeitem aria-label=Commands><button aria-hidden=true></button><a title="Describes usage and options of the Istio commands and utilities." href=/v1.3/docs/reference/commands/>Commands</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Galley provides configuration management services for Istio." href=/v1.3/docs/reference/commands/galley/>galley</a></li><li role=none><a role=treeitem title="Istio Certificate Authority (CA)." href=/v1.3/docs/reference/commands/istio_ca/>istio_ca</a></li><li role=none><a role=treeitem title="Istio control interface." href=/v1.3/docs/reference/commands/istioctl/>istioctl</a></li><li role=none><a role=treeitem title="Mixer is Istio's abstraction on top of infrastructure backends." href=/v1.3/docs/reference/commands/mixs/>mixs</a></li><li role=none><a role=treeitem title="Istio security per-node agent." href=/v1.3/docs/reference/commands/node_agent/>node_agent</a></li><li role=none><a role=treeitem title="The Istio operator." href=/v1.3/docs/reference/commands/operator/>operator</a></li><li role=none><a role=treeitem title="Istio Pilot agent." href=/v1.3/docs/reference/commands/pilot-agent/>pilot-agent</a></li><li role=none><a role=treeitem title="Istio Pilot." href=/v1.3/docs/reference/commands/pilot-discovery/>pilot-discovery</a></li><li role=none><a role=treeitem title="Kubernetes webhook for automatic Istio sidecar injection." href=/v1.3/docs/reference/commands/sidecar-injector/>sidecar-injector</a></li></ul></li><li role=none><a role=treeitem title="A glossary of common Istio terms." href=/v1.3/docs/reference/glossary/>Glossary</a></li></ul></div></div></div></nav></div><div class=article-container><button tabindex=-1 id=sidebar-toggler title="Toggle the navigation bar"><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#pull"/></svg></button><nav aria-label=Breadcrumb><ol><li><a href=/v1.3/ title="Connect, secure, control, and observe services.">Istio</a></li><li><a href=/v1.3/docs/ title="Learn how to deploy, use, and operate Istio.">Docs</a></li><li><a href=/v1.3/docs/concepts/ title="Learn about the different parts of the Istio system and the abstractions it uses.">Concepts</a></li><li>Deployment Models</li></ol></nav><article aria-labelledby=title><div class=title-area><div><h1 id=title>Deployment Models</h1><p class=byline><span title="1817 words"><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#clock"/></svg><span>&nbsp;</span>9 minute read</span></p></div></div><nav class=toc-inlined aria-label="Table of Contents"><div><hr><ol><li role=none aria-label="Cluster models"><a href=#cluster-models>Cluster models</a><ol><li role=none aria-label="Single cluster"><a href=#single-cluster>Single cluster</a><li role=none aria-label="Multiple clusters"><a href=#multiple-clusters>Multiple clusters</a></ol></li><li role=none aria-label="Network models"><a href=#network-models>Network models</a><ol><li role=none aria-label="Single network"><a href=#single-network>Single network</a><li role=none aria-label="Multiple networks"><a href=#multiple-networks>Multiple networks</a></ol></li><li role=none aria-label="Control plane models"><a href=#control-plane-models>Control plane models</a><li role=none aria-label="Identity and trust models"><a href=#identity-and-trust-models>Identity and trust models</a><ol><li role=none aria-label="Trust within a mesh"><a href=#trust-within-a-mesh>Trust within a mesh</a><li role=none aria-label="Trust between meshes"><a href=#trust-between-meshes>Trust between meshes</a></ol></li><li role=none aria-label="Mesh models"><a href=#mesh-models>Mesh models</a><ol><li role=none aria-label="Single mesh"><a href=#single-mesh>Single mesh</a><li role=none aria-label="Multiple meshes"><a href=#multiple-meshes>Multiple meshes</a></ol></li><li role=none aria-label="Tenancy models"><a href=#tenancy-models>Tenancy models</a><ol><li role=none aria-label="Namespace tenancy"><a href=#namespace-tenancy>Namespace tenancy</a><li role=none aria-label="Cluster tenancy"><a href=#cluster-tenancy>Cluster tenancy</a></ol></li><li role=none aria-label="See also"><a href=#see-also>See also</a></li></ol><hr></div></nav><p>Important system models impact your overall Istio deployment model. This page
discusses the options for each of these models and describes how you can
configure Istio to address them.</p><h2 id=cluster-models>Cluster models</h2><p>The workload instances of your application run in one or more
<span class=term data-title=Cluster data-body="&lt;p&gt;A cluster is set of compute nodes that run containerized applications.
Typically, the compute nodes comprising a cluster can reach each other directly.
Clusters limit external access through rules or policies.&lt;/p&gt;">clusters</span>. For isolation, performance, and
high availability, you can confine clusters to availability zones and regions.</p><p>Production systems, depending on their requirements, can run across multiple
clusters spanning a number of zones or regions, leveraging cloud load balancers
to handle things like locality and zonal or regional fail over.</p><p>In most cases, clusters represent boundaries for configuration and endpoint
discovery. For example, each Kubernetes cluster has an API Server which manages
the configuration for the cluster as well as serving
<span class=term data-title="Service Endpoint" data-body='&lt;p&gt;The network-reachable manifestation of a &lt;a href="#service"&gt;service&lt;/a&gt;.
&lt;a href="#workload-instance"&gt;Workload instances&lt;/a&gt; expose service endpoints but not all
services have service endpoints.&lt;/p&gt;'>service endpoint</span> information as pods are brought up
or down. Since Kubernetes configures this behavior on a per-cluster basis, this
approach helps limit the potential problems caused by incorrect configurations.</p><p>In Istio, you can configure a single service mesh to span any number of
clusters.</p><h3 id=single-cluster>Single cluster</h3><p>In the simplest case, you can confine an Istio mesh to a single
<span class=term data-title=Cluster data-body="&lt;p&gt;A cluster is set of compute nodes that run containerized applications.
Typically, the compute nodes comprising a cluster can reach each other directly.
Clusters limit external access through rules or policies.&lt;/p&gt;">cluster</span>. A cluster usually operates over a
<a href=#single-network>single network</a>, but it varies between infrastructure
providers. A single cluster and single network model includes a control plane,
which results in the simplest Istio deployment.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:91.74921915843377%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/single-cluster.svg title="Single cluster"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/single-cluster.svg alt="A service mesh with a single cluster"></a></div><figcaption>A service mesh with a single cluster</figcaption></figure><p>Single cluster deployments offer simplicity, but lack other features, for
example, fault isolation and fail over. If you need higher availability, you
should use multiple clusters.</p><h3 id=multiple-clusters>Multiple clusters</h3><p>You can configure a single mesh to include
multiple <span class=term data-title=Cluster data-body="&lt;p&gt;A cluster is set of compute nodes that run containerized applications.
Typically, the compute nodes comprising a cluster can reach each other directly.
Clusters limit external access through rules or policies.&lt;/p&gt;">clusters</span>. Using a
<span class=term data-title=Multi-Cluster data-body='&lt;p&gt;Multi-cluster is a deployment model that consists of a
&lt;a href="/docs/reference/glossary/#service-mesh"&gt;mesh&lt;/a&gt; with multiple
&lt;a href="/docs/reference/glossary/#cluster"&gt;clusters&lt;/a&gt;.&lt;/p&gt;'>multi-cluster</span> deployment within a single mesh affords
the following capabilities beyond that of a single cluster deployment:</p><ul><li>Fault isolation and fail over: <code>cluster-1</code> goes down, fail over to <code>cluster-2</code>.</li><li>Location-aware routing and fail over: Send requests to the nearest service.</li><li>Various <a href=#control-plane-models>control plane models</a>: Support different
levels of availability.</li><li>Team or project isolation: Each team runs its own set of clusters.</li></ul><figure style=width:75%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:65.0971323771268%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/multi-cluster.svg title=Multi-cluster><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/multi-cluster.svg alt="A service mesh with multiple clusters"></a></div><figcaption>A service mesh with multiple clusters</figcaption></figure><p>Multi-cluster deployments give you a greater degree of isolation and
availability but increase complexity. If your systems have high availability
requirements, you likely need clusters across multiple zones and regions. You
can canary configuration changes or new binary releases in a single cluster,
where the configuration changes only affect a small amount of user traffic.
Additionally, if a cluster has a problem, you can temporarily route traffic to
nearby clusters until you address the issue.</p><p>You can configure inter-cluster communication based on the
<a href=#network-models>network</a> and the options supported by your cloud provider. For
example, if two clusters reside on the same underlying network, you can enable
cross-cluster communication by simply configuring firewall rules.</p><h2 id=network-models>Network models</h2><p>Many production systems require multiple networks or subnets for isolation
and high availability. Istio supports spanning a service mesh over a variety of
network topologies. This approach allows you to select the network model that
fits your existing network topology.</p><h3 id=single-network>Single network</h3><p>In the simplest case, a service mesh operates over a single fully connected
network. In a single network model, all
<span class=term data-title="Workload Instance" data-body='&lt;p&gt;A single instantiation of a &lt;a href="#workload"&gt;workload&amp;rsquo;s&lt;/a&gt; binary.
A workload instance can expose zero or more &lt;a href="#service-endpoint"&gt;service endpoints&lt;/a&gt;,
and can consume zero or more &lt;a href="#service"&gt;services&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Workload instances have a number of properties:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Name and namespace&lt;/li&gt;
&lt;li&gt;Unique ID&lt;/li&gt;
&lt;li&gt;IP Address&lt;/li&gt;
&lt;li&gt;Labels&lt;/li&gt;
&lt;li&gt;Principal&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These properties are available in policy and telemetry configuration
using the many &lt;a href="/docs/reference/config/policy-and-telemetry/attribute-vocabulary/"&gt;&lt;code&gt;source.*&lt;/code&gt; and &lt;code&gt;destination.*&lt;/code&gt; attributes&lt;/a&gt;.&lt;/p&gt;'>workload instances</span>
can reach each other directly without an Istio gateway.</p><p>A single network allows Istio to configure service consumers in a uniform
way across the mesh with the ability to directly address workload instances.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:75.78194040013328%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/single-net.svg title="Single network"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/single-net.svg alt="A service mesh with a single network"></a></div><figcaption>A service mesh with a single network</figcaption></figure><h3 id=multiple-networks>Multiple networks</h3><p>You can span a single service mesh across multiple networks; such a
configuration is known as <strong>multi-network</strong>.</p><p>Multiple networks afford the following capabilities beyond that of single networks:</p><ul><li>Overlapping IP or VIP ranges for <strong>service endpoints</strong></li><li>Crossing of administrative boundaries</li><li>Fault tolerance</li><li>Scaling of network addresses</li><li>Compliance with standards that require network segmentation</li></ul><p>In this model, the workload instances in different networks can only reach each
other through one or more <a href=/v1.3/docs/concepts/traffic-management/#gateways>Istio gateways</a>.
Istio uses <strong>partitioned service discovery</strong> to provide consumers a different
view of <span class=term data-title="Service Endpoint" data-body='&lt;p&gt;The network-reachable manifestation of a &lt;a href="#service"&gt;service&lt;/a&gt;.
&lt;a href="#workload-instance"&gt;Workload instances&lt;/a&gt; expose service endpoints but not all
services have service endpoints.&lt;/p&gt;'>service endpoint</span>s. The view depends on the
network of the consumers.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:75.57262768530374%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/multi-net.svg title="Multi-network deployment"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/multi-net.svg alt="A service mesh with multiple networks"></a></div><figcaption>A service mesh with multiple networks</figcaption></figure><h2 id=control-plane-models>Control plane models</h2><p>An Istio mesh uses the <span class=term data-title="Control Plane" data-body="&lt;p&gt;A control plane is a set of system services that configure the mesh or a subset of
the mesh to manage the communication between the workload instances within.
All instances of a control plane in a single mesh share the same configuration source.&lt;/p&gt;">control plane</span> to configure all
communication between workload instances within the mesh. You can replicate the
control plane, and workload instances connect to any control plane instance to
get their configuration.</p><p>In the simplest case, you can run your mesh with a control plane on a single
cluster.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:91.74921915843377%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/single-cluster.svg title="Single control plane"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/single-cluster.svg alt="A service mesh with a control plane"></a></div><figcaption>A service mesh with a control plane</figcaption></figure><p>Multi-cluster deployments can also share control plane instances. In this case,
the control plane instances can reside in one or more clusters.</p><figure style=width:75%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:52.89403650064289%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/shared-control.svg title="Shared control plane"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/shared-control.svg alt="A service mesh with two clusters sharing a control plane"></a></div><figcaption>A service mesh with two clusters sharing a control plane</figcaption></figure><p>For high availability, you should deploy a control plane across multiple
clusters, zones, or regions.</p><figure style=width:75%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:92.28423056604902%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/multi-control.svg title="Multiple control planes"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/multi-control.svg alt="A service mesh with control plane instances for each region"></a></div><figcaption>A service mesh with control plane instances for each region</figcaption></figure><p>This model affords the following benefits:</p><ul><li><p>Improved availability: If a control plane becomes unavailable, the scope of
the outage is limited to only that control plane.</p></li><li><p>Configuration isolation: You can make configuration changes in one cluster,
zone, or region without impacting others.</p></li></ul><p>You can improve control plane availability through fail over. When a control
plane instance becomes unavailable, workload instances can connect to
another available control plane instance. Fail over can happen across clusters,
zones, or regions.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:52.89403650064289%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/failover.svg title="Control plane fail over"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/failover.svg alt="A service mesh after a control plane instance fails"></a></div><figcaption>A service mesh after a control plane instance fails</figcaption></figure><p>The following list ranks control plane deployment examples by availability:</p><ul><li>One cluster per region (<strong>lowest availability</strong>)</li><li>Multiple clusters per region</li><li>One cluster per zone</li><li>Multiple clusters per zone</li><li>Each cluster (<strong>highest availability</strong>)</li></ul><h2 id=identity-and-trust-models>Identity and trust models</h2><p>When a workload instance is created within a service mesh, Istio assigns the
workload an <span class=term data-title=Identity data-body='&lt;p&gt;Identity is a fundamental security infrastructure concept. The Istio identity
model is based on a first-class workload identity. At the beginning of
service-to-service communication, the two parties exchange credentials with
their identity information for mutual authentication purposes.&lt;/p&gt;
&lt;p&gt;Clients check the server’s identity against their secure naming information to
determine if the server is authorized to run the service.&lt;/p&gt;
&lt;p&gt;Servers check the client&amp;rsquo;s identity to determine what information the client can
access. Servers base that determination on the configured authorization
policies.&lt;/p&gt;
&lt;p&gt;Using identity, servers can audit the time information was accessed and what
information was accessed by a specific client. They can also charge clients
based on the services they use and reject any clients that failed to pay their
bill from accessing the services.&lt;/p&gt;
&lt;p&gt;The Istio identity model is flexible and granular enough to represent a human
user, an individual service, or a group of services. On platforms without
first-class service identity, Istio can use other identities that can group
service instances, such as service names.&lt;/p&gt;
&lt;p&gt;Istio supports the following service identities on different platforms:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Kubernetes: Kubernetes service account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GKE/GCE: GCP service account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GCP: GCP service account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;AWS: AWS IAM user/role account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;On-premises (non-Kubernetes): user account, custom service account, service
name, Istio service account, or GCP service account. The custom service
account refers to the existing service account just like the identities that
the customer’s Identity Directory manages.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Typically, the &lt;a href="/docs/reference/glossary/#trust-domain"&gt;trust domain&lt;/a&gt; specifies
the mesh the identity belongs to.&lt;/p&gt;'>identity</span>.</p><p>The Certificate Authority (CA) creates and signs the certificates used to verify
the identities used within the mesh. You can verify the identity of the message sender
with the public key of the CA that created and signed the certificate
for that identity. A <strong>trust bundle</strong> is the set of all CA public keys used by
an Istio mesh. With a mesh&rsquo;s trust bundle, anyone can verify the sender of any
message coming from that mesh.</p><h3 id=trust-within-a-mesh>Trust within a mesh</h3><p>Within a single Istio mesh, Istio ensures each workload instance has an
appropriate certificate representing its own identity, and the trust bundle
necessary to recognize all identities within the mesh and any federated meshes.
The CA only creates and signs the certificates for those identities. This model
allows workload instances in the mesh to authenticate each other when
communicating.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:91.74921915843377%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/single-trust.svg title="Trust within a mesh"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/single-trust.svg alt="A service mesh with a certificate authority"></a></div><figcaption>A service mesh with a certificate authority</figcaption></figure><h3 id=trust-between-meshes>Trust between meshes</h3><p>If a service in a mesh requires a service in another, you must federate identity
and trust between the two meshes. To federate identity and trust, you must
exchange the trust bundles of the meshes. You can exchange the trust bundles
either manually or automatically using a protocol such as <a href=https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Federation.md>SPIFFE Trust Domain Federation</a>.
Once you import a trust bundle to a mesh, you can configure local policies for
those identities.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:52.79593627076436%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/multi-trust.svg title="Trust between meshes"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/multi-trust.svg alt="Multiple service meshes with certificate authorities"></a></div><figcaption>Multiple service meshes with certificate authorities</figcaption></figure><h2 id=mesh-models>Mesh models</h2><p>Istio supports having all of your services in a
<span class=term data-title="Service Mesh" data-body='&lt;p&gt;A &lt;em&gt;service mesh&lt;/em&gt; or simply &lt;em&gt;mesh&lt;/em&gt; is an infrastructure layer that enables
managed, observable and secure communication between
&lt;a href="/docs/reference/glossary/#workload-instance"&gt;workload instances&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Service names combined with a namespace are unique within a mesh.
In a &lt;a href="/docs/reference/glossary/#multi-cluster"&gt;multi-cluster&lt;/a&gt; mesh, for example,
the &lt;code&gt;bar&lt;/code&gt; service in the &lt;code&gt;foo&lt;/code&gt; namespace in &lt;code&gt;cluster-1&lt;/code&gt; is considered the same
service as the &lt;code&gt;bar&lt;/code&gt; service in the &lt;code&gt;foo&lt;/code&gt; namespace in &lt;code&gt;cluster-2&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Since &lt;a href="/docs/reference/glossary/#identity"&gt;identities&lt;/a&gt; are shared within the service
mesh, workload instances can authenticate communication with any other workload
instance within the same service mesh.&lt;/p&gt;'>mesh</span>, or federating multiple meshes
together, which is also known as <span class=term data-title=Multi-Mesh data-body='&lt;p&gt;Multi-mesh is a deployment model that consists of two or more &lt;a href="/docs/reference/glossary/#service-mesh"&gt;service meshes&lt;/a&gt;.
Each mesh has independent administration for naming and identities but you can
expose services between meshes through &lt;a href="/docs/reference/glossary/#mesh-federation"&gt;mesh federation&lt;/a&gt;.
The resulting deployment is a multi-mesh deployment.&lt;/p&gt;'>multi-mesh</span>.</p><h3 id=single-mesh>Single mesh</h3><p>The simplest Istio deployment is a single mesh. Within a mesh, service names are
unique. For example, only one service can have the name <code>mysvc</code> in the <code>foo</code>
namespace. Additionally, workload instances share a common identity since
service account names are unique within a namespace, just like service names.</p><p>A single mesh can span <a href=#cluster-models>one or more clusters</a> and
<a href=#network-models>one or more networks</a>. Within a mesh,
<a href=#namespace-tenancy>namespaces</a> are used for <a href=#tenancy-models>tenancy</a>.</p><h3 id=multiple-meshes>Multiple meshes</h3><p>Multiple mesh deployments result from <span class=term data-title="Mesh Federation" data-body='&lt;p&gt;Mesh federation is the act of exposing services between meshes and enabling
communication across mesh boundaries. Each mesh may expose a subset of its
services to enable one or more other meshes to consume the exposed services. You
can use mesh federation to enable communication between meshes in a
&lt;a href="/docs/concepts/deployment-models/#multiple-meshes"&gt;multi-mesh deployment&lt;/a&gt;.&lt;/p&gt;'>mesh federation</span>.</p><p>Multiple meshes afford the following capabilities beyond that of a single mesh:</p><ul><li>Organizational boundaries: lines of business</li><li>Service name or namespace reuse: multiple distinct uses of the <code>default</code>
namespace</li><li>Stronger isolation: isolating test workloads from production workloads</li></ul><p>You can enable inter-mesh communication with <span class=term data-title="Mesh Federation" data-body='&lt;p&gt;Mesh federation is the act of exposing services between meshes and enabling
communication across mesh boundaries. Each mesh may expose a subset of its
services to enable one or more other meshes to consume the exposed services. You
can use mesh federation to enable communication between meshes in a
&lt;a href="/docs/concepts/deployment-models/#multiple-meshes"&gt;multi-mesh deployment&lt;/a&gt;.&lt;/p&gt;'>mesh federation</span>. When federating, each mesh can expose a set of services and
identities, which all participating meshes can recognize.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:68.06079261254328%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/multi-mesh.svg title=Multi-mesh><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/multi-mesh.svg alt="Multiple service meshes"></a></div><figcaption>Multiple service meshes</figcaption></figure><p>To avoid service naming collisions, you can give each mesh a globally unique
<strong>mesh ID</strong>, to ensure that the fully qualified domain
name (FQDN) for each service is distinct.</p><p>When federating two meshes that do not share the same
<span class=term data-title="Trust Domain" data-body='&lt;p&gt;A trust domain is a unique name that Istio uses to create all
&lt;a href="/docs/reference/glossary/#identity"&gt;identities&lt;/a&gt; within a mesh. Every mesh has
an exclusive trust domain.&lt;/p&gt;
&lt;p&gt;For example in &lt;code&gt;spiffe://mytrustdomain.com/ns/default/sa/myname&lt;/code&gt; the substring
identifying the mesh is: &lt;code&gt;mytrustdomain.com&lt;/code&gt;. This substring is the trust
domain of the mesh.&lt;/p&gt;'>trust domain</span>, you must
<span class=term data-title="Mesh Federation" data-body='&lt;p&gt;Mesh federation is the act of exposing services between meshes and enabling
communication across mesh boundaries. Each mesh may expose a subset of its
services to enable one or more other meshes to consume the exposed services. You
can use mesh federation to enable communication between meshes in a
&lt;a href="/docs/concepts/deployment-models/#multiple-meshes"&gt;multi-mesh deployment&lt;/a&gt;.&lt;/p&gt;'>federate</span>
<span class=term data-title=Identity data-body='&lt;p&gt;Identity is a fundamental security infrastructure concept. The Istio identity
model is based on a first-class workload identity. At the beginning of
service-to-service communication, the two parties exchange credentials with
their identity information for mutual authentication purposes.&lt;/p&gt;
&lt;p&gt;Clients check the server’s identity against their secure naming information to
determine if the server is authorized to run the service.&lt;/p&gt;
&lt;p&gt;Servers check the client&amp;rsquo;s identity to determine what information the client can
access. Servers base that determination on the configured authorization
policies.&lt;/p&gt;
&lt;p&gt;Using identity, servers can audit the time information was accessed and what
information was accessed by a specific client. They can also charge clients
based on the services they use and reject any clients that failed to pay their
bill from accessing the services.&lt;/p&gt;
&lt;p&gt;The Istio identity model is flexible and granular enough to represent a human
user, an individual service, or a group of services. On platforms without
first-class service identity, Istio can use other identities that can group
service instances, such as service names.&lt;/p&gt;
&lt;p&gt;Istio supports the following service identities on different platforms:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Kubernetes: Kubernetes service account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GKE/GCE: GCP service account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GCP: GCP service account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;AWS: AWS IAM user/role account&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;On-premises (non-Kubernetes): user account, custom service account, service
name, Istio service account, or GCP service account. The custom service
account refers to the existing service account just like the identities that
the customer’s Identity Directory manages.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Typically, the &lt;a href="/docs/reference/glossary/#trust-domain"&gt;trust domain&lt;/a&gt; specifies
the mesh the identity belongs to.&lt;/p&gt;'>identity</span> and <strong>trust bundles</strong> between them. See the
section on <a href=#trust-between-meshes>Multiple Trust Domains</a> for an overview.</p><h2 id=tenancy-models>Tenancy models</h2><p>In Istio, a <strong>tenant</strong> is a group of users that share
common access and privileges to a set of deployed workloads. Generally, you
isolate the workload instances from multiple tenants from each other through
network configuration and policies.</p><p>You can configure tenancy models to satisfy the following organizational
requirements for isolation:</p><ul><li>Security</li><li>Policy</li><li>Capacity</li><li>Cost</li><li>Performance</li></ul><p>Istio supports two types of tenancy models:</p><ul><li><a href=#namespace-tenancy>Namespace tenancy</a></li><li><a href=#cluster-tenancy>Cluster tenancy</a></li></ul><h3 id=namespace-tenancy>Namespace tenancy</h3><p>Istio uses <a href="https://kubernetes.io/docs/reference/glossary/?fundamental=true#term-namespace">namespaces</a>
as a unit of tenancy within a mesh. Istio also works in environments that don&rsquo;t
implement namespace tenancy. In environments that do, you can grant a team
permission to deploy their workloads only to a given namespace or set of
namespaces. By default, services from multiple tenant namespaces can communicate
with each other.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:75.78194040013328%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/iso-ns.svg title="Isolated namespaces"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/iso-ns.svg alt="A service mesh with two isolated namespaces"></a></div><figcaption>A service mesh with two isolated namespaces</figcaption></figure><p>To improve isolation, you can selectively choose which services to expose to
other namespaces. You can configure authorization policies for exposed services
to restrict access to only the appropriate callers.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:75.78194040013328%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/exp-ns.svg title="Namespaces with an exposed service"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/exp-ns.svg alt="A service mesh with two namespaces and an exposed service"></a></div><figcaption>A service mesh with two namespaces and an exposed service</figcaption></figure><p>When using <a href=#multiple-clusters>multiple clusters</a>, the namespaces in each
cluster sharing the same name are considered the same namespace. For example,
<code>Service B</code> in the <code>foo</code> namespace of <code>cluster-1</code> and <code>Service B</code> in the
<code>foo</code> namespace of <code>cluster-2</code> refer to the same service, and Istio merges their
endpoints for service discovery and load balancing.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:75.78194040013328%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/cluster-ns.svg title="Multi-cluster namespaces"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/cluster-ns.svg alt="A service mesh with two clusters with the same namespace"></a></div><figcaption>A service mesh with clusters with the same namespace</figcaption></figure><h3 id=cluster-tenancy>Cluster tenancy</h3><p>Istio supports using clusters as a unit of tenancy. In this case, you can give
each team a dedicated cluster or set of clusters to deploy their
workloads. Permissions for a cluster are usually limited to the members of the
team that owns it. You can set various roles for finer grained control, for
example:</p><ul><li>Cluster administrator</li><li>Developer</li></ul><p>To use cluster tenancy with Istio, you configure each cluster as an independent
mesh. Alternatively, you can use Istio to implement a group of clusters as a
single tenant. Then, each team can own one or more clusters, but you configure
all their clusters as a single mesh. To connect the meshes of the various teams
together, you can federate the meshes into a multi-mesh deployment.</p><figure style=width:50%><div class=wrapper-with-intrinsic-ratio style=padding-bottom:76.17309435102204%><a data-skipendnotes=true href=/v1.3/docs/concepts/deployment-models/cluster-iso.svg title="Cluster isolation"><img class=element-to-stretch src=/v1.3/docs/concepts/deployment-models/cluster-iso.svg alt="Two isolated service meshes with two clusters and two namespaces"></a></div><figcaption>Two isolated service meshes with two clusters and two namespaces</figcaption></figure><p>Since a different team or organization operates each mesh, service naming
is rarely distinct. For example, the <code>mysvc</code> in the <code>foo</code> namespace of
<code>cluster-1</code> and the <code>mysvc</code> service in the <code>foo</code> namespace of
<code>cluster-2</code> do not refer to the same service. The most common example is the
scenario in Kubernetes where many teams deploy their workloads to the <code>default</code>
namespace.</p><p>When each team has their own mesh, cross-mesh communication follows the
concepts described in the <a href=#multiple-meshes>multiple meshes</a> model.</p><nav id=see-also><h2>See also</h2><div class=see-also><div class=entry><p class=link><a data-skipendnotes=true href=/v1.3/blog/2018/soft-multitenancy/>Istio Soft Multi-Tenancy Support</a></p><p class=desc>Using Kubernetes namespaces and RBAC to create an Istio soft multi-tenancy environment.</p></div></div></nav></article><nav class=pagenav><div class=left><a title="Introduces performance and scalability for Istio." href=/v1.3/docs/concepts/performance-and-scalability/><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#left-arrow"/></svg>Performance and Scalability</a></div><div class=right></div></nav><div id=endnotes-container aria-hidden=true><h2>Links</h2><ol id=endnotes></ol></div></div><div class=toc-container><nav class=toc aria-label="Table of Contents"><div id=toc><ol><li role=none aria-label="Cluster models"><a href=#cluster-models>Cluster models</a><ol><li role=none aria-label="Single cluster"><a href=#single-cluster>Single cluster</a><li role=none aria-label="Multiple clusters"><a href=#multiple-clusters>Multiple clusters</a></ol></li><li role=none aria-label="Network models"><a href=#network-models>Network models</a><ol><li role=none aria-label="Single network"><a href=#single-network>Single network</a><li role=none aria-label="Multiple networks"><a href=#multiple-networks>Multiple networks</a></ol></li><li role=none aria-label="Control plane models"><a href=#control-plane-models>Control plane models</a><li role=none aria-label="Identity and trust models"><a href=#identity-and-trust-models>Identity and trust models</a><ol><li role=none aria-label="Trust within a mesh"><a href=#trust-within-a-mesh>Trust within a mesh</a><li role=none aria-label="Trust between meshes"><a href=#trust-between-meshes>Trust between meshes</a></ol></li><li role=none aria-label="Mesh models"><a href=#mesh-models>Mesh models</a><ol><li role=none aria-label="Single mesh"><a href=#single-mesh>Single mesh</a><li role=none aria-label="Multiple meshes"><a href=#multiple-meshes>Multiple meshes</a></ol></li><li role=none aria-label="Tenancy models"><a href=#tenancy-models>Tenancy models</a><ol><li role=none aria-label="Namespace tenancy"><a href=#namespace-tenancy>Namespace tenancy</a><li role=none aria-label="Cluster tenancy"><a href=#cluster-tenancy>Cluster tenancy</a></ol></li><li role=none aria-label="See also"><a href=#see-also>See also</a></li></ol></div></nav></div></main><footer><div class=user-links><a class=channel title="Go download Istio 1.3.5 now" href=/v1.3/docs/setup#downloading-the-release aria-label="Download Istio"><span>download</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#download"/></svg>
</a><a class=channel title="Join the Istio discussion board to participate in discussions and get help troubleshooting problems" href=https://discuss.istio.io aria-label="Istio discussion board"><span>discuss</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#discourse"/></svg></a>
<a class=channel title="Stack Overflow is where you can ask questions and find curated answers on deploying, configuring, and using Istio" href=https://stackoverflow.com/questions/tagged/istio aria-label="Stack Overflow"><span>stack overflow</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#stackoverflow"/></svg></a>
<a class=channel title="Interactively discuss issues with the Istio community on Slack" href=https://istio.slack.com aria-label=slack><span>slack</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#slack"/></svg></a>
<a class=channel title="Follow us on Twitter to get the latest news" href=https://twitter.com/IstioMesh aria-label=Twitter><span>twitter</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#twitter"/></svg></a><div class=tag>for everyone</div></div><div class=info><p class=copyright>Istio Archive
1.3.5<br>&copy; 2019 Istio Authors, <a href=https://policies.google.com/privacy>Privacy Policy</a><br>Archived on November 14, 2019</p></div><div class=dev-links><a class=channel title="GitHub is where development takes place on Istio code" href=https://github.com/istio/community aria-label=GitHub><span>github</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#github"/></svg></a>
<a class=channel title="Access our team drive if you'd like to take a look at the Istio technical design documents" href=https://groups.google.com/forum/#!forum/istio-team-drive-access aria-label="team drive"><span>drive</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#drive"/></svg></a>
<a class=channel title="If you'd like to contribute to the Istio project, consider participating in our working groups" href=https://github.com/istio/community/blob/master/WORKING-GROUPS.md aria-label="working groups"><span>working groups</span><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#working-groups"/></svg></a><div class=tag>for developers</div></div></footer><script src=https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.7/umd/popper.min.js defer></script><div id=scroll-to-top-container aria-hidden=true><button id=scroll-to-top title="Back to top"><svg class="icon"><use xlink:href="/v1.3/img/icons.svg#top"/></svg></button></div></body></html>
Reference in New Issue View Git Blame Copy Permalink