Add starting implementation of Gateway API v1alpha2 #900
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
Renaming all Gateway API related identifiers to a distinct name that does not collide with the new version. This will allow us to process both v1alpha1 and v1alpha2 in the same controller, helping users to migrate from these two incompatible CRDs. In addition only listers and informers being used were maintained: gatewayclass, gateway and httproute. This is only an internal refactor, there is no change in the behavior.
jcmoraisjr
force-pushed
the
jm-gateway-v1alpha2
branch
from
a718769 to
38e5924
Compare
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.
Adds the new version of the spec alongside with v1alpha1, so users of the former version have a less harder way to migrate - this won't happen automatically.
Todo list: