{"id":69,"date":"2026-10-24T16:20:00","date_gmt":"2026-10-24T16:20:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/24\/kubernetes-graceful-shutdown-readiness\/"},"modified":"2026-10-24T16:20:00","modified_gmt":"2026-10-24T16:20:00","slug":"kubernetes-graceful-shutdown-readiness","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/24\/kubernetes-graceful-shutdown-readiness\/","title":{"rendered":"Kubernetes&#8217;te Deploy S\u0131ras\u0131nda Neden 502 Al\u0131yoruz? Graceful Shutdown"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Rolling update ile deploy yap\u0131yoruz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yeni pod&#8217;lar aya\u011fa kalk\u0131yor, eskiler kapan\u0131yor. Teoride hi\u00e7bir istek kaybolmamal\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama monitoring ekran\u0131nda her deploy s\u0131ras\u0131nda k\u00fc\u00e7\u00fck bir 502 ve 503 s\u0131\u00e7ramas\u0131 g\u00f6r\u00fcn\u00fcyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Birka\u00e7 istek. Birka\u00e7 saniye.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c7o\u011fu ekip bunu kabul edip ge\u00e7iyor. Ama bu istekler bir \u00f6deme \u00e7a\u011fr\u0131s\u0131ysa, &#8220;birka\u00e7 istek&#8221; k\u00fc\u00e7\u00fck bir problem de\u011fil.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kapanma s\u0131ras\u0131 paralel ilerler<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Kubernetes bir pod&#8217;u sonland\u0131rmaya karar verdi\u011finde iki \u015fey neredeyse ayn\u0131 anda olur:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pod&#8217;a SIGTERM sinyali g\u00f6nderilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pod, Service&#8217;in endpoint listesinden \u00e7\u0131kar\u0131l\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sorun \u015fu ki ikincisi anl\u0131k de\u011fildir. Endpoint de\u011fi\u015fikli\u011finin kube-proxy&#8217;lere, ingress controller&#8217;a ve service mesh&#8217;e yay\u0131lmas\u0131 zaman al\u0131r. Birka\u00e7 saniye boyunca bu bile\u015fenler trafi\u011fi h\u00e2l\u00e2 kapanmakta olan pod&#8217;a g\u00f6nderebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Uygulama SIGTERM&#8217;i al\u0131r almaz kapan\u0131rsa, bu s\u00fcre i\u00e7inde gelen istekler kapal\u0131 bir porta denk gelir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">preStop ile beklemek<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu yar\u0131\u015f\u0131 \u00f6nlemenin en yayg\u0131n yolu, SIGTERM&#8217;den \u00f6nce k\u0131sa bir bekleme koymakt\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>lifecycle:\n  preStop:\n    exec:\n      command: [\"sleep\", \"10\"]<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Kubernetes \u00f6nce preStop hook&#8217;unu \u00e7al\u0131\u015ft\u0131r\u0131r, o bitince SIGTERM g\u00f6nderir. Bu 10 saniye boyunca uygulama normal \u015fekilde istek almaya devam eder, bu arada da endpoint de\u011fi\u015fikli\u011fi b\u00fct\u00fcn bile\u015fenlere yay\u0131l\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kula\u011fa biraz hack gibi geliyor. Ama Kubernetes&#8217;in mevcut tasar\u0131m\u0131nda bu yakla\u015f\u0131m olduk\u00e7a standart. Yeni Kubernetes s\u00fcr\u00fcmlerinde <code>sleep<\/code> i\u00e7in container image&#8217;\u0131na ihtiya\u00e7 duymayan yerle\u015fik bir preStop aksiyonu da bulunuyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Graceful shutdown<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SIGTERM geldi\u011finde uygulaman\u0131n yapmas\u0131 gereken \u015fey yeni istek kabul etmeyi b\u0131rakmak ve devam eden istekleri tamamlamakt\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Boot&#8217;ta bu tek sat\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>server.shutdown=graceful\nspring.lifecycle.timeout-per-shutdown-phase=20s<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Uygulama yeni ba\u011flant\u0131lar\u0131 reddeder, mevcut istekler en fazla 20 saniye i\u00e7inde tamamlan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama HTTP istekleri tek i\u015f de\u011fildir. Kafka consumer&#8217;lar\u0131, i\u015flenmekte olan kuyruk mesajlar\u0131 ve arka plan i\u015fleri de d\u00fczg\u00fcn \u015fekilde durdurulmal\u0131. Yar\u0131da kalan bir mesaj, commit edilmediyse ba\u015fka bir instance taraf\u0131ndan yeniden i\u015flenir. Bu da idempotency&#8217;nin neden her yerde \u00f6nemli oldu\u011funun bir ba\u015fka \u00f6rne\u011fi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">S\u00fcreler birbirine uymal\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Burada birka\u00e7 de\u011fer birbiriyle tutarl\u0131 olmal\u0131:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>preStop sleep              10s\ngraceful shutdown timeout  20s\nterminationGracePeriod     40s<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>terminationGracePeriodSeconds<\/code> toplam s\u00fcredir ve preStop beklemesini de kapsar. Varsay\u0131lan de\u011feri 30 saniyedir. preStop ve graceful shutdown s\u00fcresinin toplam\u0131 bunu a\u015farsa Kubernetes SIGKILL g\u00f6nderir ve uygulama ne yap\u0131yorsa yar\u0131da kal\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Readiness ve liveness farkl\u0131 sorular sorar<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Deploy problemlerinin bir k\u0131sm\u0131 da yeni pod&#8217;un trafi\u011fe \u00e7ok erken a\u00e7\u0131lmas\u0131ndan kaynaklan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Readiness probe \u015funu sorar: bu pod \u015fu anda trafik almaya haz\u0131r m\u0131?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Liveness probe ise \u015funu sorar: bu pod kurtar\u0131lamaz bir durumda m\u0131, yeniden ba\u015flat\u0131lmal\u0131 m\u0131?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Boot Actuator bu ikisini ayr\u0131 endpoint&#8217;ler olarak sunuyor:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/actuator\/health\/readiness\n\/actuator\/health\/liveness<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0131k yap\u0131lan bir hata, liveness probe&#8217;a veritaban\u0131 kontrol\u00fc eklemektir. Veritaban\u0131 k\u0131sa s\u00fcreli\u011fine eri\u015filemez oldu\u011funda b\u00fct\u00fcn pod&#8217;lar ayn\u0131 anda yeniden ba\u015flat\u0131l\u0131r. Bu da veritaban\u0131 geri geldi\u011finde \u00fczerine so\u011fuk ba\u015flayan onlarca pod&#8217;un y\u00fcklenmesi anlam\u0131na gelir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">D\u0131\u015f ba\u011f\u0131ml\u0131l\u0131klar liveness&#8217;ta de\u011fil, gerekiyorsa readiness&#8217;ta kontrol edilmelidir. Liveness sadece uygulaman\u0131n kendisinin kilitlenip kilitlenmedi\u011fini s\u00f6ylemeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">JVM uygulamalar\u0131 i\u00e7in bir de startup s\u00fcresi var. Uygulama aya\u011fa kalkarken liveness probe&#8217;un erken ba\u015far\u0131s\u0131z olmas\u0131n\u0131 \u00f6nlemek i\u00e7in <code>startupProbe<\/code> tan\u0131mlamak, uzun initial delay de\u011ferleriyle u\u011fra\u015fmaktan daha temiz bir \u00e7\u00f6z\u00fcm.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Test etmek<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu ayarlar\u0131n do\u011fru olup olmad\u0131\u011f\u0131n\u0131 anlaman\u0131n en iyi yolu, deploy s\u0131ras\u0131nda s\u00fcrekli trafik g\u00f6nderen basit bir y\u00fck testi \u00e7al\u0131\u015ft\u0131rmakt\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deploy boyunca tek bir hata bile g\u00f6r\u00fcn\u00fcyorsa, kapanma s\u0131ras\u0131nda bir \u015fey eksik demektir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kesintisiz deploy, platformun bize haz\u0131r verdi\u011fi bir \u00f6zellik de\u011fil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Uygulaman\u0131n kapanmay\u0131 bilmesiyle elde edilen bir sonu\u00e7.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Rolling update kesintisiz olmal\u0131 ama her deploy&#8217;da birka\u00e7 502 g\u00f6r\u00fcn\u00fcyor. SIGTERM, preStop, readiness probe ve Spring Boot graceful shutdown birlikte nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/p>\n","protected":false},"author":1,"featured_media":68,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-69","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dagitik-sistemler"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/69","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=69"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/69\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/68"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=69"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=69"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=69"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}