Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor protocol-detection doc tweak #1892

Merged
merged 1 commit into from
Dec 4, 2024
+6 −6
Merged

Minor protocol-detection doc tweak #1892

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions linkerd.io/content/2-edge/features/protocol-detection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,9 +107,9 @@ provide will _replace_, not augment, the default list of opaque ports.

{{< note >}}
If you are using [authorization policies](../server-policy/), the `Server`'s
`proxyProtocol` field which can be used to control protocol detection behavior
and can be used instead of a Service annotation. Regardless, we suggest
annotating the Service object for clarity.
`proxyProtocol` field can be used to control protocol detection behavior
instead of a Service annotation. Regardless, we suggest annotating the
Service object for clarity.
{{< /note >}}

## Marking ports as skip ports
Expand Down
6 changes: 3 additions & 3 deletions linkerd.io/content/2.16/features/protocol-detection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,9 +107,9 @@ provide will _replace_, not augment, the default list of opaque ports.

{{< note >}}
If you are using [authorization policies](../server-policy/), the `Server`'s
`proxyProtocol` field which can be used to control protocol detection behavior
and can be used instead of a Service annotation. Regardless, we suggest
annotating the Service object for clarity.
`proxyProtocol` field can be used to control protocol detection behavior
instead of a Service annotation. Regardless, we suggest annotating the
Service object for clarity.
{{< /note >}}

## Marking ports as skip ports
Expand Down
Loading