Two Houses, Both Alike in Dignity: Gateway API and MCS API

Gateway API and the MCS API are two pieces of your multicluster traffic management puzzle: Gateway API provides advanced routing capabilities and the MCS API provides cross cluster service discovery. These two Kubernetes native APIs are sponsored by SIG-Network and SIG-Multicluster, respectively. How can these two APIs work together? How have they evolved, separately and as part of a larger upstream initiative to make the multicluster experience feel native? Both APIs are CRD-based, and each SIG focused on standards over details, leaving implementers plenty of room; so how have users dealt with the challenges to discover, install, and maintain synergistic controllers? Finally, where do they fit with the larger ecosystem of service discovery solutions, including service meshes and vendor specific tooling? Another project, the GAMMA initiative, sits smack between all of these, seeking to unify the east-west traffic management puzzle along one coherent, standards-driven direction. Answering these questions and more, join us for a panel style discussion with representatives from the Gateway API project, MCS API project, and GAMMA initiative. Our panelists will speak from their experience both developing the upstream standard and actually implementing the APIs with different vendors.