{"id":751,"date":"2024-03-01T00:00:00","date_gmt":"2024-02-29T21:00:00","guid":{"rendered":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/genel\/kubernetes-sirlari-iste-ipuclari\/"},"modified":"2026-10-06T03:13:30","modified_gmt":"2026-10-06T00:13:30","slug":"kubernetes-sirlari-iste-ipuclari","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/konteynerlar-kubernetes-docker\/kubernetes-sirlari-iste-ipuclari\/","title":{"rendered":"Kubernetes S\u0131rlar\u0131: \u0130\u015fte \u0130pu\u00e7lar\u0131"},"content":{"rendered":"
\n

Kubernetes\u2019te iyi hata inceleme, belirtileri do\u011fru katmana ay\u0131rmakla ba\u015flar. Pending, CrashLoopBackOff, ba\u011flant\u0131 hatas\u0131 veya yava\u015f yan\u0131t ayn\u0131 nedenle olu\u015fmaz. \u00d6nce ba\u011flam\u0131 ve kan\u0131t\u0131 kaydedin; yeniden ba\u015flatma gibi de\u011fi\u015fiklikler \u00f6nemli g\u00f6zlemleri ortadan kald\u0131rmadan sorunun kayna\u011f\u0131n\u0131 daralt\u0131n.<\/p>\n

\"\u00d6nce
Her ad\u0131m farkl\u0131 bir hipotezi s\u0131nar; i\u015flem sonucu sonraki ad\u0131m\u0131 belirler.
G\u00f6rseli b\u00fcy\u00fct \u2192<\/a><\/figcaption><\/figure>\n

Do\u011fru k\u00fcmeyi ve namespace\u2019i kontrol edin<\/h2>\n

Birden fazla ortamla \u00e7al\u0131\u015f\u0131yorsan\u0131z ilk ad\u0131m aktif context ve hedef namespace\u2019i do\u011frulamakt\u0131r. A\u015fa\u011f\u0131daki komutlar durumu incelemek i\u00e7indir; app<\/code> ve Pod ad\u0131n\u0131 kendi yetkili ortam\u0131n\u0131zla de\u011fi\u015ftirin. Eri\u015fim reddi al\u0131rsan\u0131z sorunu \u00e7\u00f6zmek i\u00e7in kendinize geli\u015fig\u00fczel k\u00fcme y\u00f6neticisi yetkisi vermeyin.<\/p>\n

kubectl config current-context\nkubectl get pods -n app\nkubectl describe pod POD_ADI -n app\nkubectl get events -n app --sort-by=.metadata.creationTimestamp<\/code><\/pre>\n
Event kay\u0131tlar\u0131n\u0131n saklama s\u00fcresi s\u0131n\u0131rl\u0131 olabilir. Sorunun ba\u015flang\u0131c\u0131n\u0131, son de\u011fi\u015fikli\u011fi ve tekrar s\u0131kl\u0131\u011f\u0131n\u0131 kaydedin. Tek bir anl\u0131k g\u00f6r\u00fcnt\u00fc aral\u0131kl\u0131 sorunu a\u00e7\u0131klamayabilir.<\/p>\n
Pending ile yeniden ba\u015flatma d\u00f6ng\u00fcs\u00fcn\u00fc ay\u0131r\u0131n<\/h2>\n
Pending durumunda zamanlama, kaynak talebi, node se\u00e7imi, taint\/toleration veya PVC ba\u011flama sorunlar\u0131 bulunabilir. Pod event\u2019leri zamanlay\u0131c\u0131n\u0131n gerek\u00e7esini g\u00f6sterir. Kaynak taleplerini rastgele d\u00fc\u015f\u00fcrmek yerine gereken kapasiteyi ve yerle\u015fim politikas\u0131n\u0131 inceleyin.<\/p>\n
CrashLoopBackOff, container\u2019\u0131n tekrarlayan ba\u015far\u0131s\u0131z ba\u015flang\u0131c\u0131na i\u015faret eder; tek ba\u015f\u0131na nedeni s\u00f6ylemez. Uygulama \u00e7\u0131k\u0131\u015f kodu, yap\u0131land\u0131rma, dosya izni ve ba\u011f\u0131ml\u0131l\u0131k hatalar\u0131n\u0131 loglarla birlikte de\u011ferlendirin. \u00d6nceki container \u00f6rne\u011finin logu yararl\u0131 olabilir:<\/p>\n
kubectl logs POD_ADI -n app -c CONTAINER_ADI\nkubectl logs POD_ADI -n app -c CONTAINER_ADI --previous<\/code><\/pre>\n
Loglar parola, token veya m\u00fc\u015fteri verisi i\u00e7erebilir; yaln\u0131z gerekli ve temizlenmi\u015f b\u00f6l\u00fcm\u00fc payla\u015f\u0131n. Pod\u2019u silmeden \u00f6nce hata ba\u011flam\u0131n\u0131 kaydedin.<\/p>\n
Probe ve kaynak s\u0131n\u0131rlar\u0131n\u0131 inceleyin<\/h2>\n
Readiness ba\u015far\u0131s\u0131zsa uygulama \u00e7al\u0131\u015f\u0131yor g\u00f6r\u00fcnse bile trafi\u011fe al\u0131nmayabilir. Liveness ba\u015far\u0131s\u0131zl\u0131\u011f\u0131 yeniden ba\u015flatmaya yol a\u00e7abilir; uygulaman\u0131n normal ba\u015flang\u0131\u00e7 s\u00fcresini tan\u0131mayan bir kontrol d\u00f6ng\u00fc olu\u015fturur. Yava\u015f ba\u015flayan uygulamalarda startup probe ihtiyac\u0131n\u0131 de\u011ferlendirin.<\/p>\n
OOMKilled, bellek s\u0131n\u0131r\u0131 veya sistem bask\u0131s\u0131yla ili\u015fkili olabilir; uygulaman\u0131n bellek davran\u0131\u015f\u0131n\u0131 ve node durumunu birlikte inceleyin. CPU throttling, limit ve talep aras\u0131ndaki ili\u015fkiyle de\u011ferlendirilmelidir. Yaln\u0131z limitleri kald\u0131rmak sorunun nedenini \u00e7\u00f6zmez ve kom\u015fu i\u015f y\u00fcklerini etkileyebilir.<\/p>\n
Service eri\u015fimini u\u00e7tan uca takip edin<\/h2>\n
Service se\u00e7icilerinin Pod etiketleriyle e\u015fle\u015fti\u011fini, hedef portun do\u011fru oldu\u011funu ve uygun endpoint\u2019lerin olu\u015ftu\u011funu kontrol edin. Ard\u0131ndan DNS \u00e7\u00f6z\u00fcmlemesini, a\u011f politikas\u0131n\u0131 ve uygulaman\u0131n dinledi\u011fi adresi inceleyin. Ingress veya gateway gibi d\u0131\u015f eri\u015fim katmanlar\u0131 ayr\u0131ca de\u011ferlendirilmelidir.<\/p>\n
NetworkPolicy kullan\u0131yorsan\u0131z a\u011f eklentisinin kurallar\u0131 uygulad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n. Ba\u011flant\u0131 sorunu i\u00e7in b\u00fct\u00fcn politikalar\u0131 kald\u0131rmak yerine hangi kaynak, hedef ve portun gerekli oldu\u011funu belirleyin. TLS hatas\u0131, ba\u011flant\u0131 reddi ve uygulama HTTP hatas\u0131 farkl\u0131 te\u015fhis yollar\u0131d\u0131r.<\/p>\n
D\u00fczeltmeyi ve sonucu kaydedin<\/h2>\n
Bir de\u011fi\u015fikli\u011fi k\u00fc\u00e7\u00fck kapsamda uygulay\u0131n ve beklenen sonucu \u00f6nceden tan\u0131mlay\u0131n. Yeni imaj, kaynak ayar\u0131 veya eri\u015fim kural\u0131n\u0131n etkisini kullan\u0131c\u0131 i\u015f ak\u0131\u015f\u0131yla do\u011frulay\u0131n. Da\u011f\u0131t\u0131m geri alma karar\u0131 verirken veritaban\u0131 \u015femas\u0131 ve d\u0131\u015f sistemlerdeki de\u011fi\u015fikliklerin otomatik geri al\u0131nmad\u0131\u011f\u0131n\u0131 hesaba kat\u0131n.<\/p>\n
Olay sonras\u0131 neden, etkilenen kapsam, uygulanan d\u00fczeltme ve erken uyar\u0131 f\u0131rsatlar\u0131n\u0131 kaydedin. Ayn\u0131 hatay\u0131 tekrar \u00f6nlemek i\u00e7in test veya alarm\u0131 ger\u00e7ek bulguya ba\u011flay\u0131n; yaln\u0131z Pod say\u0131s\u0131n\u0131 art\u0131rarak kal\u0131c\u0131 \u00e7\u00f6z\u00fcm elde edildi\u011fini varsaymay\u0131n.<\/p>\n
S\u0131k sorulan sorular<\/h2>\n
\n
CrashLoopBackOff bir Kubernetes hatas\u0131 m\u0131d\u0131r?<\/strong><\/dt>\n
\n
Bu durum yeniden ba\u015flayan container\u2019\u0131n belirtisidir. Uygulama, yap\u0131land\u0131rma, izin veya ba\u011f\u0131ml\u0131l\u0131k gibi nedenler event ve loglarla incelenmelidir.<\/p>\n<\/dd>\n
\u0130lk ad\u0131m Pod\u2019u silmek olmal\u0131 m\u0131?<\/strong><\/dt>\n
\n
Genellikle \u00f6nce kan\u0131t\u0131 toplamak daha yararl\u0131d\u0131r. Yeniden olu\u015fturma ge\u00e7ici belirtiyi kald\u0131rabilir fakat nedeni gizleyebilir; i\u015flemin uygulama etkisini de\u011ferlendirin.<\/p>\n<\/dd>\n<\/dl>\n
Sonraki ad\u0131m<\/h2>\n
Nesne ili\u015fkilerini temel Kubernetes kavramlar\u0131<\/a> ve tekrarlanan olaylar\u0131 i\u015fletim plan\u0131<\/a> ile birlikte ele al\u0131n.<\/p>\n
Kaynaklar<\/h2>\n
    \n
  1. Troubleshooting Applications | Kubernetes<\/a><\/li>\n
  2. Debug Running Pods | Kubernetes<\/a><\/li>\n
  3. Security Checklist | Kubernetes<\/a><\/li>\n
  4. kubectl get | Kubernetes<\/a><\/li>\n
  5. kubectl describe | Kubernetes<\/a><\/li>\n
  6. kubectl logs | Kubernetes<\/a><\/li>\n
  7. kubectl config current-context | Kubernetes<\/a><\/li>\n
  8. Liveness, Readiness, and Startup Probes | Kubernetes<\/a><\/li>\n
  9. Kubernetes \u2014 Pod ve container kaynak y\u00f6netimi, CPU ve bellek s\u0131n\u0131rlar\u0131<\/a><\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
    Kubernetes\u2019te iyi hata inceleme, belirtileri do\u011fru katmana ay\u0131rmakla ba\u015flar. Pending, CrashLoopBackOff, ba\u011flant\u0131 hatas\u0131 veya yava\u015f yan\u0131t ayn\u0131 nedenle olu\u015fmaz. \u00d6nce ba\u011flam\u0131 ve kan\u0131t\u0131 kaydedin; yeniden ba\u015flatma gibi de\u011fi\u015fiklikler \u00f6nemli g\u00f6zlemleri ortadan kald\u0131rmadan sorunun kayna\u011f\u0131n\u0131 daralt\u0131n. Her ad\u0131m farkl\u0131 bir hipotezi s\u0131nar; i\u015flem sonucu sonraki ad\u0131m\u0131 belirler.G\u00f6rseli b\u00fcy\u00fct \u2192 Do\u011fru k\u00fcmeyi ve namespace\u2019i kontrol edin Birden […]<\/p>\n","protected":false},"author":4,"featured_media":1432,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27,24,25],"tags":[35,92],"class_list":["post-751","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-konteynerlar-kubernetes-docker","category-bulut-danismanlik-hizmeti","category-buluta-genel-bakis","tag-kubernetes","tag-kubernetes-ile-bulut-yonetimi"],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/751","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=751"}],"version-history":[{"count":2,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/751\/revisions"}],"predecessor-version":[{"id":759,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/751\/revisions\/759"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/media\/1432"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/media?parent=751"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/categories?post=751"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/tags?post=751"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}