diff --git a/networking/v1alpha3/destination_rule.proto b/networking/v1alpha3/destination_rule.proto index 5759ff50..334edf05 100644 --- a/networking/v1alpha3/destination_rule.proto +++ b/networking/v1alpha3/destination_rule.proto @@ -19,7 +19,7 @@ import "gogoproto/gogo.proto"; // $title: Destination Rule // $description: Configuration affecting load balancing, outlier detection, etc. -// $location: https://istio.io/docs/reference/config/networking/v1alpha3/destination-rule.html +// $location: https://istio.io/docs/reference/config/networking/v1alpha3/destination_rule.html // `DestinationRule` defines policies that apply to traffic intended for a // service after routing has occurred. These rules specify configuration @@ -99,7 +99,7 @@ message DestinationRule { // REQUIRED. The name of a service from the service registry. Service // names are looked up from the platform's service registry (e.g., // Kubernetes services, Consul services, etc.) and from the hosts - // declared by [ServiceEntries](/docs/reference/config/networking/v1alpha3/service-entry/#ServiceEntry). Rules defined for + // declared by [ServiceEntries](/docs/reference/config/networking/v1alpha3/service_entry/#ServiceEntry). Rules defined for // services that do not exist in the service registry will be ignored. // // *Note for Kubernetes users*: When short names are used (e.g. "reviews" @@ -177,7 +177,7 @@ message TrafficPolicy { // A subset of endpoints of a service. Subsets can be used for scenarios // like A/B testing, or routing to a specific version of a service. Refer -// to [VirtualService](/docs/reference/config/networking/v1alpha3/virtual-service/#VirtualService) documentation for examples of using +// to [VirtualService](/docs/reference/config/networking/v1alpha3/virtual_service/#VirtualService) documentation for examples of using // subsets in these scenarios. In addition, traffic policies defined at the // service-level can be overridden at a subset-level. The following rule // uses a round robin load balancing policy for all traffic going to a diff --git a/networking/v1alpha3/envoy_filter.proto b/networking/v1alpha3/envoy_filter.proto index 4b9d040c..a8824f27 100644 --- a/networking/v1alpha3/envoy_filter.proto +++ b/networking/v1alpha3/envoy_filter.proto @@ -18,7 +18,7 @@ import "google/protobuf/struct.proto"; // $title: Envoy Filter // $description: Configuration affecting insertion of custom envoy filters. -// $location: https://istio.io/docs/reference/config/networking/v1alpha3/envoy-filter.html +// $location: https://istio.io/docs/reference/config/networking/v1alpha3/envoy_filter.html // `EnvoyFilter` describes Envoy proxy-specific filters that can be used to // customize the Envoy proxy configuration generated by Istio networking diff --git a/networking/v1alpha3/service_entry.proto b/networking/v1alpha3/service_entry.proto index 0964ead5..25b72fad 100644 --- a/networking/v1alpha3/service_entry.proto +++ b/networking/v1alpha3/service_entry.proto @@ -18,7 +18,7 @@ import "networking/v1alpha3/gateway.proto"; // $title: Service Entry // $description: Configuration affecting service registry. -// $location: https://istio.io/docs/reference/config/networking/v1alpha3/service-entry.html +// $location: https://istio.io/docs/reference/config/networking/v1alpha3/service_entry.html // `ServiceEntry` enables adding additional entries into Istio's internal // service registry, so that auto-discovered services in the mesh can diff --git a/networking/v1alpha3/virtual_service.proto b/networking/v1alpha3/virtual_service.proto index 823adc02..4a09a7a4 100644 --- a/networking/v1alpha3/virtual_service.proto +++ b/networking/v1alpha3/virtual_service.proto @@ -19,7 +19,7 @@ import "google/protobuf/wrappers.proto"; // $title: Virtual Service // $description: Configuration affecting label/content routing, sni routing, etc. -// $location: https://istio.io/docs/reference/config/networking/v1alpha3/virtual-service.html +// $location: https://istio.io/docs/reference/config/networking/v1alpha3/virtual_service.html // Configuration affecting traffic routing. Here are a few terms useful to define // in the context of traffic routing. @@ -196,7 +196,7 @@ message VirtualService { // registry. Istio's service registry is composed of all the services found // in the platform's service registry (e.g., Kubernetes services, Consul // services), as well as services declared through the -// [ServiceEntry](/docs/reference/config/networking/v1alpha3/service-entry/#ServiceEntry) resource. +// [ServiceEntry](/docs/reference/config/networking/v1alpha3/service_entry/#ServiceEntry) resource. // // *Note for Kubernetes users*: When short names are used (e.g. "reviews" // instead of "reviews.default.svc.cluster.local"), Istio will interpret