Closed tao12345666333 closed 1 month ago
Thanks for reporting this, I definitely get that this behavior is confusing. This is actually intentional though - we made breaking changes (field renames) to BackendTLSPolicy in v1.1. That resulted in us bumping the version to v1alpha3, and dropping v1alpha2 since we do not want to maintain a conversion webhook. I added more information about this transition in https://github.com/kubernetes-sigs/gateway-api/pull/3084.
Thank you @robscott
Now that I understand the background. Do we need to include a note in the upgrade guide about how to fix this error?
That's a good idea, open to any suggestions for how to improve what we have there!
What happened:
When I upgraded my CRDs to v1.1, I encountered the following error.
What you expected to happen:
no error
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: