Add Gateway API CRDs #302
Closed
Add Gateway API CRDs #302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
peschmae
force-pushed
the
feat/gateway-api
branch
from
de8f084
to
5927973
Compare
|
Superseeded by #319 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As gatewayAPI has gone GA in late 2023, many ingress controllers have enabled or are enabling the use of HTTPRoute and other gatewayAPI resources. Also, as it is meant to replace ingress ressources, it would be great to have these resources as part of the CRD catalog.
The resources were created from the standard Channel (meaning it only includes
Gateway,GatewayClass,HttpRouteandReferenceGrant), and doesn't contain the experimental features likeGRPCRoute