mirror of https://github.com/istio/istio.io.git
89 lines
27 KiB
HTML
89 lines
27 KiB
HTML
<!DOCTYPE html><html lang="en" itemscope itemtype="https://schema.org/WebPage" style="overflow-y: scroll;"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge"><meta name="viewport" content="width=device-width, initial-scale=1"><meta name="title" content="Mixer Configuration"><meta name="og:title" content="Mixer Configuration"><meta name="og:image" content="/v0.3/img/logo.png"/><meta name="theme-color" content="#466BB0"/><meta name="description" content="An overview of the key concepts used to configure Mixer."><meta name="og:description" content="An overview of the key concepts used to configure Mixer."><title>Istioldie 0.3 / Mixer Configuration</title><script> window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)};ga.l=+new Date; ga('create', 'UA-98480406-2', 'auto'); ga('send', 'pageview'); </script> <script async src='https://www.google-analytics.com/analytics.js'></script><link rel="alternate" type="application/rss+xml" title="Istio Blog RSS" href="/v0.3/feed.xml"><link rel="shortcut icon" href="/v0.3/favicons/favicon.ico" ><link rel="apple-touch-icon" href="/v0.3/favicons/apple-touch-icon-180x180.png" sizes="180x180"><link rel="icon" type="image/png" href="/v0.3/favicons/favicon-16x16.png" sizes="16x16"><link rel="icon" type="image/png" href="/v0.3/favicons/favicon-32x32.png" sizes="32x32"><link rel="icon" type="image/png" href="/v0.3/favicons/android-36x36.png" sizes="36x36"><link rel="icon" type="image/png" href="/v0.3/favicons/android-48x48.png" sizes="48x48"><link rel="icon" type="image/png" href="/v0.3/favicons/android-72x72.png" sizes="72x72"><link rel="icon" type="image/png" href="/v0.3/favicons/android-96x196.png" sizes="96x196"><link rel="icon" type="image/png" href="/v0.3/favicons/android-144x144.png" sizes="144x144"><link rel="icon" type="image/png" href="/v0.3/favicons/android-192x192.png" sizes="192x192"><link rel="manifest" href="/v0.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=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900,900italic"><link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css"><link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css"><link rel="stylesheet" href="/v0.3/css/all.css"><link rel="stylesheet" href="/v0.3/css/prism.css"></head><body class="language-unknown"> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js"></script><div class="nav-hero-container" style="z-index: 200000;"><nav id="header-nav" class="navbar navbar-inverse" role="navigation" style="z-index: 200000;"><div class="container"><div class="row"><div class="col-md-11 nofloat center-block "><div class="navbar-header"> <button type="button" class="hamburger navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar-collapse-1" aria-expanded="false"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a class="navbar-brand" href="/v0.3/"><div> <img src="/v0.3/img/istio-logo.svg" alt="Istio Logo" height="54px"/> <span class="brand-name">Istioldie 0.3</span></div></a></div><div class="collapse navbar-collapse" id="navbar-collapse-1"><ul class="nav navbar-nav navbar-right"><li><a href="/v0.3/about" >About</a></li><li><a href="/v0.3/blog" >Blog</a></li><li><a href="/v0.3/docs/welcome" class='current'>Docs</a></li><li><a href="/v0.3/help" >Help</a></li><li><a href="/v0.3/community" >Community</a></li><li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href=""> <i class='fa fa-lg fa-cog'></i> <span class="caret"></span> </a><ul class="dropdown-menu"><h6 class="dropdown-header">Other versions of this site</h6><li> <a href="https://istio.io">Current Release</a></li><li> <a href="https://preliminary.istio.io">Next Release</a></li><li> <a href="https://archive.istio.io">Older Releases</a></li></ul></li><li><form name="cse" id="searchbox_demo" class="navbar-form navbar-right" 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" /><div class="form-group"><div class="input-group"> <input name="q" class="form-control search-box" type="text" size="30" /><div class="input-group-addon"> <span class="btn-search glyphicon glyphicon-search"></span></div></div></div></form> <script type="text/javascript" src="https://www.google.com/cse/brand?form=searchbox_demo"></script></li></ul></div></div></div></div></nav></div><div class="container"><div class="row"><div class="col-md-11 nofloat center-block" style="margin-top: 3px;"><ul class="col-sm-10 nav nav-tabs"><li role="presentation" ><a href="/v0.3/docs/welcome/">Welcome</a></li><li role="presentation" class='active'><a href="/v0.3/docs/concepts/">Concepts</a></li><li role="presentation" ><a href="/v0.3/docs/setup/">Setup</a></li><li role="presentation" ><a href="/v0.3/docs/tasks/">Tasks</a></li><li role="presentation" ><a href="/v0.3/docs/guides/">Guides</a></li><li role="presentation" ><a href="/v0.3/docs/reference/">Reference</a></li></ul></div></div></div><script src="/v0.3/js/navtree.min.js"></script><div class="container docs"><div class="row"><div class="col-md-11 nofloat center-block"><div class="row"><div id="sidebar-container" class="col-sm-3"><ul class="doc-side-nav"><li><h5 class='doc-side-nav-title'>Concepts</h5></li><script type="text/javascript"> var docs = []; docs.push({path: [ "index.md", ], url: "/docs/concepts/", title: "Concepts", order: 10, overview: "Concepts help you learn about the different parts of the Istio system and the abstractions it uses."}); docs.push({path: [ "policy-and-control", "attributes.md", ], url: "/docs/concepts/policy-and-control/attributes.html", title: "Attributes", order: 10, overview: "Explains the important notion of attributes, which is a central mechanism for how policies and control are applied to services within the mesh."}); docs.push({path: [ "policy-and-control", "index.md", ], url: "/docs/concepts/policy-and-control/", title: "Policies and Control", order: 40, overview: "Introduces the policy control mechanisms."}); docs.push({path: [ "policy-and-control", "mixer-config.md", ], url: "/docs/concepts/policy-and-control/mixer-config.html", title: "Mixer Configuration", order: 30, overview: "An overview of the key concepts used to configure Mixer."}); docs.push({path: [ "policy-and-control", "mixer.md", ], url: "/docs/concepts/policy-and-control/mixer.html", title: "Mixer", order: 20, overview: "Architectural deep-dive into the design of Mixer, which provides the policy and control mechanisms within the service mesh."}); docs.push({path: [ "security", "index.md", ], url: "/docs/concepts/security/", title: "Security", order: 30, overview: "Describes Istio's authorization and authentication functionality."}); docs.push({path: [ "security", "mutual-tls.md", ], url: "/docs/concepts/security/mutual-tls.html", title: "Mutual TLS Authentication", order: 10, overview: "Describes Istio's mutual TLS authentication architecture which provides a strong service identity and secure communication channels between services."}); docs.push({path: [ "traffic-management", "fault-injection.md", ], url: "/docs/concepts/traffic-management/fault-injection.html", title: "Fault Injection", order: 40, overview: "Introduces the idea of systematic fault injection that can be used to uncover conflicting failure recovery policies across services."}); docs.push({path: [ "traffic-management", "handling-failures.md", ], url: "/docs/concepts/traffic-management/handling-failures.html", title: "Handling Failures", order: 30, overview: "An overview of failure recovery capabilities in Envoy that can be leveraged by unmodified applications to improve robustness and prevent cascading failures."}); docs.push({path: [ "traffic-management", "index.md", ], url: "/docs/concepts/traffic-management/", title: "Traffic Management", order: 20, overview: "Describes the various Istio features focused on traffic routing and control."}); docs.push({path: [ "traffic-management", "load-balancing.md", ], url: "/docs/concepts/traffic-management/load-balancing.html", title: "Discovery & Load Balancing", order: 25, overview: "Describes how traffic is load balanced across instances of a service in the mesh."}); docs.push({path: [ "traffic-management", "overview.md", ], url: "/docs/concepts/traffic-management/overview.html", title: "Overview", order: 0, overview: "Provides a conceptual overview of traffic management in Istio and the features it enables."}); docs.push({path: [ "traffic-management", "pilot.md", ], url: "/docs/concepts/traffic-management/pilot.html", title: "Pilot", order: 10, overview: "Introduces Pilot, the component responsible for managing a distributed deployment of Envoy proxies in the service mesh."}); docs.push({path: [ "traffic-management", "request-routing.md", ], url: "/docs/concepts/traffic-management/request-routing.html", title: "Request Routing", order: 20, overview: "Describes how requests are routed between services in an Istio service mesh."}); docs.push({path: [ "traffic-management", "rules-configuration.md", ], url: "/docs/concepts/traffic-management/rules-configuration.html", title: "Rules Configuration", order: 50, overview: "Provides a high-level overview of the domain-specific language used by Istio to configure traffic management rules in the service mesh."}); docs.push({path: [ "what-is-istio", "goals.md", ], url: "/docs/concepts/what-is-istio/goals.html", title: "Design Goals", order: 20, overview: "Describes the core principles that Istio's design adheres to."}); docs.push({path: [ "what-is-istio", "index.md", ], url: "/docs/concepts/what-is-istio/", title: "What is Istio?", order: 10, overview: "A broad overview of the Istio system."}); docs.push({path: [ "what-is-istio", "overview.md", ], url: "/docs/concepts/what-is-istio/overview.html", title: "Overview", order: 15, overview: "Provides a conceptual introduction to Istio, including the problems it solves and its high-level architecture."}); genNavBarTree(docs) </script></ul></div><div id="tab-container" class="col-xs-1 tab-neg-margin pull-left"> <a id="sidebar-tab" class="glyphicon glyphicon-chevron-left" href="javascript:void 0;"> </a></div><div id="content-container" class="thin-left-border col-sm-9 markdown"><div id="toc" class="toc"></div><div id="doc-content"><h1>Mixer Configuration</h1><p>This page describes Mixer’s configuration model.</p><h2 id="background">Background</h2><p>Istio is a sophisticated system with hundreds of independent features. An Istio deployment can be a sprawling affair potentially involving dozens of services, with a swarm of Envoy proxies and Mixer instances to support them. In large deployments, many different operators, each with different scopes and areas of responsibility, may be involved in managing the overall deployment.</p><p>Mixer’s configuration model makes it possible to exploit all of its capabilities and flexibility, while remaining relatively simple to use. The model’s scoping features enable large support organizations to collectively manage complex deployments with ease. Some of the model’s key features include:</p><ul><li><p><strong>Designed for Operators</strong>. Service operators control all operational and policy aspects of a Mixer deployment by manipulating configuration resources.</p></li><li><p><strong>Flexible</strong>. The configuration model is built around Istio’s <a href="./attributes.html">attributes</a>, enabling operators unprecedented control over the policies used and telemetry produced within a deployment.</p></li><li><p><strong>Robust</strong>. The configuration model is designed to provide maximum static correctness guarantees to help reduce the potential for bad configuration changes leading to service outages.</p></li><li><p><strong>Extensible</strong>. The model is designed to support Istio’s overall extensibility story. New or custom <a href="./mixer.html#adapters">adapters</a> can be added to Istio and be fully manipulated using the same general mechanisms as existing adapters.</p></li></ul><h2 id="concepts">Concepts</h2><p>Mixer is an attribute processing machine. Requests arrive at Mixer with a set of <a href="./attributes.html"><em>attributes</em></a>, and based on these attributes, Mixer generates calls to a variety of infrastructure backends. A rate limit system, an ACL provider, and a policy enforcer are examples of infrastructure backends. The set of attributes determines which backend Mixer calls for a given request and what parameters each is given. In order to hide the details of individual backends, Mixer uses modules known as <a href="./mixer.html#adapters"><em>adapters</em></a>.</p><figure><img src="./img/mixer-config/machine.svg" alt="Attribute Machine" title="Attribute Machine" /><figcaption>Attribute Machine</figcaption></figure><p>Mixer’s configuration has the following central responsibilities:</p><ul><li>Describe which adapters are being used and how they operate.</li><li>Describe how to map request attributes into adapter inputs.</li><li>Describe when a particular adapter is called with specific inputs.</li></ul><p>Configuration is based on <em>adapters</em> and <em>templates</em>.</p><ul><li><strong>Adapters</strong> encapsulate the logic necessary to interface Mixer with a specific infrastructure backend.</li><li><strong>Templates</strong> define the schema for specifying request mapping from attributes to adapter inputs. A given adapter may support any number of templates.</li></ul><p>Configuration is expressed using a YAML format built around the following abstractions:</p><table><thead><tr><th>Concept</th><th>Description</th></tr></thead><tbody><tr><td><a href="#handlers">Handlers</a></td><td>A handler is a configured instance of an adapter. The adapter constructor parameters are specified as handler configuration.</td></tr><tr><td><a href="#instances">Instances</a></td><td>A (request) instance is the result of applying request attributes to the template mapping. The mapping is specified as an instance configuration.</td></tr><tr><td><a href="#rules">Rules</a></td><td>A rule defines when a particular handler is invoked using a specific template configuration.</td></tr></tbody></table><p>Configuration resources are expressed in Kubernetes resource syntax:</p><pre><code class="language-yaml">apiVersion: config.istio.io/v1alpha2
|
||
kind: rule, adapter kind, or template kind
|
||
metadata:
|
||
name: shortname
|
||
namespace: istio-system
|
||
spec:
|
||
# kind specific configuration.
|
||
</code></pre><ul><li><strong>apiVersion</strong> - A constant for an Istio release.</li><li><strong>kind</strong> - A Mixer assigned unique “kind” for every adapter and template.</li><li><strong>name</strong> - The configuration resource name.</li><li><strong>namespace</strong> - The namespace in which the configuration resource is applicable.</li><li><strong>spec</strong> - The <code>kind</code>-specific configuration.</li></ul><h3 id="handlers">Handlers</h3><p><a href="./mixer.html#adapters">Adapters</a> encapsulate the logic necessary to interface Mixer with specific external infrastructure backends such as <a href="https://prometheus.io">Prometheus</a>, <a href="https://newrelic.com">New Relic</a>, or <a href="https://cloud.google.com/logging">Stackdriver</a>. Individual adapters generally need operational parameters in order to do their work. For example, a logging adapter may require the IP address and port of the log sink.</p><p>Here is an example showing how to configure an adapter of kind = <code>listchecker</code>. The listchecker adapter checks an input value against a list. If the adapter is configured for a whitelist, it returns success if the input value is found in the list.</p><pre><code class="language-yaml">apiVersion: config.istio.io/v1alpha2
|
||
kind: listchecker
|
||
metadata:
|
||
name: staticversion
|
||
namespace: istio-system
|
||
spec:
|
||
providerUrl: http://white_list_registry/
|
||
blacklist: false
|
||
</code></pre><p><code>{metadata.name}.{kind}.{metadata.namespace}</code> is the fully qualified name of a handler. The fully qualified name of the above handler is <code>staticversion.listchecker.istio-system</code> and it must be unique. The schema of the data in the <code>spec</code> stanza depends on the specific adapter being configured.</p><p>Some adapters implement functionality that goes beyond connecting Mixer to a backend. For example, the <code>prometheus</code> adapter consumes metrics and aggregates them as distributions or counters in a configurable way.</p><pre><code class="language-yaml">apiVersion: config.istio.io/v1alpha2
|
||
kind: prometheus
|
||
metadata:
|
||
name: handler
|
||
namespace: istio-system
|
||
spec:
|
||
metrics:
|
||
- name: request_count
|
||
instance_name: requestcount.metric.istio-system
|
||
kind: COUNTER
|
||
label_names:
|
||
- destination_service
|
||
- destination_version
|
||
- response_code
|
||
- name: request_duration
|
||
instance_name: requestduration.metric.istio-system
|
||
kind: DISTRIBUTION
|
||
label_names:
|
||
- destination_service
|
||
- destination_version
|
||
- response_code
|
||
buckets:
|
||
explicit_buckets:
|
||
bounds: [0.005, 0.01, 0.025, 0.05, 0.1, 0.25, 0.5, 1, 2.5, 5, 10]
|
||
</code></pre><p>Each adapter defines its own particular format of configuration data. The exhaustive set of adapters and their specific configuration formats can be found <a href="/v0.3/docs/reference/config/mixer/adapters/">here</a>.</p><h3 id="instances">Instances</h3><p>Instance configuration specifies the request mapping from attributes to adapter inputs. The following is an example of a metric instance configuration that produces the <code>requestduration</code> metric.</p><pre><code class="language-yaml">apiVersion: config.istio.io/v1alpha2
|
||
kind: metric
|
||
metadata:
|
||
name: requestduration
|
||
namespace: istio-system
|
||
spec:
|
||
value: response.duration | "0ms"
|
||
dimensions:
|
||
destination_service: destination.service | "unknown"
|
||
destination_version: destination.labels["version"] | "unknown"
|
||
response_code: response.code | 200
|
||
monitored_resource_type: '"UNSPECIFIED"'
|
||
</code></pre><p>Note that all the dimensions expected in the handler configuration are specified in the mapping.</p><p>Each template defines its own particular format of configuration data. The exhaustive set of templates and their specific configuration formats can be found <a href="/v0.3/docs/reference/config/mixer/template/">here</a>.</p><h3 id="rules">Rules</h3><p>Rules specify when a particular handler is invoked with a specific instance configuration. Consider an example where you want to deliver the <code>requestduration</code> metric to the prometheus handler if the destination service is <code>service1</code> and the <code>x-user</code> request header has a specific value.</p><pre><code class="language-yaml">apiVersion: config.istio.io/v1alpha2
|
||
kind: rule
|
||
metadata:
|
||
name: promhttp
|
||
namespace: istio-system
|
||
spec:
|
||
match: destination.service == "service1.ns.svc.cluster.local" && request.headers["x-user"] == "user1"
|
||
actions:
|
||
- handler: handler.prometheus
|
||
instances:
|
||
- requestduration.metric.istio-system
|
||
</code></pre><p>A rule contains a <code>match</code> predicate expression and a list of actions to perform if the predicate is true. An action specifies the list of instances to be delivered to a handler. A rule must use the fully qualified names of handlers and instances. If the rule, handlers, and instances are all in the same namespace, the namespace suffix can be elided from the fully qualified name as seen in <code>handler.prometheus</code>.</p><p>The match predicate is an attribute expression, which are explained below.</p><h3 id="attribute-expressions">Attribute expressions</h3><p>Mixer features a number of independent <a href="./mixer.html#request-phases">request processing phases</a>. The <em>Attribute Processing</em> phase is responsible for ingesting a set of attributes and producing template instances necessary to invoke individual adapters. The phase operates by evaluating a series of <em>attribute expressions</em>.</p><p>You have already seen a few simple attribute expressions in the previous examples:</p><pre><code class="language-yaml"> destination_service: destination.service
|
||
response_code: response.code
|
||
destination_version: destination.labels["version"] | "unknown"
|
||
</code></pre><p>The sequences on the right-hand side of the colons are the simplest forms of attribute expressions. The first two only consist of attribute names. The <code>response_code</code> label is assigned the value from the <code>request.code</code> attribute.</p><p>Here’s an example of a conditional expression:</p><pre><code class="language-yaml"> destination_version: destination.labels["version"] | "unknown"
|
||
</code></pre><p>With the above, the <code>destination_version</code> label is assigned the value of <code>destination.labels["version"]</code>. However if that attribute is not present, the literal <code>"unknown"</code> is used.</p><p>The attributes that can be used in attribute expressions must be defined in an <a href="#manifests"><em>attribute manifest</em></a> for the deployment. Within the manifest, each attribute has a type which represents the kind of data that the attribute carries. In the same way, attribute expressions are also typed, and their type is derived from the attributes in the expression and the operators applied to these attributes.</p><p>Refer to the <a href="/v0.3/docs/reference/config/mixer/expression-language.html">attribute expression reference</a> for details.</p><h3 id="resolution">Resolution</h3><p>When a request arrives, Mixer goes through a number of <a href="./mixer.html#request-phases">request processing phases</a>. The Resolution phase is concerned with identifying the configuration resources to use in order to process the incoming request. For example, a request arriving at Mixer for service A likely has some configuration differences with requests arriving for service B. Resolution is about deciding which config resources to use for a request.</p><p>Resolution depends on a well-known attribute to guide its choice, called the <em>identity attribute</em>. The default identity attribute is <code>destination.service</code>. The mesh-wide configuration is stored in the <code>configDefaultNamespace</code> whose default value is <code>istio-system</code>.</p><p>Mixer goes through the following steps to arrive at the set of <code>actions</code>.</p><ol><li><p>Extract the value of the identity attribute from the request.</p></li><li><p>Extract the service namespace from the identity attribute.</p></li><li><p>Evaluate the <code>match</code> predicate for all rules in the <code>configDefaultNamespace</code> and the service namespace.</p></li></ol><p>The actions resulting from these steps are performed by Mixer.</p><h3 id="manifests">Manifests</h3><p>Manifests capture invariants about the components involved in a particular Istio deployment. The only kind of manifest supported at the moment are <em>attribute manifests</em> which are used to define the exact set of attributes produced by individual components. Manifests are supplied by component producers and inserted into a deployment’s configuration.</p><p>Here’s part of the manifest for the Istio proxy:</p><pre><code class="language-yaml">manifests:
|
||
- name: istio-proxy
|
||
revision: "1"
|
||
attributes:
|
||
source.name:
|
||
valueType: STRING
|
||
description: The name of the source.
|
||
destination.name:
|
||
valueType: STRING
|
||
description: The name of the destination
|
||
source.ip:
|
||
valueType: IP_ADDRESS
|
||
description: Did you know that descriptions are optional?
|
||
origin.user:
|
||
valueType: STRING
|
||
request.time:
|
||
valueType: TIMESTAMP
|
||
request.method:
|
||
valueType: STRING
|
||
response.code:
|
||
valueType: INT64
|
||
</code></pre><h2 id="examples">Examples</h2><p>You can find fully-formed examples of Mixer configuration by visiting the <a href="/v0.3/docs/guides">Guides</a>. Here is some <a href="https://github.com/istio/istio/blob/master/mixer/testdata/config">example configuration</a>.</p><h2 id="whats-next">What’s next</h2><ul><li>Read the <a href="/v0.3/blog/mixer-adapter-model.html">blog post</a> describing Mixer’s adapter model.</li></ul></div></div></div></div></div></div><script src="/v0.3/js/sidemenu.min.js"></script><footer><div class="container"><div class="row"><div class="col-lg-2 col-md-2 col-sm-2"></div><div class="col-lg-3 col-md-3 col-sm-3 col-xs-12 center-block"><ul><li><a class="header" href="/v0.3/docs/welcome">Docs</a></li><li><a href="/v0.3/docs/concepts">Concepts</a></li><li><a href="/v0.3/docs/setup">Setup</a></li><li><a href="/v0.3/docs/tasks">Tasks</a></li><li><a href="/v0.3/docs/guides">Guides</a></li><li><a href="/v0.3/docs/reference">Reference</a></li></ul></div><div class="col-lg-3 col-md-3 col-sm-3 col-xs-12 center-block"><ul><li><a class="header" href="/v0.3/help">Help</a></li><li><a href="/v0.3/faq">FAQ</a></li><li><a href="/v0.3/glossary">Glossary</a></li><li><a href="/v0.3/troubleshooting">Troubleshooting</a></li><li><a href="/v0.3/bugs">Report Bugs</a></li><li><a href="https://github.com/istio/istio.github.io/issues/new?title=Issue with _docs/concepts/policy-and-control/mixer-config.md">Doc Bugs & Gaps</a></li><li><a href="https://github.com/istio/istio.github.io/edit/master/_docs/concepts/policy-and-control/mixer-config.md">Edit This Page</a></li></ul></div><div class="col-lg-3 col-md-3 col-sm-3 col-xs-12 center-block"><ul><li> <a class="header" href="/v0.3/community">Community</a></li><li> <a href="https://groups.google.com/forum/#!forum/istio-users" target="_blank" rel="noopener">User</a> | <a href="https://groups.google.com/forum/#!forum/istio-dev" target="_blank" rel="noopener">Dev Mailing Lists</a></li><li><a href="https://twitter.com/IstioMesh" target="_blank" rel="noopener">Twitter</a></li><li><a href="https://stackoverflow.com/questions/tagged/istio" target="_blank" rel="noopener">Stack Overflow</a></li><li><a href="https://github.com/istio/community" target="_blank" rel="noopener">GitHub</a></li><li><a href="https://github.com/istio/community/blob/master/WORKING-GROUPS.md" target="_blank" rel="noopener">Working Groups</a></li></ul></div><div class="col-lg-1 col-md-1 col-sm-1"></div></div><div class="row"><p class="description small text-center"> Istio 0.3, Copyright © 2017 Istio Authors<br> Archived on 08-Dec-2017</p></div></div></footer><script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-validate/1.15.0/jquery.validate.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.form/4.2.1/jquery.form.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-visible/1.2.0/jquery.visible.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/1.7.1/clipboard.min.js"></script> <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script> <script src="/v0.3/js/common.min.js"></script> <script src="/v0.3/js/search.js"></script> <script src="/v0.3/js/prism.min.js"></script></body></html>
|