diff --git a/networking/v1alpha3/destination_rule.pb.go b/networking/v1alpha3/destination_rule.pb.go
index 229e1934c1..9b263002db 100644
--- a/networking/v1alpha3/destination_rule.pb.go
+++ b/networking/v1alpha3/destination_rule.pb.go
@@ -250,7 +250,6 @@ type DestinationRule struct {
 	// One or more named sets that represent individual versions of a
 	// service. Traffic policies can be overridden at subset level.
 	Subsets []*Subset `protobuf:"bytes,3,rep,name=subsets" json:"subsets,omitempty"`
-	// $hide_from_docs
 	// The resolution of a DestinationRule to apply to a service occurs in the
 	// context of a hierarchy of namespaces. This rule controls whether those
 	// namespaces are allowed to select this rule.
diff --git a/networking/v1alpha3/destination_rule.proto b/networking/v1alpha3/destination_rule.proto
index ff7b277d2c..1c340f8bbf 100644
--- a/networking/v1alpha3/destination_rule.proto
+++ b/networking/v1alpha3/destination_rule.proto
@@ -118,7 +118,6 @@ message DestinationRule {
   // service. Traffic policies can be overridden at subset level.
   repeated Subset subsets = 3;
 
-  // $hide_from_docs
   // The resolution of a DestinationRule to apply to a service occurs in the
   // context of a hierarchy of namespaces. This rule controls whether those
   // namespaces are allowed to select this rule.
diff --git a/networking/v1alpha3/istio.networking.v1alpha3.pb.html b/networking/v1alpha3/istio.networking.v1alpha3.pb.html
index 8720593094..c523127b17 100644
--- a/networking/v1alpha3/istio.networking.v1alpha3.pb.html
+++ b/networking/v1alpha3/istio.networking.v1alpha3.pb.html
@@ -669,6 +669,16 @@ <h2 id="DestinationRule">DestinationRule</h2>
 <p>One or more named sets that represent individual versions of a
 service. Traffic policies can be overridden at subset level.</p>
 
+</td>
+</tr>
+<tr id="DestinationRule-export_to">
+<td><code>exportTo</code></td>
+<td><code>string[]</code></td>
+<td>
+<p>The resolution of a DestinationRule to apply to a service occurs in the
+context of a hierarchy of namespaces. This rule controls whether those
+namespaces are allowed to select this rule.</p>
+
 </td>
 </tr>
 </tbody>
@@ -3230,7 +3240,7 @@ <h2 id="ServiceEntry">ServiceEntry</h2>
 
 <p>The following example demonstrates the use of a dedicated egress gateway
 through which all external service traffic is forwarded.
-The &lsquo;export_to&rsquo; field allows for control over the visibility of a service
+The &lsquo;exportTo&rsquo; field allows for control over the visibility of a service
 declaration to other namespaces in the mesh. By default a service is exported
 to all namespaces. The following example restricts the visibility to the
 current namespace, represented by &ldquo;.&rdquo;, so that it cannot be used by other
@@ -3244,8 +3254,8 @@ <h2 id="ServiceEntry">ServiceEntry</h2>
 spec:
   hosts:
   - httpbin.com
-  export_to:
-  - .
+  exportTo:
+  - &quot;.&quot;
   location: MESH_EXTERNAL
   ports:
   - number: 80
@@ -3288,7 +3298,7 @@ <h2 id="ServiceEntry">ServiceEntry</h2>
 spec:
   hosts:
   - httpbin.com
-  export_to:
+  exportTo:
   - *
   gateways:
   - mesh
@@ -3494,6 +3504,29 @@ <h2 id="ServiceEntry">ServiceEntry</h2>
 <td>
 <p>One or more endpoints associated with the service.</p>
 
+</td>
+</tr>
+<tr id="ServiceEntry-export_to">
+<td><code>exportTo</code></td>
+<td><code>string[]</code></td>
+<td>
+<p>A list of namespaces to which this service is exported. Exporting a service
+allows it to used by sidecars, gateways and virtual services defined in
+other namespaces. This feature provides a mechanism for service owners
+and mesh administrators to control the visibility of services across
+namespace boundaries.</p>
+
+<p>If no namespaces are specified then the service is exported to all
+namespaces by default.</p>
+
+<p>The value &ldquo;.&rdquo; is reserved and defines an export to the same namespace that
+the service is declared in, similarly the value &ldquo;*&rdquo; is reserved and
+defines an export to all namespaces.</p>
+
+<p>For a Kubernetes Service the equivalent effect can be achieved by setting
+the annotation &ldquo;networking.istio.io/exportTo&rdquo; to a comma-separated list
+of namespace names.</p>
+
 </td>
 </tr>
 <tr id="ServiceEntry-subject_alt_names">
@@ -4573,6 +4606,25 @@ <h2 id="VirtualService">VirtualService</h2>
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.</p>
 
+</td>
+</tr>
+<tr id="VirtualService-export_to">
+<td><code>exportTo</code></td>
+<td><code>string[]</code></td>
+<td>
+<p>A list of namespaces to which this virtual service is exported. Exporting a
+virtual service allows it to used by sidecars and gateways defined in
+other namespaces. This feature provides a mechanism for service owners
+and mesh administrators to control the visibility of virtual services
+across namespace boundaries.</p>
+
+<p>If no namespaces are specified then the virtual service is exported to all
+namespaces by default.</p>
+
+<p>The value &ldquo;.&rdquo; is reserved and defines an export to the same namespace that
+the virtual service is declared in, similarly the value &ldquo;*&rdquo; is reserved and
+defines an export to all namespaces.</p>
+
 </td>
 </tr>
 </tbody>
diff --git a/networking/v1alpha3/service_entry.pb.go b/networking/v1alpha3/service_entry.pb.go
index fec6204361..091d09a45a 100644
--- a/networking/v1alpha3/service_entry.pb.go
+++ b/networking/v1alpha3/service_entry.pb.go
@@ -213,7 +213,7 @@ func (ServiceEntry_Resolution) EnumDescriptor() ([]byte, []int) {
 //
 // The following example demonstrates the use of a dedicated egress gateway
 // through which all external service traffic is forwarded.
-// The 'export_to' field allows for control over the visibility of a service
+// The 'exportTo' field allows for control over the visibility of a service
 // declaration to other namespaces in the mesh. By default a service is exported
 // to all namespaces. The following example restricts the visibility to the
 // current namespace, represented by ".", so that it cannot be used by other
@@ -228,8 +228,8 @@ func (ServiceEntry_Resolution) EnumDescriptor() ([]byte, []int) {
 // spec:
 //   hosts:
 //   - httpbin.com
-//   export_to:
-//   - .
+//   exportTo:
+//   - "."
 //   location: MESH_EXTERNAL
 //   ports:
 //   - number: 80
@@ -274,7 +274,7 @@ func (ServiceEntry_Resolution) EnumDescriptor() ([]byte, []int) {
 // spec:
 //   hosts:
 //   - httpbin.com
-//   export_to:
+//   exportTo:
 //   - *
 //   gateways:
 //   - mesh
@@ -442,7 +442,6 @@ type ServiceEntry struct {
 	Resolution ServiceEntry_Resolution `protobuf:"varint,5,opt,name=resolution,proto3,enum=istio.networking.v1alpha3.ServiceEntry_Resolution" json:"resolution,omitempty"`
 	// One or more endpoints associated with the service.
 	Endpoints []*ServiceEntry_Endpoint `protobuf:"bytes,6,rep,name=endpoints" json:"endpoints,omitempty"`
-	// $hide_from_docs
 	// A list of namespaces to which this service is exported. Exporting a service
 	// allows it to used by sidecars, gateways and virtual services defined in
 	// other namespaces. This feature provides a mechanism for service owners
@@ -457,7 +456,7 @@ type ServiceEntry struct {
 	// defines an export to all namespaces.
 	//
 	// For a Kubernetes Service the equivalent effect can be achieved by setting
-	// the annotation "networking.istio.io/export_to" to a comma-separated list
+	// the annotation "networking.istio.io/exportTo" to a comma-separated list
 	// of namespace names.
 	ExportTo []string `protobuf:"bytes,7,rep,name=export_to,json=exportTo" json:"export_to,omitempty"`
 	// The list of subject alternate names allowed for workloads that
diff --git a/networking/v1alpha3/service_entry.proto b/networking/v1alpha3/service_entry.proto
index 94d4e92a42..1527586f47 100644
--- a/networking/v1alpha3/service_entry.proto
+++ b/networking/v1alpha3/service_entry.proto
@@ -134,7 +134,7 @@ option go_package = "istio.io/api/networking/v1alpha3";
 //
 // The following example demonstrates the use of a dedicated egress gateway
 // through which all external service traffic is forwarded.
-// The 'export_to' field allows for control over the visibility of a service
+// The 'exportTo' field allows for control over the visibility of a service
 // declaration to other namespaces in the mesh. By default a service is exported
 // to all namespaces. The following example restricts the visibility to the
 // current namespace, represented by ".", so that it cannot be used by other
@@ -149,8 +149,8 @@ option go_package = "istio.io/api/networking/v1alpha3";
 // spec:
 //   hosts:
 //   - httpbin.com
-//   export_to:
-//   - .
+//   exportTo:
+//   - "."
 //   location: MESH_EXTERNAL
 //   ports:
 //   - number: 80
@@ -195,7 +195,7 @@ option go_package = "istio.io/api/networking/v1alpha3";
 // spec:
 //   hosts:
 //   - httpbin.com
-//   export_to:
+//   exportTo:
 //   - *
 //   gateways:
 //   - mesh
@@ -470,7 +470,6 @@ message ServiceEntry {
   // One or more endpoints associated with the service.
   repeated Endpoint endpoints = 6;
 
-  // $hide_from_docs
   // A list of namespaces to which this service is exported. Exporting a service
   // allows it to used by sidecars, gateways and virtual services defined in
   // other namespaces. This feature provides a mechanism for service owners
@@ -485,7 +484,7 @@ message ServiceEntry {
   // defines an export to all namespaces.
   //
   // For a Kubernetes Service the equivalent effect can be achieved by setting
-  // the annotation "networking.istio.io/export_to" to a comma-separated list
+  // the annotation "networking.istio.io/exportTo" to a comma-separated list
   // of namespace names.
   repeated string export_to = 7;
 
diff --git a/networking/v1alpha3/virtual_service.pb.go b/networking/v1alpha3/virtual_service.pb.go
index 46799d78cf..1d854732ba 100644
--- a/networking/v1alpha3/virtual_service.pb.go
+++ b/networking/v1alpha3/virtual_service.pb.go
@@ -134,7 +134,6 @@ type VirtualService struct {
 	// be applied to any port that is not a HTTP or TLS port. The first rule
 	// matching an incoming request is used.
 	Tcp []*TCPRoute `protobuf:"bytes,4,rep,name=tcp" json:"tcp,omitempty"`
-	// $hide_from_docs
 	// A list of namespaces to which this virtual service is exported. Exporting a
 	// virtual service allows it to used by sidecars and gateways defined in
 	// other namespaces. This feature provides a mechanism for service owners
diff --git a/networking/v1alpha3/virtual_service.proto b/networking/v1alpha3/virtual_service.proto
index 925cd58bcd..d654c46cf3 100644
--- a/networking/v1alpha3/virtual_service.proto
+++ b/networking/v1alpha3/virtual_service.proto
@@ -176,7 +176,6 @@ message VirtualService {
   // matching an incoming request is used.
   repeated TCPRoute tcp = 4;
 
-  // $hide_from_docs
   // A list of namespaces to which this virtual service is exported. Exporting a
   // virtual service allows it to used by sidecars and gateways defined in
   // other namespaces. This feature provides a mechanism for service owners