{"id":745,"date":"2024-03-01T00:00:00","date_gmt":"2024-02-29T21:00:00","guid":{"rendered":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/genel\/kubernetes-hakkinda-bilmeniz-gerekenler\/"},"modified":"2026-10-06T03:13:30","modified_gmt":"2026-10-06T00:13:30","slug":"kubernetes-hakkinda-bilmeniz-gerekenler","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/konteynerlar-kubernetes-docker\/kubernetes-hakkinda-bilmeniz-gerekenler\/","title":{"rendered":"Kubernetes Hakk\u0131nda Bilmeniz Gerekenler"},"content":{"rendered":"
\n

Kubernetes\u2019i \u00f6\u011frenirken nesne adlar\u0131n\u0131 ezberlemekten \u00e7ok aralar\u0131ndaki ili\u015fkiyi anlamak yararl\u0131d\u0131r. Bir uygulaman\u0131n \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131, a\u011fa a\u00e7\u0131lmas\u0131, yap\u0131land\u0131rma almas\u0131 ve veriyi saklamas\u0131 farkl\u0131 kaynaklarla y\u00f6netilir. Bu rehber, ilk uygulama tasar\u0131m\u0131nda kar\u015f\u0131la\u015f\u0131lan kavramlar\u0131n g\u00f6revlerini ve s\u0131n\u0131rlar\u0131n\u0131 a\u00e7\u0131klar.<\/p>\n

\"Deployment
\u00c7al\u0131\u015ft\u0131rma, eri\u015fim, yap\u0131land\u0131rma ve veri ya\u015fam d\u00f6ng\u00fcleri ayr\u0131d\u0131r.
G\u00f6rseli b\u00fcy\u00fct \u2192<\/a><\/figcaption><\/figure>\n

Kontrol d\u00fczlemi ve worker node<\/h2>\n

Kontrol d\u00fczlemi API, zamanlama ve kontrol d\u00f6ng\u00fclerini y\u00f6netir. Worker node\u2019larda container \u00e7al\u0131\u015fma zaman\u0131 ve kubelet gibi bile\u015fenler i\u015f y\u00fcklerini y\u00fcr\u00fct\u00fcr. Bir node\u2019un haz\u0131r olmas\u0131, \u00fczerindeki b\u00fct\u00fcn uygulamalar\u0131n do\u011fru yan\u0131t verdi\u011fini g\u00f6stermez; altyap\u0131 ve uygulama sa\u011fl\u0131klar\u0131n\u0131 ayr\u0131 izleyin.<\/p>\n

Y\u00f6netilen bir hizmette bu katmanlar\u0131n baz\u0131lar\u0131 sa\u011flay\u0131c\u0131 taraf\u0131ndan i\u015fletilebilir. Hangi bile\u015fenin g\u00fcncellemesi, yede\u011fi ve eri\u015fim politikas\u0131n\u0131n kime ait oldu\u011funu \u00fcr\u00fcn\u00fcn kapsam\u0131ndan do\u011frulay\u0131n. Eri\u015febildi\u011finiz bir y\u00f6netim ekran\u0131 b\u00fct\u00fcn altyap\u0131 sorumlulu\u011funu devrald\u0131\u011f\u0131n\u0131z veya devretti\u011finiz anlam\u0131na gelmez.<\/p>\n

Pod ile Deployment farkl\u0131 g\u00f6revler \u00fcstlenir<\/h2>\n

Pod, birlikte yerle\u015ftirilen ve baz\u0131 kaynaklar\u0131 payla\u015fan container\u2019lar\u0131n \u00e7al\u0131\u015fma birimidir. Tek ba\u015f\u0131na kal\u0131c\u0131 kimlik veya disk garantisi de\u011fildir. Deployment, uygun i\u015f y\u00fckleri i\u00e7in Pod \u00f6rneklerinin istenen say\u0131s\u0131n\u0131 ve da\u011f\u0131t\u0131m durumunu y\u00f6netir; Pod yeniden olu\u015fturuldu\u011funda \u00f6nceki \u00f6rne\u011fin yerel dosyalar\u0131n\u0131n korunaca\u011f\u0131n\u0131 varsaymay\u0131n.<\/p>\n

StatefulSet, Job ve CronJob gibi kaynaklar farkl\u0131 ya\u015fam d\u00f6ng\u00fcleri i\u00e7indir. StatefulSet kullanmak veritaban\u0131n\u0131n yede\u011fini veya replikasyonunu otomatik kurmaz. \u00c7al\u0131\u015ft\u0131rma kayna\u011f\u0131n\u0131 uygulaman\u0131n durum ve tamamlanma davran\u0131\u015f\u0131na g\u00f6re se\u00e7in.<\/p>\n

Service ve d\u0131\u015f eri\u015fim<\/h2>\n

Service, uygun Podlara ula\u015fmak i\u00e7in kararl\u0131 bir eri\u015fim soyutlamas\u0131 sa\u011flar. Pod etiketleriyle Service se\u00e7icilerinin uyu\u015fmas\u0131 gerekir. D\u0131\u015f d\u00fcnyaya eri\u015fim i\u00e7in kullan\u0131lan ingress, gateway veya load balancer bile\u015fenleri ayr\u0131ca kurulmu\u015f ve yap\u0131land\u0131r\u0131lm\u0131\u015f olmal\u0131d\u0131r.<\/p>\n

Bir Service olu\u015fturmak TLS sertifikas\u0131, alan ad\u0131 veya b\u00fct\u00fcn d\u0131\u015f a\u011f kurallar\u0131n\u0131 kendili\u011finden tamamlamaz. DNS, sertifika, y\u00f6nlendirme ve uygulama haz\u0131r olma durumunu u\u00e7tan uca do\u011frulay\u0131n.<\/p>\n

ConfigMap, Secret ve namespace<\/h2>\n

ConfigMap gizli olmayan yap\u0131land\u0131rmay\u0131 ta\u015f\u0131r. Secret hassas de\u011ferler i\u00e7in ayr\u0131 bir kaynak t\u00fcr\u00fcd\u00fcr; base64 g\u00f6sterimi \u015fifreleme de\u011fildir. Secret\u2019a kimlerin eri\u015febildi\u011fi, API saklama korumas\u0131 ve de\u011ferlerin loglara yaz\u0131l\u0131p yaz\u0131lmad\u0131\u011f\u0131 ayr\u0131ca kontrol edilmelidir.<\/p>\n

Namespace kaynaklar\u0131 gruplamak ve y\u00f6netim kapsam\u0131n\u0131 d\u00fczenlemek i\u00e7in kullan\u0131l\u0131r. Tek ba\u015f\u0131na eksiksiz bir g\u00fcvenlik s\u0131n\u0131r\u0131 de\u011fildir. RBAC, kaynak kotalar\u0131 ve gereken a\u011f politikalar\u0131yla tamamlanmal\u0131d\u0131r. NetworkPolicy\u2019nin beklenen etkisi i\u00e7in a\u011f eklentisinin ilgili davran\u0131\u015f\u0131 destekledi\u011fini do\u011frulay\u0131n.<\/p>\n

Kaynak ve sa\u011fl\u0131k tan\u0131mlar\u0131<\/h2>\n

Requests, zamanlama i\u00e7in dikkate al\u0131nan kaynak talebini; limits ise ilgili kaynak t\u00fcr\u00fcne g\u00f6re uygulanabilen s\u0131n\u0131rlar\u0131 ifade eder. \u00c7ok d\u00fc\u015f\u00fck limit veya yanl\u0131\u015f talep, CPU k\u0131s\u0131tlamas\u0131 ya da bellek kaynakl\u0131 sonland\u0131rma gibi sorunlara yol a\u00e7abilir. De\u011ferleri ger\u00e7ek y\u00fck \u00f6l\u00e7\u00fcmlerinden t\u00fcretin.<\/p>\n

Readiness, uygulaman\u0131n trafi\u011fe haz\u0131r olup olmad\u0131\u011f\u0131n\u0131; liveness, gerekti\u011finde yeniden ba\u015flatma karar\u0131n\u0131; startup probe ise yava\u015f a\u00e7\u0131lan uygulamalar\u0131n ba\u015flang\u0131\u00e7 davran\u0131\u015f\u0131n\u0131 destekler. B\u00fct\u00fcn kontrolleri ayn\u0131 endpoint\u2019e k\u00f6r bi\u00e7imde ba\u011flamak yerine g\u00f6revlerini ay\u0131r\u0131n.<\/p>\n

Kal\u0131c\u0131 depolamay\u0131 ayr\u0131ca planlay\u0131n<\/h2>\n

PersistentVolumeClaim, depolama iste\u011fini ifade eder. StorageClass ve s\u00fcr\u00fcc\u00fc, bu iste\u011fin nas\u0131l kar\u015f\u0131lanaca\u011f\u0131n\u0131 belirler. Eri\u015fim modu, b\u00f6lge ba\u011f\u0131ml\u0131l\u0131\u011f\u0131, performans ve silme politikas\u0131 se\u00e7ilen altyap\u0131ya ba\u011fl\u0131d\u0131r. PVC\u2019nin ba\u011fl\u0131 olmas\u0131, uygulama verisinin yedeklendi\u011fi veya geri y\u00fcklenebilir oldu\u011fu anlam\u0131na gelmez.<\/p>\n

S\u0131k sorulan sorular<\/h2>\n
\n
Secret i\u00e7indeki base64 de\u011fer g\u00fcvenli \u015fifreleme midir?<\/strong><\/dt>\n
\n

Hay\u0131r. Kodlama ile \u015fifreleme farkl\u0131d\u0131r. Yetki, saklama korumas\u0131 ve uygulaman\u0131n de\u011feri kullanma bi\u00e7imi ayr\u0131ca y\u00f6netilmelidir.<\/p>\n<\/dd>\n

Namespace farkl\u0131 ekipleri tamamen izole eder mi?<\/strong><\/dt>\n
\n

Tek ba\u015f\u0131na de\u011fil. Yetkiler, a\u011f politikalar\u0131, kota ve gerekti\u011finde daha g\u00fc\u00e7l\u00fc s\u0131n\u0131rlar ayr\u0131ca tasarlanmal\u0131d\u0131r.<\/p>\n<\/dd>\n<\/dl>\n

Sonraki ad\u0131m<\/h2>\n

G\u00fcnl\u00fck i\u015fletimi Kubernetes y\u00f6netim rehberi<\/a> ve sorun incelemesini Kubernetes ipu\u00e7lar\u0131<\/a> \u00fczerinden ilerletin.<\/p>\n

Kaynaklar<\/h2>\n
    \n
  1. Overview | Kubernetes<\/a><\/li>\n
  2. Workloads | Kubernetes<\/a><\/li>\n
  3. Services, Load Balancing, and Networking | Kubernetes<\/a><\/li>\n
  4. Cluster Architecture | Kubernetes<\/a><\/li>\n
  5. Liveness, Readiness, and Startup Probes | Kubernetes<\/a><\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    Kubernetes\u2019i \u00f6\u011frenirken nesne adlar\u0131n\u0131 ezberlemekten \u00e7ok aralar\u0131ndaki ili\u015fkiyi anlamak yararl\u0131d\u0131r. Bir uygulaman\u0131n \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131, a\u011fa a\u00e7\u0131lmas\u0131, yap\u0131land\u0131rma almas\u0131 ve veriyi saklamas\u0131 farkl\u0131 kaynaklarla y\u00f6netilir. Bu rehber, ilk uygulama tasar\u0131m\u0131nda kar\u015f\u0131la\u015f\u0131lan kavramlar\u0131n g\u00f6revlerini ve s\u0131n\u0131rlar\u0131n\u0131 a\u00e7\u0131klar. \u00c7al\u0131\u015ft\u0131rma, eri\u015fim, yap\u0131land\u0131rma ve veri ya\u015fam d\u00f6ng\u00fcleri ayr\u0131d\u0131r.G\u00f6rseli b\u00fcy\u00fct \u2192 Kontrol d\u00fczlemi ve worker node Kontrol d\u00fczlemi API, zamanlama ve kontrol […]<\/p>\n","protected":false},"author":4,"featured_media":1428,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[91,35],"class_list":["post-745","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-konteynerlar-kubernetes-docker","tag-konteyner","tag-kubernetes"],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/comments?post=745"}],"version-history":[{"count":2,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/745\/revisions"}],"predecessor-version":[{"id":755,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/745\/revisions\/755"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/media\/1428"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/media?parent=745"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/categories?post=745"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/tags?post=745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}