Breaking Changes
Gateway API GRPCRoute
version v1alpha2
removal
Release v1.1
of the AWS Gateway API Controller is built against Gateway API v1.2
. The controller is also compatible with Gateway API v1.1
but not with v1.0
.
- Upgrade to
v1.2
of gateway API (#680)
We strongly recommend backing up your configuration as this transition particularly affects GRPCRoute
in the following ways:
- The controller requires either Gateway API
v1.1
orv1.2
to be installed. - If using Gateway API
v1.1
, existingGRPCRoutes
onv1alpha2
will automatically update to v1 when the controller reconciles them. - Alternatively, you can manually update your
GRPCRoute
versions. - Kubernetes will reject new
GRPCRoute
objects created usingv1alpha2
.
If you are upgrading to Gateway API v1.2
, you will need to take additional steps because v1alpha2
is no longer a valid version for GRPCRoute
objects. For detailed instructions, refer to the v1.2
Gateway API release notes.
To ensure a streamlined Gateway API migration, follow the guide to upgrade the controller from v.1.0.x to v1.1.y
Document Improvements
- Document updates for Gateway API v1.2 CRDs (#683)
- Upgrading to Gateway API
v1.2
Full Change log: v1.0.7...v1.1.0