istio · geeknoid · Nov 4, 2017 · Nov 3, 2017 · ldemailly · Nov 4, 2017
@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.8)
+    activesupport (4.2.9)
       i18n (~> 0.7)
       minitest (~> 5.1)
       thread_safe (~> 0.3, >= 0.3.4)
@@ -14,18 +14,19 @@ GEM
     coffee-script-source (1.11.1)
     colorator (1.1.0)
     colorize (0.8.1)
-    ethon (0.10.1)
+    concurrent-ruby (1.0.5)
+    ethon (0.11.0)
       ffi (>= 1.3.0)
     execjs (2.7.0)
     faraday (0.13.1)
       multipart-post (>= 1.2, < 3)
     ffi (1.9.18)
     forwardable-extended (2.6.0)
     gemoji (3.0.0)
-    github-pages (161)
-      activesupport (= 4.2.8)
+    github-pages (167)
+      activesupport (= 4.2.9)
       github-pages-health-check (= 1.3.5)
-      jekyll (= 3.5.2)
+      jekyll (= 3.6.2)
       jekyll-avatar (= 0.5.0)
       jekyll-coffeescript (= 1.0.2)
       jekyll-default-layout (= 0.1.4)
@@ -37,7 +38,7 @@ GEM
       jekyll-paginate (= 1.1.0)
       jekyll-readme-index (= 0.1.0)
       jekyll-redirect-from (= 0.12.1)
-      jekyll-relative-links (= 0.4.1)
+      jekyll-relative-links (= 0.5.1)
       jekyll-sass-converter (= 1.5.0)
       jekyll-seo-tag (= 2.3.0)
       jekyll-sitemap (= 1.1.1)
@@ -56,13 +57,13 @@ GEM
       jekyll-theme-tactile (= 0.1.0)
       jekyll-theme-time-machine (= 0.1.0)
       jekyll-titles-from-headings (= 0.4.0)
-      jemoji (= 0.8.0)
-      kramdown (= 1.13.2)
+      jemoji (= 0.8.1)
+      kramdown (= 1.14.0)
       liquid (= 4.0.0)
       listen (= 3.0.6)
       mercenary (~> 0.3)
       minima (= 2.1.1)
-      rouge (= 1.11.1)
+      rouge (= 2.2.1)
       terminal-table (~> 1.4)
     github-pages-health-check (1.3.5)
       addressable (~> 2.3)
@@ -73,7 +74,7 @@ GEM
     html-pipeline (2.7.1)
       activesupport (>= 2)
       nokogiri (>= 1.4)
-    html-proofer (3.7.3)
+    html-proofer (3.7.4)
       activesupport (>= 4.2, < 6.0)
       addressable (~> 2.3)
       colorize (~> 0.8)
@@ -82,17 +83,18 @@ GEM
       parallel (~> 1.3)
       typhoeus (~> 0.7)
       yell (~> 2.0)
-    i18n (0.8.6)
-    jekyll (3.5.2)
+    i18n (0.9.1)
+      concurrent-ruby (~> 1.0)
+    jekyll (3.6.2)
       addressable (~> 2.4)
       colorator (~> 1.0)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 1.1)
-      kramdown (~> 1.3)
+      kramdown (~> 1.14)
       liquid (~> 4.0)
       mercenary (~> 0.3.3)
       pathutil (~> 0.9)
-      rouge (~> 1.7)
+      rouge (>= 1.7, < 3)
       safe_yaml (~> 1.0)
     jekyll-avatar (0.5.0)
       jekyll (~> 3.0)
@@ -121,7 +123,7 @@ GEM
       jekyll (~> 3.0)
     jekyll-redirect-from (0.12.1)
       jekyll (~> 3.3)
-    jekyll-relative-links (0.4.1)
+    jekyll-relative-links (0.5.1)
       jekyll (~> 3.3)
     jekyll-sass-converter (1.5.0)
       sass (~> 3.4)
@@ -174,12 +176,12 @@ GEM
       jekyll (~> 3.3)
     jekyll-watch (1.5.0)
       listen (~> 3.0, < 3.1)
-    jemoji (0.8.0)
-      activesupport (~> 4.0)
+    jemoji (0.8.1)
+      activesupport (~> 4.0, >= 4.2.9)
       gemoji (~> 3.0)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0)
