{"id":36409,"date":"2025-12-16T00:22:10","date_gmt":"2025-12-15T21:22:10","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/"},"modified":"2025-12-16T00:22:10","modified_gmt":"2025-12-15T21:22:10","slug":"kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/","title":{"rendered":"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#8217;ten Gateway API&#8217;ye Ge\u00e7meliyiz?"},"content":{"rendered":"<p><title>No Downtime Migration from Ingress NGINX to Gateway on DOKS<\/title><br \/>\n<body><\/p>\n<p>Kubernetes ortamlar\u0131nda Ingress NGINX&#8217;ten Gateway API&#8217;ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.<\/p>\n<p>G\u00fcn\u00fcm\u00fcz\u00fcn h\u0131zla de\u011fi\u015fen dijital d\u00fcnyas\u0131nda, uygulamalar\u0131n kesintisiz \u00e7al\u0131\u015fmas\u0131 kritik bir \u00f6neme sahip. \u00d6zellikle Kubernetes gibi dinamik ortamlarda, a\u011f trafi\u011fini y\u00f6netmek ve y\u00f6nlendirmek, uygulaman\u0131n performans\u0131 ve kullan\u0131c\u0131 deneyimi \u00fczerinde do\u011frudan etkilidir. Geleneksel olarak, Kubernetes k\u00fcmelerinde d\u0131\u015f d\u00fcnyaya a\u00e7\u0131lan servisler i\u00e7in Ingress NGINX gibi \u00e7\u00f6z\u00fcmler yayg\u0131n olarak kullan\u0131ld\u0131. Ancak, mikroservis mimarilerinin yayg\u0131nla\u015fmas\u0131 ve a\u011f gereksinimlerinin karma\u015f\u0131kla\u015fmas\u0131yla birlikte, Ingress NGINX&#8217;in baz\u0131 s\u0131n\u0131rlamalar\u0131 ortaya \u00e7\u0131kmaya ba\u015flad\u0131. \u0130\u015fte tam bu noktada, Kubernetes Gateway API devreye giriyor ve daha esnek, geni\u015fletilebilir ve rol tabanl\u0131 bir a\u011f y\u00f6netimi yakla\u015f\u0131m\u0131 sunuyor. Bu makalede, DOKS \u00fczerinde \u00e7al\u0131\u015fan bir uygulaman\u0131n Ingress NGINX&#8217;ten Gateway API&#8217;ye nas\u0131l kesintisiz bir \u015fekilde ta\u015f\u0131naca\u011f\u0131n\u0131, ad\u0131m ad\u0131m stratejiler ve ger\u00e7ek d\u00fcnya senaryolar\u0131yla birlikte ele alaca\u011f\u0131z. Amac\u0131m\u0131z, bu ge\u00e7i\u015f s\u00fcrecini sizin i\u00e7in anla\u015f\u0131l\u0131r k\u0131lmak ve olas\u0131 zorluklar\u0131n \u00fcstesinden gelmenize yard\u0131mc\u0131 olmakt\u0131r. B\u00f6ylece, uygulamalar\u0131n\u0131z\u0131n eri\u015filebilirli\u011fini ve performans\u0131n\u0131 optimize ederken, modern a\u011f y\u00f6netiminin t\u00fcm avantajlar\u0131ndan faydalanabilirsiniz.<\/p>\n<h2>Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#8217;ten Gateway API&#8217;ye Ge\u00e7meliyiz?<\/h2>\n<p>Kubernetes ekosisteminde, d\u0131\u015far\u0131dan gelen trafi\u011fi k\u00fcme i\u00e7indeki servislere y\u00f6nlendirmek i\u00e7in uzun s\u00fcredir Ingress kaynaklar\u0131 kullan\u0131l\u0131yor. \u00d6zellikle Ingress NGINX, performans, esneklik ve zengin \u00f6zellik setleri sayesinde en pop\u00fcler Ingress kontrolc\u00fclerinden biri haline geldi. Ancak, mikroservis mimarilerinin karma\u015f\u0131kl\u0131\u011f\u0131 artt\u0131k\u00e7a ve farkl\u0131 ekiplerin a\u011f yap\u0131land\u0131rmalar\u0131 \u00fczerindeki beklentileri \u00e7e\u015fitlendik\u00e7e, Ingress&#8217;in tekil ve genellikle merkeziyet\u00e7i yap\u0131s\u0131 baz\u0131 zorluklar\u0131 beraberinde getirdi. \u00d6rne\u011fin, birden fazla ekibin ayn\u0131 Ingress kayna\u011f\u0131 \u00fczerinde \u00e7ak\u0131\u015fan kurallar tan\u0131mlamas\u0131 veya farkl\u0131 g\u00fcvenlik politikalar\u0131 uygulamak istemesi, y\u00f6netimsel bir karma\u015faya yol a\u00e7abiliyordu. Ayr\u0131ca, Ingress&#8217;in temel amac\u0131 HTTP\/HTTPS trafi\u011fini y\u00f6nlendirmek oldu\u011fundan, daha geli\u015fmi\u015f trafik y\u00f6netimi (a\u011f\u0131rl\u0131kl\u0131 y\u00f6nlendirme, header tabanl\u0131 kurallar, path rewrite gibi) veya TCP\/UDP gibi farkl\u0131 protokoller i\u00e7in ek \u00e7\u00f6z\u00fcmlere ihtiya\u00e7 duyuluyordu. Bu durum, \u00f6zellikle b\u00fcy\u00fck ve dinamik ortamlarda, a\u011f yap\u0131land\u0131rmas\u0131n\u0131n esnekli\u011fini ve \u00f6l\u00e7eklenebilirli\u011fini k\u0131s\u0131tl\u0131yordu.<\/p>\n<p>\u0130\u015fte bu noktada, Kubernetes Gateway API, a\u011f y\u00f6netimini modern bir perspektifle ele alarak bu s\u0131n\u0131rlamalar\u0131n \u00fcstesinden gelmeyi hedefliyor. Gateway API, Ingress&#8217;in aksine, a\u011f kaynaklar\u0131n\u0131 farkl\u0131 roller aras\u0131nda ay\u0131rarak daha yap\u0131sal ve sorumluluk odakl\u0131 bir yakla\u015f\u0131m sunar. Altyap\u0131 operat\u00f6rleri, GatewayClass ve Gateway kaynaklar\u0131n\u0131 tan\u0131mlayarak a\u011f altyap\u0131s\u0131n\u0131 y\u00f6netirken, uygulama geli\u015ftiricileri HTTPRoute, TCPRoute gibi kaynaklar\u0131 kullanarak kendi uygulamalar\u0131n\u0131n trafi\u011fini kontrol edebilirler. Bu rol tabanl\u0131 ayr\u0131m, hem g\u00fcvenli\u011fi art\u0131r\u0131r hem de ekiplerin kendi sorumluluk alanlar\u0131 i\u00e7inde daha \u00f6zerk hareket etmelerini sa\u011flar. \u00dcstelik, Gateway API&#8217;nin mod\u00fcler yap\u0131s\u0131, sadece HTTP\/HTTPS trafi\u011fiyle s\u0131n\u0131rl\u0131 kalmay\u0131p, TCP, UDP ve hatta TLS passthrough gibi farkl\u0131 protokolleri de destekleyerek \u00e7ok daha geni\u015f bir kullan\u0131m alan\u0131 sunar. Bu ge\u00e7i\u015f, sadece bir teknoloji de\u011fi\u015fikli\u011fi de\u011fil, ayn\u0131 zamanda ekipler aras\u0131 i\u015fbirli\u011fini kolayla\u015ft\u0131ran ve a\u011f operasyonlar\u0131n\u0131 daha verimli hale getiren stratejik bir ad\u0131md\u0131r. DOKS gibi y\u00f6netilen Kubernetes hizmetlerinde bu ge\u00e7i\u015fi yapmak, altyap\u0131 y\u00f6netim y\u00fck\u00fcn\u00fc azalt\u0131rken, Gateway API&#8217;nin sundu\u011fu geli\u015fmi\u015f \u00f6zelliklerle uygulamalar\u0131n\u0131z\u0131n potansiyelini tam olarak ortaya \u00e7\u0131karman\u0131z\u0131 sa\u011flar.<\/p>\n<h3>Ingress NGINX ve Gateway API: Temel Farklar Nelerdir?<\/h3>\n<p>Ingress NGINX ve Gateway API aras\u0131ndaki temel farklar\u0131 anlamak, ge\u00e7i\u015f karar\u0131n\u0131z\u0131 sa\u011flam temellere oturtmak i\u00e7in kritik \u00f6neme sahiptir. Ingress NGINX, ad\u0131ndan da anla\u015f\u0131laca\u011f\u0131 gibi, NGINX tabanl\u0131 bir Ingress kontrolc\u00fcs\u00fcd\u00fcd\u00fcr. Kubernetes&#8217;teki Ingress kayna\u011f\u0131, d\u0131\u015far\u0131dan gelen HTTP\/HTTPS trafi\u011fini k\u00fcme i\u00e7indeki servislere y\u00f6nlendirmek i\u00e7in bir dizi kural tan\u0131mlaman\u0131za olanak tan\u0131r. Genellikle, tek bir Ingress nesnesi, bir veya daha fazla hizmet i\u00e7in y\u00f6nlendirme kurallar\u0131n\u0131 i\u00e7erir. Bu yap\u0131, basit ve orta \u00f6l\u00e7ekli uygulamalar i\u00e7in olduk\u00e7a yeterli ve kolay anla\u015f\u0131l\u0131rd\u0131r. Ancak, daha karma\u015f\u0131k senaryolarda, \u00f6rne\u011fin ayn\u0131 host i\u00e7in farkl\u0131 yollar\u0131n farkl\u0131 g\u00fcvenlik politikalar\u0131 gerektirmesi veya farkl\u0131 ekiplerin ayn\u0131 Ingress nesnesini y\u00f6netmesi gerekti\u011finde, Ingress NGINX&#8217;in yetenekleri s\u0131n\u0131rl\u0131 kalabilir. Geli\u015fmi\u015f \u00f6zellikler i\u00e7in NGINX&#8217;e \u00f6zg\u00fc anotasyonlar kullanmak gerekebilir ki bu da ta\u015f\u0131nabilirlik ve standartla\u015fma a\u00e7\u0131s\u0131ndan baz\u0131 sorunlar yaratabilir.<\/p>\n<p>\u00d6te yandan, Gateway API, Kubernetes&#8217;te a\u011f y\u00f6netimini tamamen yeniden d\u00fc\u015f\u00fcnen, daha soyut ve geni\u015fletilebilir bir \u00e7er\u00e7eve sunar. Gateway API, tek bir Ingress nesnesi yerine bir dizi yeni API nesnesi tan\u0131t\u0131r: GatewayClass, Gateway, HTTPRoute, TCPRoute, TLSRoute ve UDPRoute. Bu yap\u0131land\u0131rma, &#8220;rol tabanl\u0131&#8221; bir yakla\u015f\u0131mla tasarlanm\u0131\u015ft\u0131r. Bu, altyap\u0131 operat\u00f6rlerinin (Platform Ekibi) GatewayClass ve Gateway kaynaklar\u0131n\u0131 kullanarak a\u011f altyap\u0131s\u0131n\u0131 (\u00f6rne\u011fin, bir y\u00fck dengeleyici veya bir proxy) tan\u0131mlay\u0131p y\u00f6netmesini, uygulama geli\u015ftiricilerinin (Uygulama Ekibi) ise HTTPRoute gibi kaynaklar\u0131 kullanarak kendi uygulamalar\u0131na gelen trafi\u011fi ba\u011f\u0131ms\u0131z bir \u015fekilde yap\u0131land\u0131rmas\u0131n\u0131 sa\u011flar. Bu ayr\u0131m, ekiplerin kendi sorumluluk alanlar\u0131na odaklanmas\u0131n\u0131 kolayla\u015ft\u0131r\u0131r, \u00e7ak\u0131\u015fmalar\u0131 azalt\u0131r ve daha g\u00fcvenli bir operasyon ortam\u0131 sunar. Ayr\u0131ca, Gateway API, Ingress&#8217;in \u00f6tesine ge\u00e7erek geli\u015fmi\u015f trafik y\u00f6netimi yetenekleri (a\u011f\u0131rl\u0131kl\u0131 trafik b\u00f6lme, header veya sorgu parametrelerine g\u00f6re y\u00f6nlendirme), farkl\u0131 protokoller i\u00e7in yerel destek ve politika ekleme noktalar\u0131 (policy attachment points) gibi \u00f6zellikler sunar. Bu, daha esnek, \u00f6l\u00e7eklenebilir ve gelece\u011fe d\u00f6n\u00fck bir a\u011f altyap\u0131s\u0131 olu\u015fturman\u0131za olanak tan\u0131r. DOKS gibi y\u00f6netilen Kubernetes hizmetlerinde bu API&#8217;yi kullanmak, bulut sa\u011flay\u0131c\u0131n\u0131z\u0131n entegrasyon yeteneklerinden faydalanarak daha g\u00fc\u00e7l\u00fc ve y\u00f6netilebilir bir a\u011f katman\u0131 olu\u015fturman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<h2>DOKS Ortam\u0131nda Kesintisiz Ge\u00e7i\u015f \u0130\u00e7in \u00d6n Haz\u0131rl\u0131klar Nas\u0131l Yap\u0131l\u0131r?<\/h2>\n<p>Ingress NGINX&#8217;ten Gateway API&#8217;ye kesintisiz bir ge\u00e7i\u015f s\u00fcreci planlarken, DOKS ortam\u0131nda do\u011fru \u00f6n haz\u0131rl\u0131klar\u0131 yapmak, projenin ba\u015far\u0131s\u0131 i\u00e7in hayati \u00f6neme sahiptir. \u0130lk ad\u0131m, mevcut Kubernetes k\u00fcmenizin ve ilgili ara\u00e7lar\u0131n\u0131z\u0131n g\u00fcncel oldu\u011fundan emin olmakt\u0131r. DOKS k\u00fcmenizin en son Kubernetes s\u00fcr\u00fcm\u00fcn\u00fc \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131ndan emin olun, \u00e7\u00fcnk\u00fc Gateway API&#8217;nin tam \u00f6zellik setini kullanabilmek i\u00e7in belirli bir Kubernetes s\u00fcr\u00fcm\u00fc (genellikle 1.22 ve \u00fczeri) gereklidir. Ayr\u0131ca, <code class=\"language-\">kubectl<\/code> ve <code class=\"language-\">helm<\/code> gibi komut sat\u0131r\u0131 ara\u00e7lar\u0131n\u0131z\u0131n da g\u00fcncel s\u00fcr\u00fcmlerini kullanman\u0131z, olas\u0131 uyumluluk sorunlar\u0131n\u0131 minimize edecektir.<\/p>\n<p>Bir sonraki \u00f6nemli ad\u0131m, mevcut Ingress NGINX yap\u0131land\u0131rman\u0131z\u0131 detayl\u0131 bir \u015fekilde analiz etmektir. Hangi servislerin hangi host ve path kurallar\u0131yla d\u0131\u015far\u0131ya a\u00e7\u0131ld\u0131\u011f\u0131, kullan\u0131lan TLS sertifikalar\u0131, uygulanan yeniden y\u00f6nlendirmeler, kimlik do\u011frulama ayarlar\u0131 ve NGINX&#8217;e \u00f6zg\u00fc anotasyonlar gibi t\u00fcm detaylar\u0131 belirlemeniz gerekmektedir. Bu analiz, mevcut Ingress kurallar\u0131n\u0131 Gateway API format\u0131na d\u00f6n\u00fc\u015ft\u00fcrmek i\u00e7in bir yol haritas\u0131 olu\u015fturman\u0131za yard\u0131mc\u0131 olacakt\u0131r. Karma\u015f\u0131k anotasyonlar veya \u00f6zel NGINX yap\u0131land\u0131rmalar\u0131 varsa, bunlar\u0131n Gateway API&#8217;de nas\u0131l kar\u015f\u0131l\u0131k bulaca\u011f\u0131n\u0131 veya ek politikalarla nas\u0131l uygulanaca\u011f\u0131n\u0131 ara\u015ft\u0131rman\u0131z gerekebilir.<\/p>\n<p>Gateway API&#8217;ye ge\u00e7i\u015f i\u00e7in bir Gateway kontrolc\u00fcs\u00fc kurman\u0131z gerekecektir. DigitalOcean, Contour veya NGINX Gateway Fabric gibi pop\u00fcler Gateway API implementasyonlar\u0131n\u0131 kullanabilirsiniz. Bu kontrolc\u00fcler, Gateway API kaynaklar\u0131n\u0131 okur ve temel al\u0131nan a\u011f altyap\u0131s\u0131n\u0131 (\u00f6rne\u011fin, bir DigitalOcean Load Balancer) buna g\u00f6re yap\u0131land\u0131r\u0131r. A\u015fa\u011f\u0131daki \u00f6rnekte, Gateway API CRD&#8217;lerinin k\u00fcmede mevcut olup olmad\u0131\u011f\u0131n\u0131 kontrol etme ve pop\u00fcler bir Gateway kontrolc\u00fcs\u00fc olan Contour&#8217;u Helm ile nas\u0131l kurabilece\u011finize dair ad\u0131mlar g\u00f6sterilmektedir:<\/p>\n<pre><code>\n# Gateway API CRD'lerinin k\u00fcmede olup olmad\u0131\u011f\u0131n\u0131 kontrol edin\nkubectl get crd | grep gateway.networking.k8s.io\n\n# E\u011fer CRD'ler eksikse, manuel olarak kurman\u0131z gerekebilir\n# Ancak genellikle Gateway kontrolc\u00fcs\u00fc kurulumu s\u0131ras\u0131nda otomatik olarak eklenirler.\n# \u00d6rnek: Contour i\u00e7in kurulum\nhelm repo add projectcontour https:\/\/projectcontour.io\/contour\/\nhelm repo update\nhelm install contour projectcontour\/contour --namespace projectcontour --create-namespace \\\n  --set envoy.service.type=LoadBalancer \\\n  --set contour.service.type=LoadBalancer\n  <\/code><\/pre>\n<p>Yukar\u0131daki komutlar, Contour&#8217;u DOKS k\u00fcmenize kurar ve Envoy proxy&#8217;lerini d\u0131\u015f d\u00fcnyaya a\u00e7mak i\u00e7in bir LoadBalancer hizmeti olu\u015fturur. Bu i\u015flem tamamland\u0131ktan sonra, k\u00fcmenizde Gateway API kaynaklar\u0131n\u0131 tan\u0131mlamaya ba\u015flayabilirsiniz. Mevcut Ingress kurallar\u0131n\u0131z\u0131 Gateway API&#8217;ye d\u00f6n\u00fc\u015ft\u00fcrmek i\u00e7in manuel \u00e7al\u0131\u015fma gerekecek olsa da, baz\u0131 topluluk ara\u00e7lar\u0131 veya \u00f6zel betikler bu s\u00fcreci h\u0131zland\u0131rman\u0131za yard\u0131mc\u0131 olabilir. \u00d6rne\u011fin, <code class=\"language-\">ingress2gateway<\/code> gibi ara\u00e7lar, basit Ingress kurallar\u0131n\u0131 Gateway API format\u0131na \u00e7evirebilir. Ancak, karma\u015f\u0131k senaryolarda detayl\u0131 bir inceleme ve manuel ayarlamalar genellikle ka\u00e7\u0131n\u0131lmazd\u0131r. Bu \u00f6n haz\u0131rl\u0131k a\u015famas\u0131, ge\u00e7i\u015fin sorunsuz ve kesintisiz olmas\u0131n\u0131 sa\u011flamak i\u00e7in temel bir ad\u0131md\u0131r.<\/p>\n<div class=\"uzman-ipucu\">\n<h3>Uzman \u0130pucu: Mevcut Ingress Yap\u0131land\u0131rmas\u0131n\u0131 Detayl\u0131ca Belgeleyin<\/h3>\n<p>Ge\u00e7i\u015fe ba\u015flamadan \u00f6nce, mevcut Ingress NGINX yap\u0131land\u0131rman\u0131z\u0131n t\u00fcm detaylar\u0131n\u0131 (hostlar, path&#8217;ler, TLS ayarlar\u0131, yeniden y\u00f6nlendirmeler, \u00f6zel NGINX anotasyonlar\u0131 vb.) titizlikle belgeleyin. Bu belge, Gateway API&#8217;ye ge\u00e7i\u015f s\u0131ras\u0131nda herhangi bir kural\u0131n atlanmamas\u0131n\u0131 veya yanl\u0131\u015f yap\u0131land\u0131r\u0131lmamas\u0131n\u0131 sa\u011flayacak bir referans noktas\u0131 g\u00f6revi g\u00f6recektir. Ayr\u0131ca, bu belgeleme, olas\u0131 sorun giderme s\u00fcre\u00e7lerinde de size yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<\/p><\/div>\n<h2>Ad\u0131m Ad\u0131m Migrasyon Stratejileri: S\u0131f\u0131r Kesinti Nas\u0131l Sa\u011flan\u0131r?<\/h2>\n<p>Kesintisiz bir migrasyon, mevcut sistemin \u00e7al\u0131\u015fmaya devam ederken yeni sistemin devreye al\u0131nmas\u0131n\u0131 ve trafi\u011fin a\u015famal\u0131 olarak y\u00f6nlendirilmesini gerektirir. Bu b\u00f6l\u00fcmde, DOKS \u00fczerinde Ingress NGINX&#8217;ten Gateway API&#8217;ye s\u0131f\u0131r kesintiyle ge\u00e7i\u015f yapman\u0131z\u0131 sa\u011flayacak iki temel stratejiyi inceleyece\u011fiz: Blue\/Green da\u011f\u0131t\u0131m ve Kanarya da\u011f\u0131t\u0131m modelleri. Her iki yakla\u015f\u0131m da kendi avantajlar\u0131na sahiptir ve senaryonuza en uygun olan\u0131 se\u00e7mek \u00f6nemlidir.<\/p>\n<h3>Blue\/Green Da\u011f\u0131t\u0131m Yakla\u015f\u0131m\u0131yla Ge\u00e7i\u015f Nas\u0131l Y\u00f6netilir?<\/h3>\n<p>Blue\/Green da\u011f\u0131t\u0131m, ad\u0131ndan da anla\u015f\u0131laca\u011f\u0131 gibi, iki tamamen ayr\u0131 ortam\u0131n (Blue &#8211; mevcut, Green &#8211; yeni) ayn\u0131 anda var oldu\u011fu bir stratejidir. Bu yakla\u015f\u0131mda, mevcut Ingress NGINX yap\u0131land\u0131rman\u0131z (Blue ortam) trafi\u011fi i\u015flemeye devam ederken, Gateway API tabanl\u0131 yeni a\u011f altyap\u0131n\u0131z\u0131 (Green ortam) paralel olarak kurar ve yap\u0131land\u0131r\u0131rs\u0131n\u0131z. Bu, yeni yap\u0131land\u0131rmay\u0131 tamamen test etme ve do\u011frulamadan sonra trafi\u011fi tek bir anahtar (genellikle DNS veya Load Balancer seviyesinde) ile yeni ortama y\u00f6nlendirme imkan\u0131 sunar.<\/p>\n<p>S\u00fcre\u00e7 \u015fu ad\u0131mlar\u0131 i\u00e7erir:<\/p>\n<ol>\n<li><strong>Mevcut Ortam\u0131 Koruyun:<\/strong> Ingress NGINX&#8217;iniz mevcut uygulamalar\u0131n\u0131za gelen trafi\u011fi y\u00f6nlendirmeye devam etsin. Bu, &#8220;Blue&#8221; ortam\u0131n\u0131zd\u0131r.<\/li>\n<li><strong>Yeni Gateway API Ortam\u0131n\u0131 Kurun:<\/strong> DOKS k\u00fcmenizde Gateway API kontrolc\u00fcs\u00fcn\u00fc kurun (\u00f6nceki b\u00f6l\u00fcmde anlat\u0131ld\u0131\u011f\u0131 gibi). Ard\u0131ndan, mevcut Ingress kurallar\u0131n\u0131z\u0131n kar\u015f\u0131l\u0131\u011f\u0131 olan Gateway ve HTTPRoute kaynaklar\u0131n\u0131 olu\u015fturun. Bu, &#8220;Green&#8221; ortam\u0131n\u0131zd\u0131r.<\/li>\n<li><strong>Test ve Do\u011frulama:<\/strong> Green ortam\u0131n\u0131zdaki t\u00fcm rotalar\u0131n ve servislerin beklenen \u015fekilde \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun. \u0130\u00e7 testler yap\u0131n, u\u00e7tan uca senaryolar\u0131 do\u011frulay\u0131n. Bu a\u015famada, Green ortam\u0131na d\u0131\u015far\u0131dan trafik gelmeyece\u011fi i\u00e7in herhangi bir kesinti riski yoktur.<\/li>\n<li><strong>Trafi\u011fi Y\u00f6nlendirme:<\/strong> T\u00fcm testler ba\u015far\u0131l\u0131 oldu\u011funda, trafi\u011fi Blue ortam\u0131ndan Green ortama y\u00f6nlendirme zaman\u0131 gelir. Bu genellikle DNS kay\u0131tlar\u0131n\u0131 g\u00fcncelleyerek (CNAME veya A kayd\u0131n\u0131 yeni Gateway&#8217;in Load Balancer IP&#8217;sine i\u015faret ederek) veya DigitalOcean Load Balancer ayarlar\u0131nda hedef grubu de\u011fi\u015ftirerek yap\u0131l\u0131r. Bu ad\u0131m, tek bir anahtar hareketiyle ger\u00e7ekle\u015fir.<\/li>\n<li><strong>G\u00f6zlemleme ve Geri Alma:<\/strong> Trafi\u011fi y\u00f6nlendirdikten sonra, yeni ortam\u0131 yak\u0131ndan izleyin. Performans metriklerini, hata oranlar\u0131n\u0131 ve loglar\u0131 kontrol edin. Herhangi bir sorun ortaya \u00e7\u0131karsa, DNS kayd\u0131n\u0131 veya Load Balancer ayarlar\u0131n\u0131 h\u0131zla eski Blue ortama geri \u00e7evirerek an\u0131nda geri alma (rollback) yapabilirsiniz.<\/li>\n<li><strong>Eski Ortam\u0131 Kald\u0131rma:<\/strong> Green ortam\u0131n\u0131n stabil \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan ve t\u00fcm trafi\u011fi ba\u015far\u0131yla i\u015fledi\u011finden emin olduktan sonra, eski Ingress NGINX kaynaklar\u0131n\u0131 ve kontrolc\u00fcs\u00fcn\u00fc g\u00fcvenli bir \u015fekilde kald\u0131rabilirsiniz.<\/li>\n<\/ol>\n<p>A\u015fa\u011f\u0131da, \u00f6rnek bir HTTPRoute tan\u0131m\u0131 bulunmaktad\u0131r:<\/p>\n<pre><code>\napiVersion: gateway.networking.k8s.io\/v1beta1\nkind: HTTPRoute\nmetadata:\n  name: my-app-route\n  namespace: default\nspec:\n  parentRefs:\n    - name: my-gateway # Bu, daha \u00f6nce tan\u0131mlad\u0131\u011f\u0131n\u0131z Gateway nesnesinin ad\u0131 olmal\u0131\n  hostnames:\n    - \"myapp.example.com\"\n  rules:\n    - matches:\n        - path:\n            type: Prefix\n            value: \/\n      backendRefs:\n        - name: my-app-service # Hedef servisinizin ad\u0131\n          port: 80\n  <\/code><\/pre>\n<h3>Kanarya Da\u011f\u0131t\u0131m Modeli ile Riskler Nas\u0131l Minimize Edilir?<\/h3>\n<p>Kanarya da\u011f\u0131t\u0131m modeli, Blue\/Green&#8217;e g\u00f6re daha kademeli bir ge\u00e7i\u015f sunar ve risk tolerans\u0131 daha d\u00fc\u015f\u00fck olan ortamlar i\u00e7in idealdir. Bu stratejide, trafi\u011fin sadece k\u00fc\u00e7\u00fck bir y\u00fczdesi yeni Gateway API ortam\u0131na y\u00f6nlendirilirken, ana trafik ak\u0131\u015f\u0131 hala mevcut Ingress NGINX taraf\u0131ndan i\u015flenir. Bu sayede, yeni yap\u0131land\u0131rman\u0131n ger\u00e7ek d\u00fcnya ko\u015fullar\u0131nda nas\u0131l performans g\u00f6sterdi\u011fini g\u00f6zlemleyebilir ve olas\u0131 sorunlar\u0131 b\u00fcy\u00fck bir kullan\u0131c\u0131 kitlesini etkilemeden tespit edebilirsiniz.<\/p>\n<p>S\u00fcre\u00e7 \u015fu ad\u0131mlar\u0131 i\u00e7erir:<\/p>\n<ol>\n<li><strong>Mevcut ve Yeni Ortamlar\u0131 Haz\u0131rlay\u0131n:<\/strong> Blue\/Green&#8217;de oldu\u011fu gibi, Ingress NGINX&#8217;iniz \u00e7al\u0131\u015fmaya devam ederken Gateway API kontrolc\u00fcs\u00fcn\u00fc kurun ve HTTPRoute kaynaklar\u0131n\u0131 tan\u0131mlay\u0131n.<\/li>\n<li><strong>A\u011f\u0131rl\u0131kl\u0131 Trafik Y\u00f6nlendirme:<\/strong> Anahtar nokta buradad\u0131r. Gateway API&#8217;nin geli\u015fmi\u015f trafik y\u00f6netimi yeteneklerini kullanarak, trafi\u011fin k\u00fc\u00e7\u00fck bir y\u00fczdesini (\u00f6rne\u011fin %5 veya %10) yeni Gateway API rotas\u0131na y\u00f6nlendirin. Bu, genellikle ayn\u0131 host i\u00e7in birden fazla HTTPRoute tan\u0131mlayarak veya Gateway&#8217;in kendisinde a\u011f\u0131rl\u0131kl\u0131 y\u00f6nlendirme kurallar\u0131 belirleyerek yap\u0131l\u0131r.<\/li>\n<li><strong>Kapsaml\u0131 G\u00f6zlemleme:<\/strong> Yeni Gateway \u00fczerinden ge\u00e7en k\u00fc\u00e7\u00fck trafik dilimini \u00e7ok yak\u0131ndan izleyin. Performans, hata oranlar\u0131, gecikme s\u00fcreleri ve kullan\u0131c\u0131 geri bildirimleri gibi metrikleri s\u00fcrekli kontrol edin. Herhangi bir anormallik durumunda, trafi\u011fi hemen eski Ingress NGINX&#8217;e geri y\u00f6nlendirebilirsiniz.<\/li>\n<li><strong>A\u015famal\u0131 Trafik Art\u0131\u015f\u0131:<\/strong> Yeni Gateway API ortam\u0131n\u0131n stabil ve sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olduktan sonra, trafi\u011fin y\u00fczdesini kademeli olarak art\u0131r\u0131n (\u00f6rne\u011fin %25, %50, %75). Her art\u0131\u015ftan sonra, sistemi bir s\u00fcre daha g\u00f6zlemleyerek herhangi bir regresyon olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<li><strong>Tam Ge\u00e7i\u015f ve Temizleme:<\/strong> Trafi\u011fin %100&#8217;\u00fc yeni Gateway API \u00fczerinden akmaya ba\u015flad\u0131\u011f\u0131nda ve sistemin stabil oldu\u011fu do\u011fruland\u0131\u011f\u0131nda, eski Ingress NGINX kaynaklar\u0131n\u0131 ve kontrolc\u00fcs\u00fcn\u00fc g\u00fcvenle kald\u0131rabilirsiniz.<\/li>\n<\/ol>\n<p>A\u015fa\u011f\u0131da, a\u011f\u0131rl\u0131kl\u0131 trafik y\u00f6nlendirmesi yapan bir HTTPRoute \u00f6rne\u011fi bulunmaktad\u0131r:<\/p>\n<pre><code>\napiVersion: gateway.networking.k8s.io\/v1beta1\nkind: HTTPRoute\nmetadata:\n  name: my-app-canary-route\n  namespace: default\nspec:\n  parentRefs:\n    - name: my-gateway\n  hostnames:\n    - \"myapp.example.com\"\n  rules:\n    - matches:\n        - path:\n            type: Prefix\n            value: \/\n      backendRefs:\n        - name: my-app-service-blue # Mevcut servis\n          port: 80\n          weight: 90 # Trafi\u011fin %90'\u0131 mevcut servise\n        - name: my-app-service-green # Yeni servis (Gateway API ile eri\u015filen)\n          port: 80\n          weight: 10 # Trafi\u011fin %10'u yeni servise\n  <\/code><\/pre>\n<p>Bu stratejiler, DOKS \u00fczerinde Ingress NGINX&#8217;ten Gateway API&#8217;ye ge\u00e7erken kesintiyi en aza indirmek i\u00e7in g\u00fc\u00e7l\u00fc ara\u00e7lard\u0131r. Uygulaman\u0131z\u0131n kritiklik seviyesine ve ekibinizin risk tolerans\u0131na g\u00f6re en uygun olan\u0131 se\u00e7erek, modern a\u011f y\u00f6netiminin avantajlar\u0131ndan sorunsuz bir \u015fekilde faydalanabilirsiniz.<\/p>\n<h2>Geli\u015fmi\u015f \u00d6zellikler ve Optimizasyon: Gateway API ile Neler Yap\u0131labilir?<\/h2>\n<p>Ingress NGINX&#8217;ten Gateway API&#8217;ye ge\u00e7i\u015f, sadece mevcut i\u015flevselli\u011fi korumakla kalmaz, ayn\u0131 zamanda Kubernetes a\u011f y\u00f6netiminde yepyeni bir yetenekler d\u00fcnyas\u0131n\u0131n kap\u0131lar\u0131n\u0131 aralar. Gateway API&#8217;nin mod\u00fcler ve geni\u015fletilebilir yap\u0131s\u0131, daha \u00f6nce karma\u015f\u0131k anotasyonlar veya ek ara\u00e7larla sa\u011flanan bir\u00e7ok \u00f6zelli\u011fi do\u011frudan ve standart bir \u015fekilde y\u00f6netmenize olanak tan\u0131r. Bu, \u00f6zellikle DOKS gibi y\u00f6netilen bir ortamda, operasyonel y\u00fck\u00fc azalt\u0131rken daha sofistike a\u011f politikalar\u0131 uygulaman\u0131z\u0131 sa\u011flar.<\/p>\n<p>Gateway API ile yapabilece\u011finiz geli\u015fmi\u015f \u00f6zelliklerden baz\u0131lar\u0131 \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>Geli\u015fmi\u015f Trafik Y\u00f6netimi:<\/strong>\n<ul>\n<li><strong>Header ve Sorgu Parametresi Tabanl\u0131 Y\u00f6nlendirme:<\/strong> Belirli HTTP ba\u015fl\u0131klar\u0131na veya sorgu parametrelerine sahip istekleri farkl\u0131 servislere y\u00f6nlendirebilirsiniz. Bu, A\/B testleri veya belirli kullan\u0131c\u0131 gruplar\u0131na \u00f6zel deneyimler sunmak i\u00e7in idealdir.<\/li>\n<li><strong>Path Rewrite ve Redirect:<\/strong> Gelen isteklerin URL yollar\u0131n\u0131 de\u011fi\u015ftirebilir veya kullan\u0131c\u0131lar\u0131 farkl\u0131 URL&#8217;lere y\u00f6nlendirebilirsiniz. Bu, API versiyonlama veya eski URL yap\u0131lar\u0131n\u0131 koruma senaryolar\u0131nda faydal\u0131d\u0131r.<\/li>\n<li><strong>A\u011f\u0131rl\u0131kl\u0131 Y\u00f6nlendirme (Weighted Routing):<\/strong> Kanarya da\u011f\u0131t\u0131m\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi, trafi\u011fi birden fazla backend servisi aras\u0131nda belirli oranlarda da\u011f\u0131tabilirsiniz. Bu, yeni \u00f6zelliklerin kademeli olarak devreye al\u0131nmas\u0131n\u0131 veya y\u00fck dengeleme stratejilerini optimize etmenizi sa\u011flar.<\/li>\n<\/ul>\n<\/li>\n<li><strong>G\u00fcvenlik Politikalar\u0131 ve Kimlik Do\u011frulama:<\/strong>\n<ul>\n<li><strong>TLS Sonland\u0131rma ve Sertifika Y\u00f6netimi:<\/strong> Gateway API, TLS sertifikalar\u0131n\u0131 y\u00f6netmek ve sonland\u0131rmak i\u00e7in yerel destek sunar. <code class=\"language-\">Kubernetes Secret<\/code> kaynaklar\u0131n\u0131 kullanarak sertifikalar\u0131n\u0131z\u0131 g\u00fcvenli bir \u015fekilde saklayabilir ve Gateway&#8217;e ba\u011flayabilirsiniz. Bu, Ingress NGINX&#8217;teki <code class=\"language-\">cert-manager<\/code> entegrasyonuna benzer, ancak daha standart bir yakla\u015f\u0131mla.<\/li>\n<li><strong>Kimlik Do\u011frulama ve Yetkilendirme (Authentication &#038; Authorization):<\/strong> Gateway API, do\u011frudan olmasa da, politika ekleme noktalar\u0131 (Policy Attachment Points) sayesinde harici kimlik do\u011frulama sistemleri (\u00f6rne\u011fin, OAuth2 proxy&#8217;leri veya JWT do\u011frulay\u0131c\u0131lar\u0131) ile entegrasyonu kolayla\u015ft\u0131r\u0131r. Bu, uygulaman\u0131z\u0131n \u00f6n\u00fcne g\u00fc\u00e7l\u00fc bir g\u00fcvenlik katman\u0131 eklemenizi sa\u011flar.<\/li>\n<li><strong>Web Uygulama G\u00fcvenlik Duvar\u0131 (WAF) Entegrasyonu:<\/strong> Baz\u0131 Gateway kontrolc\u00fcleri, WAF \u00e7\u00f6z\u00fcmleriyle entegrasyon yetenekleri sunar veya kendi b\u00fcnyelerinde temel WAF \u00f6zellikleri bar\u0131nd\u0131r\u0131r. Bu, k\u00f6t\u00fc niyetli sald\u0131r\u0131lara kar\u015f\u0131 ek bir koruma katman\u0131 sa\u011flar.<\/li>\n<\/ul>\n<\/li>\n<li><strong>G\u00f6zlemlenebilirlik ve Metrikler:<\/strong>\n<ul>\n<li>Gateway API kontrolc\u00fcleri genellikle Prometheus gibi izleme sistemleriyle entegrasyon i\u00e7in zengin metrikler sunar. Bu metrikler, trafi\u011fin nas\u0131l akt\u0131\u011f\u0131n\u0131, gecikme s\u00fcrelerini, hata oranlar\u0131n\u0131 ve genel performans\u0131 anlaman\u0131za yard\u0131mc\u0131 olur. Grafana gibi ara\u00e7larla bu metrikleri g\u00f6rselle\u015ftirerek, a\u011f altyap\u0131n\u0131z\u0131n sa\u011fl\u0131\u011f\u0131n\u0131 ve performans\u0131n\u0131 s\u00fcrekli olarak izleyebilirsiniz.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Geni\u015fletilebilirlik ve \u00d6zel Kaynaklar (Custom Resources):<\/strong>\n<ul>\n<li>Gateway API&#8217;nin belki de en g\u00fc\u00e7l\u00fc y\u00f6n\u00fc, geni\u015fletilebilirli\u011fidir. Operat\u00f6rler, kendi \u00f6zel kaynaklar\u0131n\u0131 (Custom Resources) tan\u0131mlayarak Gateway API&#8217;nin yeteneklerini kendi \u00f6zel ihtiya\u00e7lar\u0131na g\u00f6re geni\u015fletebilirler. Bu, belirli bir bulut sa\u011flay\u0131c\u0131s\u0131na \u00f6zg\u00fc \u00f6zelliklerin entegrasyonu veya \u00f6zel g\u00fcvenlik politikalar\u0131n\u0131n uygulanmas\u0131 gibi senaryolarda son derece faydal\u0131d\u0131r.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>A\u015fa\u011f\u0131da, TLS sonland\u0131rmal\u0131 bir Gateway ve HTTPRoute tan\u0131m\u0131 \u00f6rne\u011fi bulunmaktad\u0131r:<\/p>\n<pre><code>\n# Gateway nesnesi: TLS sertifikas\u0131n\u0131 kullanarak HTTPS trafi\u011fini sonland\u0131r\u0131r\napiVersion: gateway.networking.k8s.io\/v1beta1\nkind: Gateway\nmetadata:\n  name: my-secure-gateway\n  namespace: default\nspec:\n  gatewayClassName: contour # Kulland\u0131\u011f\u0131n\u0131z Gateway kontrolc\u00fcs\u00fcne g\u00f6re de\u011fi\u015fir\n  listeners:\n    - name: http\n      protocol: HTTP\n      port: 80\n      allowedRoutes:\n        namespaces:\n          from: Same # Sadece ayn\u0131 namespace'teki HTTPRoute'lara izin ver\n    - name: https\n      protocol: HTTPS\n      port: 443\n      tls:\n        mode: Terminate\n        certificateRefs:\n          - kind: Secret\n            name: my-tls-secret # TLS sertifikas\u0131n\u0131 i\u00e7eren Kubernetes Secret\n      allowedRoutes:\n        namespaces:\n          from: Same\n\n---\n# HTTPRoute nesnesi: HTTPS trafi\u011fini uygulamaya y\u00f6nlendirir\napiVersion: gateway.networking.k8s.io\/v1beta1\nkind: HTTPRoute\nmetadata:\n  name: my-app-secure-route\n  namespace: default\nspec:\n  parentRefs:\n    - name: my-secure-gateway\n  hostnames:\n    - \"secure.example.com\"\n  rules:\n    - matches:\n        - path:\n            type: Prefix\n            value: \/\n      backendRefs:\n        - name: my-app-service\n          port: 80 # Uygulama genellikle HTTP \u00fczerinden dinler, Gateway TLS'i sonland\u0131r\u0131r\n  <\/code><\/pre>\n<div class=\"uzman-ipucu\">\n<h3>Uzman \u0130pucu: PolicyAttachment Mekanizmalar\u0131n\u0131 Ke\u015ffedin<\/h3>\n<p>Gateway API, <code class=\"language-\">PolicyAttachment<\/code> ad\u0131 verilen bir mekanizma ile genel veya \u00f6zel politikalar\u0131n Gateway, HTTPRoute veya di\u011fer kaynaklara eklenmesine olanak tan\u0131r. Bu, WAF kurallar\u0131, rate limiting (oran s\u0131n\u0131rlama) veya IP k\u0131s\u0131tlamalar\u0131 gibi \u00f6zellikleri standart bir yolla uygulaman\u0131z\u0131 sa\u011flar. Kendi \u00f6zel politikalar\u0131n\u0131z\u0131 CRD olarak tan\u0131mlayabilir ve bunlar\u0131 Gateway API kaynaklar\u0131n\u0131za ba\u011flayarak a\u011f altyap\u0131n\u0131z\u0131n davran\u0131\u015f\u0131n\u0131 merkezi olarak y\u00f6netebilirsiniz. Bu, karma\u015f\u0131k senaryolarda y\u00f6netim y\u00fck\u00fcn\u00fc \u00f6nemli \u00f6l\u00e7\u00fcde azalt\u0131r.<\/p>\n<\/p><\/div>\n<p>Bu geli\u015fmi\u015f \u00f6zellikler, Gateway API&#8217;nin sadece bir Ingress alternatifi olmad\u0131\u011f\u0131n\u0131, ayn\u0131 zamanda Kubernetes ortamlar\u0131nda modern a\u011f y\u00f6netiminin gelece\u011fini temsil etti\u011fini g\u00f6stermektedir. DOKS \u00fczerinde bu yetenekleri kullanarak, uygulamalar\u0131n\u0131z i\u00e7in daha g\u00fcvenli, daha esnek ve daha performansl\u0131 bir a\u011f altyap\u0131s\u0131 olu\u015fturabilirsiniz.<\/p>\n<h2>Vaka \u00c7al\u0131\u015fmas\u0131: B\u00fcy\u00fck Bir E-Ticaret Platformunda Kesintisiz Ge\u00e7i\u015f Deneyimi<\/h2>\n<p>Bir e-ticaret platformunun kesintisiz \u00e7al\u0131\u015fmas\u0131, gelir ve m\u00fc\u015fteri memnuniyeti a\u00e7\u0131s\u0131ndan hayati \u00f6neme sahiptir. &#8220;ShopFlow&#8221; ad\u0131n\u0131 verdi\u011fimiz hayali bir e-ticaret platformu, DOKS \u00fczerinde \u00e7al\u0131\u015fan ve Ingress NGINX ile y\u00f6netilen, binlerce mikroservisten olu\u015fan karma\u015f\u0131k bir mimariye sahipti. Platformun mevcut Ingress NGINX yap\u0131land\u0131rmas\u0131, zamanla b\u00fcy\u00fcyen ve de\u011fi\u015fen ihtiya\u00e7lar\u0131 kar\u015f\u0131lamakta zorlan\u0131yordu. \u00d6zellikle, yeni \u00f6zelliklerin A\/B testi, farkl\u0131 b\u00f6lgelerdeki kullan\u0131c\u0131lara \u00f6zel i\u00e7erik sunumu ve API gateway olarak kullan\u0131lan Ingress&#8217;in performans sorunlar\u0131, ekibi yeni bir \u00e7\u00f6z\u00fcme y\u00f6neltti.<\/p>\n<p><strong>Mevcut Durum ve Sorunlar:<\/strong><\/p>\n<ul>\n<li><strong>Karma\u015f\u0131k Ingress Yap\u0131land\u0131rmalar\u0131:<\/strong> Y\u00fczlerce Ingress kural\u0131, farkl\u0131 ekipler taraf\u0131ndan y\u00f6netildi\u011fi i\u00e7in \u00e7ak\u0131\u015fmalar ve tutars\u0131zl\u0131klar ya\u015fan\u0131yordu.<\/li>\n<li><strong>Geli\u015fmi\u015f Trafik Y\u00f6netimi Eksikli\u011fi:<\/strong> Kanarya da\u011f\u0131t\u0131mlar\u0131 i\u00e7in manuel NGINX yap\u0131land\u0131rmalar\u0131 veya harici Load Balancer kurallar\u0131 gerekiyordu, bu da s\u00fcreci yava\u015flat\u0131yordu.<\/li>\n<li><strong>Performans ve \u00d6l\u00e7eklenebilirlik Endi\u015feleri:<\/strong> Yo\u011fun trafik zamanlar\u0131nda Ingress NGINX&#8217;in tek noktadan darbo\u011faz yaratma potansiyeli vard\u0131.<\/li>\n<li><strong>G\u00fcvenlik Politikalar\u0131n\u0131n Da\u011f\u0131n\u0131kl\u0131\u011f\u0131:<\/strong> WAF ve kimlik do\u011frulama gibi g\u00fcvenlik katmanlar\u0131, farkl\u0131 servisler ve Ingress kurallar\u0131 aras\u0131nda tutars\u0131z bir \u015fekilde uygulan\u0131yordu.<\/li>\n<\/ul>\n<p><strong>\u00c7\u00f6z\u00fcm: Gateway API&#8217;ye Kesintisiz Ge\u00e7i\u015f<\/strong><\/p>\n<p>ShopFlow ekibi, bu sorunlar\u0131n \u00fcstesinden gelmek ve gelecekteki b\u00fcy\u00fcme hedeflerini desteklemek i\u00e7in Gateway API&#8217;ye ge\u00e7i\u015f yapmaya karar verdi. DOKS&#8217;un y\u00f6netilen Kubernetes hizmeti olmas\u0131, altyap\u0131 kurulum ve y\u00f6netim y\u00fck\u00fcn\u00fc azaltt\u0131\u011f\u0131 i\u00e7in tercih edildi. Contour Gateway kontrolc\u00fcs\u00fc se\u00e7ildi, \u00e7\u00fcnk\u00fc geli\u015fmi\u015f trafik y\u00f6netimi yetenekleri ve DigitalOcean Load Balancer ile iyi entegrasyon sunuyordu.<\/p>\n<p><strong>Ge\u00e7i\u015f S\u00fcreci ve Strateji:<\/strong><\/p>\n<ol>\n<li><strong>Planlama ve Analiz:<\/strong> Mevcut Ingress NGINX yap\u0131land\u0131rmas\u0131 kapsaml\u0131 bir \u015fekilde analiz edildi. \u00d6zellikle, \u00f6zel NGINX anotasyonlar\u0131 ve <code class=\"language-\">lua<\/code> betikleriyle uygulanan geli\u015fmi\u015f kurallar, Gateway API&#8217;de nas\u0131l yeniden olu\u015fturulaca\u011f\u0131 detayl\u0131ca planland\u0131.<\/li>\n<li><strong>Pilot Ortam Kurulumu:<\/strong> Ayr\u0131 bir DOKS k\u00fcmesi \u00fczerinde Contour Gateway kontrolc\u00fcs\u00fc kuruldu ve Gateway API kaynaklar\u0131 (Gateway, HTTPRoute) pilot uygulamalar i\u00e7in yap\u0131land\u0131r\u0131ld\u0131. Bu ortamda yo\u011fun testler yap\u0131ld\u0131.<\/li>\n<li><strong>Kanarya Ge\u00e7i\u015fi Uygulamas\u0131:<\/strong> \u00dcretim ortam\u0131nda, ilk olarak kritik olmayan bir mikroservis i\u00e7in Kanarya da\u011f\u0131t\u0131m modeli uyguland\u0131. Mevcut Ingress NGINX trafi\u011fi i\u015flemeye devam ederken, trafi\u011fin %5&#8217;i yeni Gateway API \u00fczerinden y\u00f6nlendirildi.<\/li>\n<li><strong>A\u015famal\u0131 Trafik Art\u0131\u015f\u0131:<\/strong> %5&#8217;lik trafik dilimi birka\u00e7 g\u00fcn boyunca izlendi. Metrikler (gecikme, hata oranlar\u0131) ve loglar s\u00fcrekli kontrol edildi. Herhangi bir sorun tespit edilmedi\u011finde, trafik y\u00fczdesi a\u015famal\u0131 olarak %10, %25, %50 ve %100&#8217;e \u00e7\u0131kar\u0131ld\u0131. Bu s\u00fcre\u00e7, her art\u0131\u015ftan sonra dikkatli bir g\u00f6zlem s\u00fcresiyle birlikte yakla\u015f\u0131k iki hafta s\u00fcrd\u00fc.<\/li>\n<li><strong>Geli\u015fmi\u015f \u00d6zelliklerin Entegrasyonu:<\/strong> T\u00fcm trafik Gateway API \u00fczerinden akmaya ba\u015flad\u0131ktan sonra, ShopFlow ekibi Gateway API&#8217;nin sundu\u011fu geli\u015fmi\u015f \u00f6zellikleri kullanmaya ba\u015flad\u0131:\n<ul>\n<li><strong>A\/B Testleri:<\/strong> Yeni \u00fcr\u00fcn sayfalar\u0131 i\u00e7in header tabanl\u0131 y\u00f6nlendirme kurallar\u0131 ile A\/B testleri kolayca yap\u0131land\u0131r\u0131ld\u0131.<\/li>\n<li><strong>API Versiyonlama:<\/strong> Eski ve yeni API versiyonlar\u0131 i\u00e7in path rewrite kurallar\u0131 uyguland\u0131, bu da istemci uygulamalar\u0131nda herhangi bir de\u011fi\u015fiklik yapmadan API ge\u00e7i\u015flerini kolayla\u015ft\u0131rd\u0131.<\/li>\n<li><strong>Merkezi G\u00fcvenlik Politikalar\u0131:<\/strong> Rate limiting ve belirli IP aral\u0131klar\u0131ndan eri\u015fim k\u0131s\u0131tlamalar\u0131, Gateway seviyesinde uygulanarak g\u00fcvenlik y\u00f6netimi basitle\u015ftirildi.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Eski Ortam\u0131n Kald\u0131r\u0131lmas\u0131:<\/strong> T\u00fcm servisler Gateway API \u00fczerinden ba\u015far\u0131l\u0131 bir \u015fekilde \u00e7al\u0131\u015ft\u0131ktan ve stabilite sa\u011fland\u0131ktan sonra, Ingress NGINX kontrolc\u00fcs\u00fc ve ilgili kaynaklar \u00fcretim k\u00fcmesinden kald\u0131r\u0131ld\u0131.<\/li>\n<\/ol>\n<p><strong>Elde Edilen Faydalar:<\/strong><\/p>\n<ul>\n<li><strong>S\u0131f\u0131r Kesinti:<\/strong> T\u00fcm ge\u00e7i\u015f s\u00fcreci boyunca e-ticaret platformunda herhangi bir kesinti ya\u015fanmad\u0131.<\/li>\n<li><strong>Daha Esnek A\u011f Y\u00f6netimi:<\/strong> Ekipler, kendi HTTPRoute kaynaklar\u0131n\u0131 daha ba\u011f\u0131ms\u0131z bir \u015fekilde y\u00f6netebildi, bu da geli\u015ftirme h\u0131z\u0131n\u0131 art\u0131rd\u0131.<\/li>\n<li><strong>Geli\u015fmi\u015f Trafik Kontrol\u00fc:<\/strong> A\/B testleri ve kanarya da\u011f\u0131t\u0131mlar\u0131, Gateway API&#8217;nin yerel yetenekleriyle \u00e7ok daha kolay ve g\u00fcvenilir hale geldi.<\/li>\n<li><strong>Operasyonel Verimlilik:<\/strong> A\u011f yap\u0131land\u0131rmas\u0131 daha standart ve anla\u015f\u0131l\u0131r hale geldi, bu da sorun giderme ve bak\u0131m s\u00fcre\u00e7lerini kolayla\u015ft\u0131rd\u0131.<\/li>\n<li><strong>Gelece\u011fe Haz\u0131rl\u0131k:<\/strong> Gateway API&#8217;nin geni\u015fletilebilir yap\u0131s\u0131 sayesinde, platformun gelecekteki a\u011f gereksinimlerine daha kolay adapte olabilece\u011fi bir altyap\u0131 olu\u015fturuldu.<\/li>\n<\/ul>\n<p>ShopFlow&#8217;un bu vaka \u00e7al\u0131\u015fmas\u0131, DOKS \u00fczerinde Ingress NGINX&#8217;ten Gateway API&#8217;ye kesintisiz bir ge\u00e7i\u015fin sadece m\u00fcmk\u00fcn olmakla kalmay\u0131p, ayn\u0131 zamanda \u00f6nemli operasyonel ve teknik faydalar sa\u011flayabilece\u011fini a\u00e7\u0131k\u00e7a g\u00f6stermektedir. Do\u011fru planlama, a\u015famal\u0131 ge\u00e7i\u015f stratejileri ve dikkatli g\u00f6zlem ile her b\u00fcy\u00fckl\u00fckteki platform bu d\u00f6n\u00fc\u015f\u00fcm\u00fc ba\u015far\u0131yla tamamlayabilir.<\/p>\n<h2>Sonu\u00e7 ve S\u0131k\u00e7a Sorulan Sorular<\/h2>\n<p>Kubernetes ekosisteminde a\u011f y\u00f6netimi, uygulamalar\u0131n performans\u0131, g\u00fcvenli\u011fi ve \u00f6l\u00e7eklenebilirli\u011fi a\u00e7\u0131s\u0131ndan kritik bir rol oynamaktad\u0131r. Ingress NGINX, uzun y\u0131llar boyunca bu alanda \u00f6nemli bir \u00e7\u00f6z\u00fcm sunmu\u015f olsa da, modern mikroservis mimarilerinin getirdi\u011fi karma\u015f\u0131kl\u0131klar ve geli\u015fmi\u015f gereksinimler, Gateway API gibi daha sofistike \u00e7\u00f6z\u00fcmlere olan ihtiyac\u0131 ortaya \u00e7\u0131karm\u0131\u015ft\u0131r. Bu makalede, DigitalOcean Kubernetes (DOKS) \u00fczerinde Ingress NGINX&#8217;ten Gateway API&#8217;ye kesintisiz bir ge\u00e7i\u015fin nas\u0131l ger\u00e7ekle\u015ftirilece\u011fini ad\u0131m ad\u0131m inceledik. Blue\/Green ve Kanarya da\u011f\u0131t\u0131m stratejileri sayesinde, uygulamalar\u0131n\u0131z\u0131n s\u0131f\u0131r kesintiyle yeni ve daha esnek bir a\u011f altyap\u0131s\u0131na ta\u015f\u0131nabilece\u011fini g\u00f6rd\u00fck. Gateway API&#8217;nin sundu\u011fu geli\u015fmi\u015f trafik y\u00f6netimi, g\u00fcvenlik politikalar\u0131 ve geni\u015fletilebilirlik yetenekleri, ekiplerin daha verimli \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flarken, uygulamalar\u0131n gelecekteki ihtiya\u00e7lar\u0131na daha kolay adapte olmalar\u0131na olanak tan\u0131r. ShopFlow vaka \u00e7al\u0131\u015fmas\u0131, bu d\u00f6n\u00fc\u015f\u00fcm\u00fcn ger\u00e7ek d\u00fcnyadaki faydalar\u0131n\u0131 somut bir \u015fekilde ortaya koymu\u015ftur. Unutmay\u0131n, do\u011fru planlama, detayl\u0131 analiz ve a\u015famal\u0131 bir yakla\u015f\u0131m, bu t\u00fcr bir migrasyonun ba\u015far\u0131s\u0131 i\u00e7in anahtard\u0131r. Gateway API&#8217;ye ge\u00e7i\u015f, sadece bir teknoloji de\u011fi\u015fikli\u011fi de\u011fil, ayn\u0131 zamanda Kubernetes ortamlar\u0131n\u0131zda a\u011f y\u00f6netimini modernle\u015ftirme ve optimize etme yolunda stratejik bir ad\u0131md\u0131r.<\/p>\n<h3>S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n<ul>\n<li>\n<h4>Ingress NGINX&#8217;i tamamen kald\u0131rmal\u0131 m\u0131y\u0131m?<\/h4>\n<p>Ge\u00e7i\u015f tamamland\u0131ktan ve t\u00fcm trafi\u011fin Gateway API \u00fczerinden sorunsuz bir \u015fekilde akt\u0131\u011f\u0131ndan emin olduktan sonra Ingress NGINX kontrolc\u00fcs\u00fcn\u00fc ve ilgili Ingress kaynaklar\u0131n\u0131 kald\u0131rabilirsiniz. Ancak, ge\u00e7i\u015f s\u00fcreci boyunca her ikisini de paralel olarak \u00e7al\u0131\u015ft\u0131rmak ve Kanarya veya Blue\/Green stratejileriyle kademeli bir ge\u00e7i\u015f yapmak kesintiyi \u00f6nlemek i\u00e7in \u00f6nemlidir.<\/p>\n<\/li>\n<li>\n<h4>Gateway API hangi bulut sa\u011flay\u0131c\u0131lar\u0131nda destekleniyor?<\/h4>\n<p>Gateway API, Kubernetes&#8217;in a\u00e7\u0131k bir standart\u0131d\u0131r ve DigitalOcean (DOKS) dahil olmak \u00fczere bir\u00e7ok bulut sa\u011flay\u0131c\u0131s\u0131 ve Kubernetes da\u011f\u0131t\u0131m\u0131 taraf\u0131ndan desteklenmektedir. AWS (EKS), Google Cloud (GKE), Azure (AKS) gibi b\u00fcy\u00fck bulut sa\u011flay\u0131c\u0131lar\u0131 da kendi Gateway API implementasyonlar\u0131n\u0131 veya uyumlu kontrolc\u00fcleri sunmaktad\u0131r. Kullanaca\u011f\u0131n\u0131z kontrolc\u00fcye (\u00f6rne\u011fin, Contour, NGINX Gateway Fabric, Istio, Cilium) ba\u011fl\u0131 olarak entegrasyon detaylar\u0131 de\u011fi\u015febilir.<\/p>\n<\/li>\n<li>\n<h4>Ge\u00e7i\u015f s\u0131ras\u0131nda olas\u0131 sorunlar nelerdir ve nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr?<\/h4>\n<p>Olas\u0131 sorunlar aras\u0131nda yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f HTTPRoute kurallar\u0131, TLS sertifika sorunlar\u0131, eski Ingress anotasyonlar\u0131n\u0131n Gateway API&#8217;de kar\u015f\u0131l\u0131\u011f\u0131n\u0131n bulunmamas\u0131 veya performans darbo\u011fazlar\u0131 say\u0131labilir. Bu sorunlar\u0131 \u00e7\u00f6zmek i\u00e7in:<\/p>\n<ul>\n<li><code class=\"language-\">kubectl describe<\/code> ve <code class=\"language-\">kubectl logs<\/code> komutlar\u0131n\u0131 kullanarak Gateway API kaynaklar\u0131n\u0131 ve kontrolc\u00fc podlar\u0131n\u0131 detayl\u0131ca inceleyin.<\/li>\n<li>Gateway API dok\u00fcmantasyonunu ve se\u00e7ti\u011finiz kontrolc\u00fcn\u00fcn (\u00f6rn. Contour) belgelerini dikkatlice okuyun.<\/li>\n<li>\u00d6zellikle karma\u015f\u0131k Ingress anotasyonlar\u0131 i\u00e7in Gateway API&#8217;nin politika ekleme mekanizmalar\u0131n\u0131 ara\u015ft\u0131r\u0131n.<\/li>\n<li>G\u00f6zlemleme ara\u00e7lar\u0131 (Prometheus, Grafana) ile metrikleri izleyerek performans sorunlar\u0131n\u0131 erken tespit edin.<\/li>\n<\/ul>\n<\/li>\n<li>\n<h4>Performans a\u00e7\u0131s\u0131ndan Gateway API ne gibi avantajlar sunar?<\/h4>\n<p>Gateway API&#8217;nin kendisi do\u011frudan bir performans art\u0131\u015f\u0131 sa\u011flamaz; performans, kullan\u0131lan Gateway kontrolc\u00fcs\u00fcn\u00fcn (\u00f6rne\u011fin, Envoy tabanl\u0131 Contour veya NGINX tabanl\u0131 NGINX Gateway Fabric) performans\u0131na ba\u011fl\u0131d\u0131r. Ancak, Gateway API&#8217;nin rol tabanl\u0131 ve daha yap\u0131land\u0131r\u0131lm\u0131\u015f yap\u0131s\u0131, karma\u015f\u0131k konfig\u00fcrasyonlar\u0131n daha optimize edilmesine ve daha az hatayla y\u00f6netilmesine olanak tan\u0131r. Bu da dolayl\u0131 olarak daha stabil ve performansl\u0131 bir a\u011f katman\u0131 anlam\u0131na gelebilir. Ayr\u0131ca, geli\u015fmi\u015f trafik y\u00f6netimi yetenekleri sayesinde y\u00fck dengeleme daha verimli hale getirilebilir.<\/p>\n<\/li>\n<li>\n<h4>Hangi Gateway API implementasyonunu se\u00e7meliyim?<\/h4>\n<p>Se\u00e7im, ihtiya\u00e7lar\u0131n\u0131za ve tercihlerinize ba\u011fl\u0131d\u0131r. Pop\u00fcler implementasyonlar aras\u0131nda:<\/p>\n<ul>\n<li><strong>Contour:<\/strong> Envoy proxy \u00fczerine kurulu, hafif ve performansl\u0131. DigitalOcean ile iyi entegrasyonu vard\u0131r.<\/li>\n<li><strong>NGINX Gateway Fabric:<\/strong> NGINX&#8217;in g\u00fcc\u00fcn\u00fc Gateway API ile birle\u015ftirir, Ingress NGINX&#8217;ten ge\u00e7i\u015f yapanlar i\u00e7in tan\u0131d\u0131k olabilir.<\/li>\n<li><strong>Istio\/Linkerd (Service Meshler):<\/strong> E\u011fer zaten bir servis a\u011f\u0131 kullan\u0131yorsan\u0131z veya daha geli\u015fmi\u015f servisler aras\u0131 trafik y\u00f6netimi, g\u00fcvenlik ve g\u00f6zlemlenebilirlik \u00f6zelliklerine ihtiyac\u0131n\u0131z varsa, bu \u00e7\u00f6z\u00fcmler Gateway API ile entegre olabilir.<\/li>\n<\/ul>\n<p>        Se\u00e7im yaparken, performans, \u00f6zellik seti, topluluk deste\u011fi ve mevcut altyap\u0131n\u0131zla uyumlulu\u011fu g\u00f6z \u00f6n\u00fcnde bulundurmal\u0131s\u0131n\u0131z.\n      <\/p>\n<\/li>\n<\/ul>\n<p><\/body><\/p>\n","protected":false},"excerpt":{"rendered":"No Downtime Migration from Ingress NGINX to Gateway on DOKS Kubernetes ortamlar\u0131nda Ingress NGINX&#8217;ten Gateway API&#8217;ye kesintisiz ge\u00e7i\u015f&hellip;","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1328],"tags":[],"class_list":{"0":"post-36409","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-bash","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#039;ten Gateway API&#039;ye Ge\u00e7meliyiz?<\/title>\n<meta name=\"description\" content=\"Kubernetes ortamlar\u0131nda Ingress NGINX&#039;ten Gateway API&#039;ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#039;ten Gateway API&#039;ye Ge\u00e7meliyiz?\" \/>\n<meta property=\"og:description\" content=\"Kubernetes ortamlar\u0131nda Ingress NGINX&#039;ten Gateway API&#039;ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-12-15T21:22:10+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"25 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#8217;ten Gateway API&#8217;ye Ge\u00e7meliyiz?\",\"datePublished\":\"2025-12-15T21:22:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\"},\"wordCount\":4836,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Bash\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\",\"name\":\"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress'ten Gateway API'ye Ge\u00e7meliyiz?\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-12-15T21:22:10+00:00\",\"description\":\"Kubernetes ortamlar\u0131nda Ingress NGINX'ten Gateway API'ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#8217;ten Gateway API&#8217;ye Ge\u00e7meliyiz?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress'ten Gateway API'ye Ge\u00e7meliyiz?","description":"Kubernetes ortamlar\u0131nda Ingress NGINX'ten Gateway API'ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/","og_locale":"tr_TR","og_type":"article","og_title":"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress'ten Gateway API'ye Ge\u00e7meliyiz?","og_description":"Kubernetes ortamlar\u0131nda Ingress NGINX'ten Gateway API'ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.","og_url":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-12-15T21:22:10+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"25 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#8217;ten Gateway API&#8217;ye Ge\u00e7meliyiz?","datePublished":"2025-12-15T21:22:10+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/"},"wordCount":4836,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Bash"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/","url":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/","name":"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress'ten Gateway API'ye Ge\u00e7meliyiz?","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-12-15T21:22:10+00:00","description":"Kubernetes ortamlar\u0131nda Ingress NGINX'ten Gateway API'ye kesintisiz ge\u00e7i\u015f mi ar\u0131yorsunuz? DigitalOcean Kubernetes (DOKS) \u00fczerinde s\u0131f\u0131r kesintiyle modern a\u011f y\u00f6netimini nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedin, uygulamalar\u0131n\u0131z\u0131n s\u00fcreklili\u011fini garantileyin.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/kubernetes-ag-yonetiminde-donusum-neden-ingressten-gateway-apiye-gecmeliyiz\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Kubernetes A\u011f Y\u00f6netiminde D\u00f6n\u00fc\u015f\u00fcm: Neden Ingress&#8217;ten Gateway API&#8217;ye Ge\u00e7meliyiz?"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/36409","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=36409"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/36409\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=36409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=36409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=36409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}