Переходим с Ingress на Gateway API

Subscribe to our channel here and on Telegram at https://t.me/meetups_evrone to stay up to date with future meetups and never miss a useful talk! This talk provides an overview and analysis of the various benefits and capabilities offered by the Gateway API. We'll cover the key reasons to consider migrating from Ingress to the Gateway API, as well as specific examples and scenarios where the Gateway API can be particularly useful and effective, and when it's best to stick with the older, more stable Ingress API. Alexander Kirillov / Evrone 00:00 Introduction 00:58 How traffic flows in Kubernetes 01:56 Example of an Ingress entity 02:40 What does an Ingress Controller provide? 03:24 Nuances of an Ingress Controller 04:20 Kubernetes Gateway API 05:48 Gateway API Concepts 06:23 How the Gateway API can be divided into layers and role models 06:56 GatewayClass 07:18 HTTP Gateway 07:49 HTTPRoute 08:25 Separation at different levels 09:37 New deployment patterns 10:48 How to migrate to the new API? 11:44 Step 1: Define Gateway 12:28 Step 2: Define HTTPRoutes 12:57 Step 3: Configure TLS Redirect 13:36 Ingress to Gateway 14:10 So, should I migrate or not?