Gateway API v1.6, released on 30 June and covered by Kubernetes on 3 August, moved TCPRoute and UDPRoute to the Standard channel at API version v1. This provides a shared model for describing layer 4 routing by port and protocol.
Why does this matter to an architect?
For services using raw TCP or UDP, it may be time to reassess dependence on extensions from one controller vendor. Check support in your specific implementation and the migration from older definitions separately: “Standard” does not mean every installation is ready to change.
Question for your project
Does the current controller support this version of the resources, and how will we migrate without interrupting existing connections?
Discuss this article
Share a constructive observation or an anonymised example. Comments are checked by AI before publication. Uncertain cases go to the moderator.