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

add note about installing gateway api crds #1821

Merged
merged 1 commit into from
Aug 9, 2024
Merged

add note about installing gateway api crds #1821

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
7 changes: 7 additions & 0 deletions linkerd.io/content/2.16/features/httproute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,13 @@ documentation](../../reference/httproute/#linkerd-and-gateway-api-httproutes)
for details.
{{< /note >}}

If the Gateway API CRDs already exist in your cluster, then Linkerd must be
installed with the `--set enableHttpRoutes=false` flag during the
`linkerd install --crds` step or with the `enableHttpRoutes=false` Helm value
when installing the `linkerd-crds` Helm chart. This avoid conflicts by
instructing Linkerd to not install the Gateway API CRDs and instead rely on the
Gateway CRDs which already exist.

An HTTPRoute is a Kubernetes resource which attaches to a parent resource, such
as a [Service]. The HTTPRoute defines a set of rules which match HTTP requests
to that resource, based on parameters such as the request's path, method, and
Expand Down
11 changes: 9 additions & 2 deletions linkerd.io/content/2.16/reference/httproute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,15 @@ largely the same, the `policy.linkerd.io` HTTPRoute resource is an experimental
version that contains features not yet stabilized in the upstream
`gateway.networking.k8s.io` HTTPRoute resource, such as
[timeouts](#httproutetimeouts). Both the Linkerd and Gateway API resource
definitions may coexist within the same cluster, and both can be used to
configure policies for use with Linkerd.
definitions coexist within the same cluster, and both can be used to configure
policies for use with Linkerd.

If the Gateway API CRDs already exist in your cluster, then Linkerd must be
installed with the `--set enableHttpRoutes=false` flag during the
`linkerd install --crds` step or with the `enableHttpRoutes=false` Helm value
when installing the `linkerd-crds` Helm chart. This avoid conflicts by
instructing Linkerd to not install the Gateway API CRDs and instead rely on the
Gateway CRDs which already exist.

This documentation describes the `policy.linkerd.io` HTTPRoute resource. For a
similar description of the upstream Gateway API HTTPRoute resource, refer to the
Expand Down
Loading