Skip to content

[RS-2690] Doc OpenShift restriction of Gateway API CRDs #2205

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

Merged
merged 3 commits into from
Aug 20, 2025
Merged

[RS-2690] Doc OpenShift restriction of Gateway API CRDs #2205

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7414ecd
[RS-2690] Doc OpenShift restriction of Gateway API CRDs
nelljerram Jul 31, 2025
8d365db
Merge remote-tracking branch 'origin/main' into gapi-openshift
nelljerram Aug 19, 2025
f67b106
Improve presentation
nelljerram Aug 19, 2025
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
10 changes: 10 additions & 0 deletions calico-cloud/networking/gateway-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@
| TLSRoute | v1alpha2 |
| UDPRoute | v1alpha2 |

:::note

OpenShift 4.19 introduced [restrictions](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html-single/ingress_and_load_balancing/index#nw-ingress-gateway-api-overview_ingress-gateway-api) on which Gateway API CRDs can be installed.

Check failure on line 36 in calico-cloud/networking/gateway-api.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'CRDs'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'CRDs'?", "location": {"path": "calico-cloud/networking/gateway-api.mdx", "range": {"start": {"line": 36, "column": 236}}}, "severity": "ERROR"}

- The available Gateway API resources in OpenShift 4.19 are: `GatewayClass`, `Gateway`, `GRPCRoute`, `HTTPRoute` and `ReferenceGrant`.

- Other Gateway API resources, namely `BackendLBPolicy`, `BackendTLSPolicy`, `TCPRoute`, `TLSRoute` and `UDPRoute`, are not available in OpenShift 4.19.

:::

### Envoy Gateway

Several implementations of the Gateway API are available, one of which is the [Envoy Gateway](https://gateway.envoyproxy.io/). $[prodname] integrates the Envoy Gateway implementation in order to provide support for the Gateway API.
Expand Down
10 changes: 10 additions & 0 deletions calico-enterprise/networking/gateway-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@
| TLSRoute | v1alpha2 |
| UDPRoute | v1alpha2 |

:::note

OpenShift 4.19 introduced [restrictions](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html-single/ingress_and_load_balancing/index#nw-ingress-gateway-api-overview_ingress-gateway-api) on which Gateway API CRDs can be installed.

Check failure on line 36 in calico-enterprise/networking/gateway-api.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'CRDs'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'CRDs'?", "location": {"path": "calico-enterprise/networking/gateway-api.mdx", "range": {"start": {"line": 36, "column": 236}}}, "severity": "ERROR"}

- The available Gateway API resources in OpenShift 4.19 are: `GatewayClass`, `Gateway`, `GRPCRoute`, `HTTPRoute` and `ReferenceGrant`.

- Other Gateway API resources, namely `BackendLBPolicy`, `BackendTLSPolicy`, `TCPRoute`, `TLSRoute` and `UDPRoute`, are not available in OpenShift 4.19.

:::

### Envoy Gateway

Several implementations of the Gateway API are available, one of which is the [Envoy Gateway](https://gateway.envoyproxy.io/). $[prodname] integrates the Envoy Gateway implementation in order to provide support for the Gateway API.
Expand Down
10 changes: 10 additions & 0 deletions calico/networking/gateway-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@
| TLSRoute | v1alpha2 |
| UDPRoute | v1alpha2 |

:::note

OpenShift 4.19 introduced [restrictions](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html-single/ingress_and_load_balancing/index#nw-ingress-gateway-api-overview_ingress-gateway-api) on which Gateway API CRDs can be installed.

Check failure on line 36 in calico/networking/gateway-api.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'CRDs'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'CRDs'?", "location": {"path": "calico/networking/gateway-api.mdx", "range": {"start": {"line": 36, "column": 236}}}, "severity": "ERROR"}

- The available Gateway API resources in OpenShift 4.19 are: `GatewayClass`, `Gateway`, `GRPCRoute`, `HTTPRoute` and `ReferenceGrant`.

- Other Gateway API resources, namely `BackendLBPolicy`, `BackendTLSPolicy`, `TCPRoute`, `TLSRoute` and `UDPRoute`, are not available in OpenShift 4.19.

:::

### Envoy Gateway

Several implementations of the Gateway API are available, one of which is the [Envoy Gateway](https://gateway.envoyproxy.io/). $[prodname] integrates the Envoy Gateway implementation in order to provide support for the Gateway API.
Expand Down