Skip to content

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

Merged
ctauchen merged 3 commits into
tigera:mainfrom
nelljerram:gapi-openshift
Aug 20, 2025
Merged

ctauchen merged 3 commits into
tigera:mainfrom
nelljerram:gapi-openshift

Conversation

@nelljerram

Copy link
Copy Markdown
Member

No description provided.

@nelljerram
nelljerram requested a review from a team as a code owner July 31, 2025 17:29
@netlify

netlify Bot commented Jul 31, 2025 •

Copy link
Copy Markdown

✅ Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit f67b106
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/68a45b7635bf7c0008bf4c43
😎 Deploy Preview https://deploy-preview-2205--calico-docs-preview-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 31, 2025 •

Copy link
Copy Markdown

✅ Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit f67b106
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/68a45b76c1cd5d0008eed008
😎 Deploy Preview https://deploy-preview-2205--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 25 (no change from production)
Accessibility: 90 (no change from production)
Best Practices: 83 (🔴 down 9 from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@ctauchen

Copy link
Copy Markdown
Collaborator

@nelljerram Thanks for this. A few questions:

  • Are these CRDs unrestricted for earlier versions? Like 4.18?
  • Do we have an idea of what happens for upcoming versions, like 4.20?

@nelljerram

Copy link
Copy Markdown
Member Author

@ctauchen

  • Yes
  • No

I have tried to avoid creating a maintenance burden here - i.e. to write something that has a chance of remaining true when future versions come out. But perhaps that can be done in a better way; please LMK your thoughts.

Comment thread calico-cloud/networking/gateway-api.mdx Outdated

:::note

Some versions of OpenShift (currently just 4.19) restrict the Gateway API CRDs that may be installed: only `GatewayClass`, `Gateway`, `GRPCRoute`, `HTTPRoute` and `ReferenceGrant`. In clusters with those OpenShift versions the `BackendLBPolicy`, `BackendTLSPolicy`, `TCPRoute`, `TLSRoute` and `UDPRoute` APIs will not be available.

@ctauchen ctauchen Aug 13, 2025 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like this?

:::note
OpenShift 4.19 introduced restrictions for which the Gateway API CRDs can be installed. This change means that certain APIs are unavailable, a departure from OpenShift 4.18 and earlier, which provided full access to all CRDs.

This table shows which Gateway API CRDs are available for each OpenShift version.

| Gateway API CRD | OpenShift 4.18 and lower | OpenShift 4.19 |
| :--- | :--- | :--- |
| `GatewayClass` | ✅ Available | ✅ Available |
| `Gateway` | ✅ Available | ✅ Available |
| `GRPCRoute` | ✅ Available | ✅ Available |
| `HTTPRoute` | ✅ Available | ✅ Available |
| `ReferenceGrant` | ✅ Available | ✅ Available |
| `BackendLBPolicy` | ✅ Available | ❌ Not available |
| `BackendTLSPolicy` | ✅ Available | ❌ Not available |
| `TCPRoute` | ✅ Available | ❌ Not available |
| `TLSRoute` | ✅ Available | ❌ Not available |
| `UDPRoute` | ✅ Available | ❌ Not available |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there's an OpenShift docs page that lists these, best would be to point there. I haven't found one yet.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is on this topic - WDYT?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like this?

For me the table is a bit overkill - I feel it will make the page as a whole heavier and give undeserved prominence to OpenShift's choices. But I see a little merit in listing the resources separately from the narrative. Perhaps a good compromise would be a bulleted form like:

  • Available in OpenShift 4.19: GatewayClass, Gateway, GRPCRoute, HTTPRoute and ReferenceGrant.
  • Not available in OpenShift 4.19: BackendLBPolicy, BackendTLSPolicy, TCPRoute, TLSRoute and UDPRoute.

As regards the other wording changes in the narrative, I don't feel that any of them are big wins - but happy to defer to you if you feel strongly that they are.

@ctauchen ctauchen Aug 19, 2025 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough, let's try something like that.

I suggest we link to this OS Gateway API Overview: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html-single/ingress_and_load_balancing/index#nw-ingress-gateway-api-overview_ingress-gateway-api

It lists the resources that are available, and will likely be updated to include expanded functionality in future versions.

@nelljerram

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ctauchen , I've pushed an updating commit. Please take another look when you have time.

@ctauchen

Copy link
Copy Markdown
Collaborator

LGTM, merging. Thanks for this!

@ctauchen
ctauchen merged commit 8b3f592 into tigera:main Aug 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants