{"id":8451,"date":"2025-01-03T00:00:16","date_gmt":"2025-01-02T21:00:16","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/kubernetes-aglari-ingress-ve-nodeport-ayrintili-anlatim\/"},"modified":"2025-01-03T00:00:16","modified_gmt":"2025-01-02T21:00:16","slug":"kubernetes-aglari-ingress-ve-nodeport-ayrintili-anlatim","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/kubernetes-aglari-ingress-ve-nodeport-ayrintili-anlatim\/","title":{"rendered":"Kubernetes A\u011flar\u0131: Ingress ve NodePort Ayr\u0131nt\u0131l\u0131 Anlat\u0131m"},"content":{"rendered":"

<\/p>\n

Kubernetes A\u011flar\u0131: Ingress ve NodePort Ayr\u0131nt\u0131l\u0131 Anlat\u0131m<\/p>\n

Merhaba, Fatih Soysal burada. Bu yaz\u0131da, Kubernetes mimarisinde s\u0131k\u00e7a kullan\u0131lan iki \u00f6nemli a\u011flama mekanizmas\u0131 olan Ingress ve NodePort’u ayr\u0131nt\u0131l\u0131 olarak inceleyece\u011fiz. \u00d6ncelikle her iki y\u00f6ntemin ne i\u015fe yarad\u0131\u011f\u0131n\u0131, daha sonra aralar\u0131ndaki temel farklar\u0131 ve hangi senaryolarda hangisini tercih etmeniz gerekti\u011fini ele alaca\u011f\u0131z. Ayr\u0131ca, konuyu daha iyi anlamak i\u00e7in pratik \u00f6rnekler ve kod par\u00e7alar\u0131 sunaca\u011f\u0131m.<\/p>\n

NodePort: Basit ve Do\u011frudan Eri\u015febilirlik<\/h2>\n

NodePort, Kubernetes cluster’\u0131n\u0131zdaki her bir node’un (sunucunun) belirli bir portunu, service’\u0131n\u0131z\u0131n backend’ine y\u00f6nlendirmenizi sa\u011flar. Bu sayede, cluster d\u0131\u015f\u0131ndan do\u011frudan node’lar\u0131n IP adresleri ve ilgili NodePort \u00fczerinden service’\u0131n\u0131za eri\u015febilirsiniz. NodePort’un kurulumu ve kullan\u0131m\u0131 olduk\u00e7a basittir. Ancak, k\u00fc\u00e7\u00fck \u00f6l\u00e7ekli projeler i\u00e7in uygun olsa da, b\u00fcy\u00fck ve karma\u015f\u0131k ortamlar i\u00e7in \u00f6l\u00e7eklenebilirlik ve g\u00fcvenlik a\u00e7\u0131s\u0131ndan dezavantajlar\u0131 olabilir. \u00d6rne\u011fin, her node’da ayn\u0131 portu kullanman\u0131z durumunda port \u00e7at\u0131\u015fmas\u0131 ya\u015fayabilirsiniz.<\/p>\n

\u0130\u015fte basit bir NodePort tan\u0131mlama \u00f6rne\u011fi:<\/p>\n


\napiVersion: v1
\nkind: Service
\nmetadata:
\n name: my-nodeport-service
\nspec:
\n type: NodePort
\n ports:
\n - port: 80
\n nodePort: 30000
\n targetPort: 8080
\n selector:
\n app: my-app
\n<\/code><\/p>\n

Bu \u00f6rnekte, my-app<\/code> label’\u0131na sahip pod’lara 8080<\/code> portundan eri\u015filecek ve bu trafik 30000<\/code> numaral\u0131 NodePort \u00fczerinden y\u00f6nlendirilecektir.<\/p>\n

Ingress: Geli\u015fmi\u015f Y\u00f6nlendirme ve G\u00fcvenlik<\/h2>\n

Ingress, birden fazla service’\u0131 y\u00f6netmek ve daha geli\u015fmi\u015f routing (y\u00f6nlendirme) yetenekleri sunmak i\u00e7in tasarlanm\u0131\u015ft\u0131r. Ingress controller’lar arac\u0131l\u0131\u011f\u0131yla, domain name’ler, SSL sertifikalar\u0131 ve di\u011fer geli\u015fmi\u015f konfig\u00fcrasyonlar ile service’lar\u0131n\u0131za eri\u015fimi y\u00f6netebilirsiniz. Ingress, NodePort’a g\u00f6re daha g\u00fcvenli ve \u00f6l\u00e7eklenebilir bir \u00e7\u00f6z\u00fcm sunar. \u00d6zellikle, birden fazla service’\u0131n\u0131z varsa ve bunlara d\u0131\u015far\u0131dan g\u00fcvenli bir \u015fekilde eri\u015fim sa\u011flamak istiyorsan\u0131z, Ingress ideal bir se\u00e7enektir.<\/p>\n

Ingress kullanman\u0131n avantajlar\u0131ndan baz\u0131lar\u0131 \u015funlard\u0131r: <\/p>\n