Should You Switch to the New Kubernetes Gateway API?

By Navendu Pottekkat

議題

Should You Switch to the New Kubernetes Gateway API?

TR212 [[ new Date( '2024-08-04 02:40:00+00:00' ).toLocaleDateString('ja', {year: 'numeric', month: '2-digit', day: '2-digit'}) ]] [[ new Date( '2024-08-04 02:40:00+00:00' ).toLocaleTimeString('zh-Hant', {hour12: false, hour: '2-digit', minute:'2-digit'}) ]] ~ [[ new Date( '2024-08-04 03:10:00+00:00' ).toLocaleTimeString('zh-Hant', {hour12: false, hour: '2-digit', minute:'2-digit'}) ]] 英文 English
加入行事曆 加入關注 加入關注 已關注

It has been some time since the Kubernetes Gateway API made its v1.0 release, signifying graduation to the generally available status for some of its key APIs.

When the Gateway API made its beta release a year ago, it did not make sense to switch to it because the API and its implementations were still in their infancy. Is that still the case?

In this talk, Navendu explores how the Gateway API evolved from the Ingress API and what users need to be aware of while choosing one over the other.

講者

Navendu Pottekkat

Navendu Pottekkat

Navendu Pottekkat is a maintainer of Apache APISIX. He is passionate about designing, developing, and deploying scalable, distributed systems. Navendu dedicates himself to helping new contributors to open source, mentoring through the Google Summer of Code and Linux Foundation Mentorship Program. He also writes and speaks about the cloud native ecosystem, sharing his experience in contributing to, building, scaling, and maintaining open source projects.

Kubernetes Community Day Taipei R8QDLH general (30mins)