From 214646c19d24253360246deb44c87d34727a3205 Mon Sep 17 00:00:00 2001
From: Vadim Eisenberg <vadime@il.ibm.com>
Date: Sun, 4 Nov 2018 17:31:05 +0200
Subject: [PATCH] remove references to envoyproxy.io api-v1

in the latest envoyproxy.io (1.9) api-v1 was removed
---
 networking/v1alpha3/destination_rule.pb.go            | 2 +-
 networking/v1alpha3/destination_rule.proto            | 4 ++--
 networking/v1alpha3/istio.networking.v1alpha3.pb.html | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/networking/v1alpha3/destination_rule.pb.go b/networking/v1alpha3/destination_rule.pb.go
index 58406ce7d1..26e8a474f6 100644
--- a/networking/v1alpha3/destination_rule.pb.go
+++ b/networking/v1alpha3/destination_rule.pb.go
@@ -1066,7 +1066,7 @@ func (m *OutlierDetection) GetMaxEjectionPercent() int32 {
 }
 
 // SSL/TLS related settings for upstream connections. See Envoy's [TLS
-// context](https://www.envoyproxy.io/docs/envoy/latest/api-v1/cluster_manager/cluster_ssl.html#config-cluster-manager-cluster-ssl)
+// context](https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/auth/cert.proto.html)
 // for more details. These settings are common to both HTTP and TCP upstreams.
 //
 // For example, the following rule configures a client to use mutual TLS
diff --git a/networking/v1alpha3/destination_rule.proto b/networking/v1alpha3/destination_rule.proto
index 08d89cf812..880862db5a 100644
--- a/networking/v1alpha3/destination_rule.proto
+++ b/networking/v1alpha3/destination_rule.proto
@@ -393,7 +393,7 @@ message ConnectionPoolSettings {
 // failures to a given host counts as an error when measuring the
 // consecutive errors metric. See Envoy's [outlier
 // detection](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/outlier)
-// for more details. 
+// for more details.
 //
 // The following rule sets a connection pool size of 100 connections and
 // 1000 concurrent HTTP2 requests, with no more than 10 req/connection to
@@ -445,7 +445,7 @@ message OutlierDetection {
 }
 
 // SSL/TLS related settings for upstream connections. See Envoy's [TLS
-// context](https://www.envoyproxy.io/docs/envoy/latest/api-v1/cluster_manager/cluster_ssl.html#config-cluster-manager-cluster-ssl)
+// context](https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/auth/cert.proto.html)
 // for more details. These settings are common to both HTTP and TCP upstreams.
 //
 // For example, the following rule configures a client to use mutual TLS
diff --git a/networking/v1alpha3/istio.networking.v1alpha3.pb.html b/networking/v1alpha3/istio.networking.v1alpha3.pb.html
index 31f7a5e7c4..bdfb888f79 100644
--- a/networking/v1alpha3/istio.networking.v1alpha3.pb.html
+++ b/networking/v1alpha3/istio.networking.v1alpha3.pb.html
@@ -3550,7 +3550,7 @@ <h2 id="TLSRoute">TLSRoute</h2>
 </section>
 <h2 id="TLSSettings">TLSSettings</h2>
 <section>
-<p>SSL/TLS related settings for upstream connections. See Envoy&rsquo;s <a href="https://www.envoyproxy.io/docs/envoy/latest/api-v1/cluster_manager/cluster_ssl.html#config-cluster-manager-cluster-ssl">TLS
+<p>SSL/TLS related settings for upstream connections. See Envoy&rsquo;s <a href="https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/auth/cert.proto.html">TLS
 context</a>
 for more details. These settings are common to both HTTP and TCP upstreams.</p>