-    kramdown (1.13.2)
+    kramdown (1.14.0)
     liquid (4.0.0)
     listen (3.0.6)
       rb-fsevent (>= 0.9.3)
@@ -196,15 +198,15 @@ GEM
     octokit (4.7.0)
       sawyer (~> 0.8.0, >= 0.5.3)
     parallel (1.12.0)
-    pathutil (0.14.0)
+    pathutil (0.16.0)
       forwardable-extended (~> 2.6)
     public_suffix (2.0.5)
     rb-fsevent (0.10.2)
     rb-inotify (0.9.10)
       ffi (>= 0.5.0, < 2)
-    rouge (1.11.1)
+    rouge (2.2.1)
     safe_yaml (1.0.4)
-    sass (3.5.1)
+    sass (3.5.3)
       sass-listen (~> 4.0.0)
     sass-listen (4.0.0)
       rb-fsevent (~> 0.9, >= 0.9.4)
@@ -217,7 +219,7 @@ GEM
     thread_safe (0.3.6)
     typhoeus (0.8.0)
       ethon (>= 0.8.0)
-    tzinfo (1.2.3)
+    tzinfo (1.2.4)
       thread_safe (~> 0.1)
     unicode-display_width (1.3.0)
     yell (2.0.7)

@@ -7,7 +7,7 @@ order: 20
 layout: docs
 type: markdown
 ---
-
+{% include home.html %}
 
 <a name="rpcIstio.mixer.v1"></a>
 ## Package istio.mixer.v1
@@ -101,7 +101,7 @@ in the deployment. The primary attribute producer in Istio is Envoy, although
 specialized Mixer adapters and services can also generate attributes.
 
 The common baseline set of attributes available in most Istio deployments is defined
