Allows users to define GatewayClasses using any controller #12733
Conversation
This file contains hidden or 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
That is, we now look first at GatewayClass.spec.controllerName and only then at GatewayClass.metadata.name. We do not lose backwards compatibility unless someone did something pathological like using Envoy's controller with a class named 'agentgateway'. Signed-off-by: David L. Chandler <[email protected]>
github-actions
bot
added
kind/feature
|
/retest |
Signed-off-by: David L. Chandler <[email protected]>
lgadban
reviewed
Nov 3, 2025
…ame-not-gatewayclass-name-matters-more
Signed-off-by: David L. Chandler <[email protected]>
lgadban
reviewed
Nov 6, 2025
Signed-off-by: David L. Chandler <[email protected]>
…s pass Signed-off-by: David L. Chandler <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
That is, we now look first at GatewayClass.spec.controllerName and only then at GatewayClass.metadata.name.
We do not lose backwards compatibility unless someone did something pathological like using Envoy's controller with a class named 'agentgateway'.
Change Type
/kind new_feature
Changelog
Additional Notes