Use Kubernetes Gateway API instead of Ingress! (TLS - Cert Manager - Istio - Prometheus)

preview_player
Показать описание

▬▬▬▬▬ Experience & Location 💼 ▬▬▬▬▬
► I’m a Senior Software Engineer at Juniper Networks (12+ years of experience)
► Located in San Francisco Bay Area, CA (US citizen)

▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ Related videos 👨‍🏫 ▬▬▬▬▬▬

▬▬▬▬▬▬▬ Source Code 📚 ▬▬▬▬▬▬▬

#Kubernetes #Istio #DevOps
Рекомендации по теме
Комментарии
Автор

This is outstandly brilant. Thank you for sharing Anton.

meron
Автор

Great tutorial. Do you have an example integrating authentication/authorization services into this workflow?

allenx-bay
Автор

Great job Anton! Thank you for always blessing us with your knowledge.
Pls I have a question; I recently migrated some of my Company's Saas applications in AWS from CLB to ALB. Our Google SSO stops working all of a sudden and can't sign us in. It brings output as; Api/Saml error. But whenever I migrate it back to CLB, it works. What could be the problem?

ladioladeni
Автор

Hope you can make a more detailed and step-by-step version, especially for novice learners like me. Thx

vitusyu
Автор

Between manifest and hlem, what you prefer to implement in production?

raypi
Автор

Nice video! Honestly this looks much more complicated than setting up an ingress 😅

valerianmp
Автор

How can we monitor requests with k8s gateway API and logging solution for requests?
In Ingress we have it done already.

Unholyknightzz
Автор

What about situations where one has only 1 IP addresses. Can 1 gateway be used to expose multiple applications? Awesome tutorial btw!

BernardBrenyah