-[here](https://istio.io/docs/reference/config/mixer/attribute-vocabulary.html).
+[here]({{home}}/docs/reference/config/mixer/attribute-vocabulary.html).
 
 Attributes are strongly typed. The supported attribute types are defined by
 [ValueType](https://github.com/istio/api/blob/master/mixer/v1/config/descriptor/value_type.proto).

@@ -47,7 +47,7 @@ are used by Mixer to validate configuration supplied by the operator at runtime.
   <td>repeated map&lt;string, <a href="#istio.mixer.v1.config.AttributeManifest.AttributeInfo">AttributeInfo</a>&gt;</td>
   <td><p>The set of attributes this Istio component will be responsible for producing at runtime. We map from attribute name to the attribute's specification. The name of an attribute, which is how attributes are referred to in aspect configuration, must conform to:</p>
 <pre><code>Name = IDENT { SEPARATOR IDENT };
-</code></pre><p>Where <code>IDENT</code> must match the regular expression <code>[a-z][a-z0-9]+</code> and <code>SEPARATOR</code> must match the regular expression <code>[\.-]</code>.</p><p>Attribute names must be unique within a single Istio deployment. The set of canonical attributes are described at <a href="https://istio.io/docs/reference/config/mixer/attribute-vocabulary.html">https://istio.io/docs/reference/config/mixer/attribute-vocabulary.html</a>. Attributes not in that list should be named with a component-specific suffix such as request.count-my.component</p></td>
+</code></pre><p>Where <code>IDENT</code> must match the regular expression <code>[a-z][a-z0-9]+</code> and <code>SEPARATOR</code> must match the regular expression <code>[\.-]</code>.</p><p>Attribute names must be unique within a single Istio deployment. The set of canonical attributes are described at <a href="{{home}}/docs/reference/config/mixer/attribute-vocabulary.html">{{home}}/docs/reference/config/mixer/attribute-vocabulary.html</a>. Attributes not in that list should be named with a component-specific suffix such as request.count-my.component</p></td>
  </tr>
 </table>
 

@@ -7,7 +7,7 @@ order: 1160
 layout: docs
 type: markdown
 ---
-
+{% include home.html %}
 
 <a name="rpcListentryIndex"></a>
 ### Index
@@ -21,8 +21,8 @@ ListEntry is used to verify the presence/absence of a string
 within a list.
 
 When writing the configuration, the value for the fields associated with this template can either be a
-literal or an [expression](https://istio.io/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
-then the expression's [inferred type](https://istio.io/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
+literal or an [expression]({{home}}/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
+then the expression's [inferred type]({{home}}/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
 
 Example config:
 

@@ -7,6 +7,7 @@ order: 1170
 layout: docs
 type: markdown
 ---
+{% include home.html %}
 
 <a name="rpcLogentry"></a>
 ## Package logentry
@@ -22,8 +23,8 @@ type: markdown
 LogEntry represents an individual entry within a log.
 
 When writing the configuration, the value for the fields associated with this template can either be a
-literal or an [expression](https://istio.io/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
-then the expression's [inferred type](https://istio.io/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
+literal or an [expression]({{home}}/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
+then the expression's [inferred type]({{home}}/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
 
 Example config:
 

@@ -7,6 +7,7 @@ order: 1180
 layout: docs
 type: markdown
 ---
+{% include home.html %}
 
 <a name="rpcMetric"></a>
 ## Package metric
@@ -22,8 +23,8 @@ type: markdown
 Metric represents a single piece of data to report.
 
 When writing the configuration, the value for the fields associated with this template can either be a
-literal or an [expression](https://istio.io/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
-then the expression's [inferred type](https://istio.io/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
+literal or an [expression]({{home}}/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
+then the expression's [inferred type]({{home}}/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
 
 Example config:
 

@@ -7,6 +7,7 @@ order: 1190
 layout: docs
 type: markdown
 ---
+{% include home.html %}
 
 <a name="rpcQuota"></a>
 ## Package quota
@@ -22,8 +23,8 @@ type: markdown
 Quota represents a piece of data to check Quota for.
 
 When writing the configuration, the value for the fields associated with this template can either be a
-literal or an [expression](https://istio.io/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
-then the expression's [inferred type](https://istio.io/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
+literal or an [expression]({{home}}/docs/reference/config/mixer/expression-language.html). Please note that if the datatype of a field is not istio.mixer.v1.config.descriptor.ValueType,
+then the expression's [inferred type]({{home}}/docs/reference/config/mixer/expression-language.html#type-checking) must match the datatype of the field.
 
 Example config:
 

@@ -67,7 +67,7 @@ has filename `tbd.md`. You don't need to put
 "Istio" in the filename, because "Istio" is already in the
 URL for the topic, for example:
 ```
-https://istio.io/docs/tasks/tbd.html
+{{home}}/docs/tasks/tbd.html
 ```
 
 ## Updating the front matter

@@ -128,7 +128,7 @@ rules.
   You can use other features of the route rules such as redirects,
   rewrites, regular expression based match in HTTP headers, websocket
   upgrades, timeouts, retries, and so on. Please refer to the
-  [routing rules](https://istio.io/docs/reference/config/traffic-rules/routing-rules.html)
+  [routing rules]({{home}}/docs/reference/config/traffic-rules/routing-rules.html)
   for more details.
 
 ## Verifying ingress

@@ -8,8 +8,9 @@ layout: post
 type: markdown
 redirect_from: "/blog/0.1-announcement.html"
 ---
+{% include home.html %}
 
-Google, IBM, and Lyft are proud to announce the first public release of [Istio](https://istio.io/): an open source project that provides a uniform way to connect, secure, manage and monitor microservices. Our current release is targeted at the [Kubernetes](https://kubernetes.io/) environment; we intend to add support for other environments such as virtual machines and Cloud Foundry in the coming months.
+Google, IBM, and Lyft are proud to announce the first public release of [Istio]({{home}}/): an open source project that provides a uniform way to connect, secure, manage and monitor microservices. Our current release is targeted at the [Kubernetes](https://kubernetes.io/) environment; we intend to add support for other environments such as virtual machines and Cloud Foundry in the coming months.
 Istio adds traffic management to microservices and creates a basis for value-add capabilities like security, monitoring, routing, connectivity management and policy.  The software is built using the battle-tested [Envoy](https://envoyproxy.github.io/envoy/) proxy from Lyft, and gives visibility and control over traffic *without requiring any changes to application code*. Istio gives CIOs a powerful tool to enforce security, policy and compliance requirements across the enterprise.
 
 <!--end_excerpt-->
@@ -72,7 +73,7 @@ We are excited to see early commitment to support the project from many companie
 
 To get involved, connect with us via any of these channels:
 
-* [istio.io](https://istio.io) for documentation and examples.
+* [istio.io]({{home}}) for documentation and examples.
 
 * The [istio-users@googlegroups.com](https://groups.google.com/forum/#!forum/istio-users) mailing list for general discussions,
 or [istio-announce@googlegroups.com](https://groups.google.com/forum/#!forum/istio-announce) for key announcements regarding the project. 

@@ -8,10 +8,11 @@ layout: post
 type: markdown
 redirect_from: "/blog/0.1-auth.html"
 ---
+{% include home.html %}
 
 Conventional network security approaches fail to address security threats to distributed applications deployed in dynamic production environments. Today, we describe how Istio Auth enables enterprises to transform their security posture from just protecting the edge to consistently securing all inter-service communications deep within their applications. With Istio Auth, developers and operators can protect services with sensitive data against unauthorized insider access and they can achieve this without any changes to the application code!
 
-Istio Auth is the security component of the broader [Istio platform](https://istio.io/). It incorporates the learnings of securing millions of microservice 
+Istio Auth is the security component of the broader [Istio platform]({{home}}/). It incorporates the learnings of securing millions of microservice 
 endpoints in Google’s production environment.
 
 <!--end_excerpt-->

@@ -7,6 +7,8 @@ attribution: The Istio Team
 layout: post
 type: markdown
 ---
+{% include home.html %}
+
 We launched Istio; an open platform to connect, manage, monitor, and secure microservices, on May 24, 2017. We have been humbled by the incredible interest, and rapid community growth of developers, operators, and partners. Our 0.1 release was focused on showing all the concepts of Istio in Kubernetes.
 
 Today we are happy to announce the 0.2 release which improves stability and performance, allows for cluster wide deployment and automated injection of sidecars in Kubernetes, adds policy and authentication for TCP services, and enables expansion of the mesh to include services deployed in virtual machines. In addition, Istio can now run outside Kubernetes, leveraging Consul/Nomad or Eureka. Beyond core features, Istio is now ready for extensions to be written by third party companies and developers.
@@ -36,12 +38,12 @@ you easily integrate your solution with Istio.
 
 * _Mesh expansion_: Istio mesh can now span services running outside of Kubernetes - like those running in virtual machines while enjoying benefits such as automatic mutual TLS authentication, traffic management, telemetry, and policy enforcement across the mesh. 
 
-* _Running outside Kubernetes_: We know many customers use other service registry and orchestration solutions like [Consul/Nomad](https://istio.io/docs/setup/consul/quick-start.html) and [Eureka](https://istio.io/docs/setup/eureka/quick-start.html). Istio Pilot can now run standalone outside Kubernetes, consuming information from these systems, and manage the Envoy fleet in VMs or containers.
+* _Running outside Kubernetes_: We know many customers use other service registry and orchestration solutions like [Consul/Nomad]({{home}}/docs/setup/consul/quick-start.html) and [Eureka]({{home}}/docs/setup/eureka/quick-start.html). Istio Pilot can now run standalone outside Kubernetes, consuming information from these systems, and manage the Envoy fleet in VMs or containers.
 
 
 ## Get involved in shaping the future of Istio 
 
-We have a growing [roadmap](https://istio.io/docs/reference/release-roadmap.html) ahead of us, full of great features to implement. Our focus next release is going to be on stability, reliability, integration with third party tools and multi-cluster use cases. 
+We have a growing [roadmap]({{home}}/docs/reference/release-roadmap.html) ahead of us, full of great features to implement. Our focus next release is going to be on stability, reliability, integration with third party tools and multi-cluster use cases. 
 
 The simplest way to get involved with Istio is by joining one of the many [working groups](https://github.com/istio/istio/blob/master/GROUPS.md) that align with your interests. Working groups will start meeting regularly, triaging issues in their area and help define roadmap of that area, etc,. Have something you’d like to broadcast to the Istio community? Share your voice at our weekly [community meeting](https://docs.google.com/document/d/14ZCWMfEV9MPDYrjhKYMErVXHTZrSwJNMm1ztKo8efPw/), and through the [mailing lists](https://github.com/istio/istio/blob/master/GROUPS.md#master-working-group-list).