Skip to content
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: servicemeshinterface/smi-spec
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0f2fd356fc1269e8ca6653eca260d73454e0a733
Choose a base ref
..
head repository: servicemeshinterface/smi-spec
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: c70e90d97bb75c2e2d6386464495f1ca4f56759e
Choose a head ref
Showing with 1 addition and 1 deletion.
  1. +1 −1 apis/traffic-access/v1alpha4/traffic-access.md
2 changes: 1 addition & 1 deletion apis/traffic-access/v1alpha4/traffic-access.md
Original file line number Diff line number Diff line change
@@ -90,7 +90,7 @@ to workloads would overcomplicate the `TrafficTarget` manifest and its administr
A `TrafficTarget` associates a set of traffic definitions (rules) with a
service identity which is allocated to a group of pods. Access is controlled
via referenced [TrafficSpecs](/apis/traffic-specs/v1alpha4/traffic-specs.md)
and by a list of source service identities (via [`IdentityBinding`](#identitybinding)
and by a list of source service identities (via [`IdentityBinding`](#identitybinding)
or `ServiceAccount`). If a pod which holds the reference service identity makes
a call to the destination on one of the defined routes then access will be
allowed. Any pod which attempts to connect and is not in the defined list of