From a17f0ebe0cddbf7bd5730d4f42afcc113343bb49 Mon Sep 17 00:00:00 2001 From: Istio Automation Date: Thu, 21 Nov 2024 11:01:43 -0500 Subject: [PATCH] [release-1.24] add missing slash to fix docs path/lint (#3358) * add missing slash to fix docs path/lint * could swear I did this too --------- Co-authored-by: Craig Box --- networking/v1alpha3/sidecar.pb.go | 2 +- networking/v1alpha3/sidecar.pb.html | 2 +- networking/v1alpha3/sidecar.proto | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/networking/v1alpha3/sidecar.pb.go b/networking/v1alpha3/sidecar.pb.go index 7c3589b123b..dcbb746603c 100644 --- a/networking/v1alpha3/sidecar.pb.go +++ b/networking/v1alpha3/sidecar.pb.go @@ -38,7 +38,7 @@ // out unneeded configuration, to improve scalability of the mesh. // A common misunderstanding is that restricting the configuration amounts to *blocking* the traffic. // If requests are sent to destinations not included in the scoping, the traffic will be treated as -// [unmatched traffic](docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic), which is often still allowed. +// [unmatched traffic](/docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic), which is often still allowed. // The sidecar is not able to enforce an outbound traffic restriction (see [Egress Gateways](/docs/tasks/traffic-management/egress/egress-gateway/) for how to achieve this). // // Services and configuration in a mesh are organized into one or more diff --git a/networking/v1alpha3/sidecar.pb.html b/networking/v1alpha3/sidecar.pb.html index 25f3ec343d7..c6b0a48a85b 100644 --- a/networking/v1alpha3/sidecar.pb.html +++ b/networking/v1alpha3/sidecar.pb.html @@ -21,7 +21,7 @@ out unneeded configuration, to improve scalability of the mesh. A common misunderstanding is that restricting the configuration amounts to blocking the traffic. If requests are sent to destinations not included in the scoping, the traffic will be treated as -unmatched traffic, which is often still allowed. +unmatched traffic, which is often still allowed. The sidecar is not able to enforce an outbound traffic restriction (see Egress Gateways for how to achieve this).

Services and configuration in a mesh are organized into one or more namespaces (e.g., a Kubernetes namespace or a CF org/space). A Sidecar diff --git a/networking/v1alpha3/sidecar.proto b/networking/v1alpha3/sidecar.proto index 3b4bf7c072a..051cd27cf9a 100644 --- a/networking/v1alpha3/sidecar.proto +++ b/networking/v1alpha3/sidecar.proto @@ -39,7 +39,7 @@ import "networking/v1alpha3/virtual_service.proto"; // out unneeded configuration, to improve scalability of the mesh. // A common misunderstanding is that restricting the configuration amounts to *blocking* the traffic. // If requests are sent to destinations not included in the scoping, the traffic will be treated as -// [unmatched traffic](docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic), which is often still allowed. +// [unmatched traffic](/docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic), which is often still allowed. // The sidecar is not able to enforce an outbound traffic restriction (see [Egress Gateways](/docs/tasks/traffic-management/egress/egress-gateway/) for how to achieve this). // // Services and configuration in a mesh are organized into one or more