Implementation Guidelines: Document Version Skew Between Implementations and CRDs #2077
Labels
kind/documentation
Categorizes issue or PR as related to documentation.
release-blocker
MUST be completed to complete the milestone
Milestone
What would you like to be added:
Update our Implementation Guidelines documentation to document what implementations should do when Gateway API CRDs are newer or older than expected.
Why this is needed:
As we release more versions of Gateway API and more implementations of the API are available, version skew is going to be increasingly common. This will be especially problematic when new features are added to the CRDs but one or more implementations in the cluster is not aware of them.
The text was updated successfully, but these errors were encountered: