Da\u011f\u0131t\u0131k sistemlerin gelece\u011fi Kubernetes ile karma\u015f\u0131k uygulamalar\u0131 y\u00f6netmek art\u0131k daha kolay! Vagrant kullanarak kendi yerel \u00e7ok d\u00fc\u011f\u00fcml\u00fc Kubernetes k\u00fcmenizi ad\u0131m ad\u0131m nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 \u00f6\u011frenin. Bu kapsaml\u0131 rehber, sanal ortamda g\u00fc\u00e7l\u00fc bir geli\u015ftirme altyap\u0131s\u0131 olu\u015fturman\u0131za yard\u0131mc\u0131 olacak.<\/p>\n
G\u00fcn\u00fcm\u00fcz\u00fcn h\u0131zla de\u011fi\u015fen teknoloji d\u00fcnyas\u0131nda, uygulamalar\u0131n esnek, \u00f6l\u00e7eklenebilir ve g\u00fcvenilir olmas\u0131 her zamankinden daha kritik. Mikroservis mimarileri ve konteynerle\u015fme, bu gereksinimleri kar\u015f\u0131lamak i\u00e7in standart haline gelmi\u015f durumda. \u0130\u015fte tam bu noktada, konteynerle\u015ftirilmi\u015f i\u015f y\u00fcklerini otomatize etmek, da\u011f\u0131tmak ve y\u00f6netmek i\u00e7in tasarlanm\u0131\u015f a\u00e7\u0131k kaynakl\u0131 bir sistem olan Kubernetes devreye giriyor. Ancak Kubernetes’i ger\u00e7ek bir ortamda denemek, \u00f6\u011frenmek veya geli\u015ftirmek \u00e7o\u011fu zaman zorlu ve kaynak yo\u011fun bir s\u00fcre\u00e7 olabilir. Bulut sa\u011flay\u0131c\u0131lar\u0131 \u00fczerinde bir k\u00fcme kurmak maliyetli olabilirken, yerel bir ortamda \u00e7ok d\u00fc\u011f\u00fcml\u00fc bir k\u00fcme olu\u015fturmak da karma\u015f\u0131k a\u011f ve sanalla\u015ft\u0131rma bilgisi gerektirebilir. Peki, bu zorluklar\u0131 a\u015farak, hem uygun maliyetli hem de pratik bir \u015fekilde kendi \u00e7ok d\u00fc\u011f\u00fcml\u00fc Kubernetes k\u00fcmenizi nas\u0131l kurabilirsiniz?<\/p>\n
Bu makale, bu sorunun cevab\u0131n\u0131 Vagrant ile veriyor. Vagrant, sanal makine ortamlar\u0131n\u0131 kolayca olu\u015fturman\u0131z\u0131 ve y\u00f6netmenizi sa\u011flayan bir ara\u00e7t\u0131r. Geli\u015ftiricilerin “makinemde \u00e7al\u0131\u015f\u0131yor” sorununu ortadan kald\u0131rmay\u0131 hedefler ve her ekip \u00fcyesi i\u00e7in ayn\u0131 geli\u015ftirme ortam\u0131n\u0131 garantiler. Vagrant’\u0131n g\u00fcc\u00fcn\u00fc Kubernetes ile birle\u015ftirdi\u011fimizde, kendi yerel makinenizde ger\u00e7ek bir \u00e7ok d\u00fc\u011f\u00fcml\u00fc Kubernetes k\u00fcmesi sim\u00fcle edebiliriz. Bu, yaln\u0131zca bir e\u011fitim arac\u0131 olmakla kalmaz, ayn\u0131 zamanda \u00fcretim ortam\u0131na deploy edece\u011finiz uygulamalar\u0131 yerel olarak test etmenizi, CI\/CD pipeline’lar\u0131n\u0131 geli\u015ftirmenizi ve da\u011f\u0131t\u0131k sistem mimarilerini derinlemesine anlaman\u0131z\u0131 sa\u011flayan paha bi\u00e7ilmez bir geli\u015ftirme ortam\u0131 sunar.<\/p>\n
\u00d6zellikle DevOps m\u00fchendisleri, yaz\u0131l\u0131m geli\u015ftiriciler ve sistem y\u00f6neticileri i\u00e7in, bu kurulum y\u00f6ntemi bir\u00e7ok avantaj sa\u011flar. \u00d6ncelikle, bulut tabanl\u0131 bir k\u00fcme kullanman\u0131n getirdi\u011fi maliyetlerden ka\u00e7\u0131nm\u0131\u015f olursunuz. \u0130kinci olarak, internet ba\u011flant\u0131s\u0131na ba\u011f\u0131ml\u0131 kalmadan istedi\u011finiz zaman ve istedi\u011finiz yerde k\u00fcmenizle \u00e7al\u0131\u015fabilirsiniz. \u00dc\u00e7\u00fcnc\u00fcs\u00fc, \u00fcretim ortam\u0131na benzer bir ortamda uygulama geli\u015ftirme ve test etme imkan\u0131, potansiyel sorunlar\u0131 erken a\u015famada tespit etmenize yard\u0131mc\u0131 olur. Bu rehberde, ad\u0131m ad\u0131m ilerleyerek, Vagrant ve VirtualBox kullanarak temel bir Kubernetes k\u00fcmesinin nas\u0131l olu\u015fturulaca\u011f\u0131n\u0131, yap\u0131land\u0131r\u0131laca\u011f\u0131n\u0131 ve y\u00f6netilece\u011fini \u00f6\u011freneceksiniz. Haz\u0131rsan\u0131z, konteyner orkestrasyonunun b\u00fcy\u00fcl\u00fc d\u00fcnyas\u0131na Vagrant ile birlikte dalal\u0131m!<\/p>\n
Ba\u015flamadan \u00f6nce, bu rehberde kullanaca\u011f\u0131m\u0131z iki ana teknoloji olan Vagrant ve Kubernetes’in temel prensiplerini anlamak \u00f6nemlidir. Bu bilgiler, yapaca\u011f\u0131m\u0131z ad\u0131mlar\u0131n ard\u0131ndaki mant\u0131\u011f\u0131 kavraman\u0131za yard\u0131mc\u0131 olacak ve olas\u0131 sorun giderme s\u00fcre\u00e7lerinde size yol g\u00f6sterecektir.<\/p>\n
Vagrant, HashiCorp taraf\u0131ndan geli\u015ftirilen, sanal ortamlar\u0131 tek tip bir i\u015f ak\u0131\u015f\u0131yla olu\u015fturmak ve y\u00f6netmek i\u00e7in kullan\u0131lan bir a\u00e7\u0131k kaynakl\u0131 ara\u00e7t\u0131r. Temel amac\u0131, geli\u015ftiricilerin farkl\u0131 i\u015fletim sistemleri ve altyap\u0131lar aras\u0131nda tutarl\u0131 geli\u015ftirme ortamlar\u0131 kurmas\u0131n\u0131 sa\u011flamakt\u0131r. Vagrant, VirtualBox, VMWare, Hyper-V gibi \u00e7e\u015fitli sanalla\u015ft\u0131rma sa\u011flay\u0131c\u0131lar\u0131yla entegre olabilir. Biz bu rehberde \u00fccretsiz ve a\u00e7\u0131k kaynakl\u0131 olmas\u0131 nedeniyle VirtualBox’\u0131 kullanaca\u011f\u0131z.<\/p>\n
Vagrant’\u0131n sa\u011flad\u0131\u011f\u0131 temel faydalar \u015funlard\u0131r:<\/p>\n
vagrant up<\/code>) ba\u015flat\u0131r.<\/li>\n- Ta\u015f\u0131nabilirlik:<\/strong> Olu\u015fturulan sanal ortamlar, Vagrantfile sayesinde farkl\u0131 makinelerde kolayca yeniden \u00fcretilebilir.<\/li>\n
- Otomasyon:<\/strong> Sanal makine kurulumunu, paket y\u00fcklemeyi, a\u011f yap\u0131land\u0131rmas\u0131n\u0131 ve di\u011fer sistem ayarlar\u0131n\u0131 otomatikle\u015ftirir.<\/li>\n<\/ul>\n
\u00d6zetle, Vagrant, karma\u015f\u0131k altyap\u0131 senaryolar\u0131n\u0131, \u00f6rne\u011fin \u00e7ok d\u00fc\u011f\u00fcml\u00fc bir Kubernetes k\u00fcmesini, yerel makinenizde kolayca sim\u00fcle etmenizi sa\u011flayan g\u00fc\u00e7l\u00fc bir otomasyon arac\u0131d\u0131r.<\/p>\n
Kubernetes Nedir ve Temel Bile\u015fenleri Nelerdir?<\/h3>\n
Kubernetes (genellikle K8s olarak k\u0131salt\u0131l\u0131r), Google taraf\u0131ndan geli\u015ftirilen ve \u015fu anda Cloud Native Computing Foundation (CNCF) taraf\u0131ndan s\u00fcrd\u00fcr\u00fclen a\u00e7\u0131k kaynakl\u0131 bir konteyner orkestrasyon platformudur. Amac\u0131, konteynerle\u015ftirilmi\u015f uygulamalar\u0131n da\u011f\u0131t\u0131m\u0131n\u0131, \u00f6l\u00e7eklendirilmesini ve y\u00f6netimini otomatikle\u015ftirmektir. Docker gibi konteyner teknolojileriyle birlikte \u00e7al\u0131\u015farak, uygulamalar\u0131n\u0131z\u0131 farkl\u0131 ortamlar aras\u0131nda ta\u015f\u0131nabilir hale getirir.<\/p>\n
Bir Kubernetes k\u00fcmesi, uygulaman\u0131z\u0131 \u00e7al\u0131\u015ft\u0131ran bir grup d\u00fc\u011f\u00fcmden (makineden) olu\u015fur. Bu d\u00fc\u011f\u00fcmler iki ana kategoriye ayr\u0131l\u0131r:<\/p>\n
\n- Kontrol D\u00fczlemi (Control Plane \/ Master Node):<\/strong> K\u00fcmenin beynidir. T\u00fcm kararlar\u0131 al\u0131r ve k\u00fcmenin durumunu y\u00f6netir. Temel bile\u015fenleri:\n
\n- kube-apiserver:<\/strong> Kubernetes API’sini ortaya \u00e7\u0131kar\u0131r. K\u00fcme ile etkile\u015fim kurmak i\u00e7in ana aray\u00fczd\u00fcr.<\/li>\n
- etcd:<\/strong> K\u00fcme verilerinin depoland\u0131\u011f\u0131, y\u00fcksek d\u00fczeyde kullan\u0131labilir bir anahtar-de\u011fer deposudur.<\/li>\n
- kube-scheduler:<\/strong> Yeni olu\u015fturulan Pod’lar\u0131 hangi d\u00fc\u011f\u00fcmlere yerle\u015ftirece\u011fine karar verir.<\/li>\n
- kube-controller-manager:<\/strong> \u00c7e\u015fitli kontrol\u00f6rleri \u00e7al\u0131\u015ft\u0131r\u0131r (\u00f6rne\u011fin, d\u00fc\u011f\u00fcm kontrol\u00f6r\u00fc, \u00e7o\u011faltma kontrol\u00f6r\u00fc).<\/li>\n<\/ul>\n<\/li>\n
- \u00c7al\u0131\u015fan D\u00fc\u011f\u00fcmler (Worker Nodes):<\/strong> Kontrol d\u00fczlemi taraf\u0131ndan atanan g\u00f6revleri \u00e7al\u0131\u015ft\u0131ran makinelerdir. Her \u00e7al\u0131\u015fan d\u00fc\u011f\u00fcmde \u015fu bile\u015fenler bulunur:\n
\n- kubelet:<\/strong> Her d\u00fc\u011f\u00fcmde \u00e7al\u0131\u015fan bir arac\u0131d\u0131r. Kontrol d\u00fczleminden gelen talimatlar\u0131 al\u0131r ve konteynerleri \u00e7al\u0131\u015ft\u0131r\u0131r, Pod’lar\u0131n durumunu denetler.<\/li>\n
- kube-proxy:<\/strong> K\u00fcme i\u00e7indeki a\u011f kurallar\u0131n\u0131 y\u00f6netir ve Pod’lara a\u011f proxy’si sa\u011flar.<\/li>\n
- Konteyner \u00c7al\u0131\u015fma Zaman\u0131 (Container Runtime):<\/strong> Konteynerleri \u00e7al\u0131\u015ft\u0131ran yaz\u0131l\u0131m (\u00f6rne\u011fin Docker, containerd, CRI-O).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Bu bile\u015fenlerin uyumlu \u00e7al\u0131\u015fmas\u0131 sayesinde Kubernetes, uygulamalar\u0131n\u0131z\u0131n y\u00fcksek oranda kullan\u0131labilir, \u00f6l\u00e7eklenebilir ve y\u00f6netilebilir olmas\u0131n\u0131 sa\u011flar.<\/p>\n
\u00d6n Haz\u0131rl\u0131k: Sistem Gereksinimleri ve Kurulum Ad\u0131mlar\u0131<\/h2>\n
\u00c7ok d\u00fc\u011f\u00fcml\u00fc Kubernetes k\u00fcmemizi Vagrant ile kurmaya ba\u015flamadan \u00f6nce, yerel geli\u015ftirme ortam\u0131m\u0131z\u0131n haz\u0131r oldu\u011fundan emin olmal\u0131y\u0131z. Bu b\u00f6l\u00fcm, gerekli yaz\u0131l\u0131mlar\u0131n kurulumu ve sistem gereksinimleri hakk\u0131nda bilgi verecektir. Ba\u015far\u0131l\u0131 bir kurulum i\u00e7in bu ad\u0131mlar\u0131 dikkatlice takip etmek \u00f6nemlidir.<\/p>\n
Gerekli Yaz\u0131l\u0131mlar ve Sistem Gereksinimleri<\/h3>\n
Bu rehber i\u00e7in a\u015fa\u011f\u0131daki yaz\u0131l\u0131mlara ihtiyac\u0131m\u0131z olacak:<\/p>\n
\n- \u0130\u015fletim Sistemi:<\/strong> Linux (Ubuntu, Fedora, CentOS), macOS veya Windows. Bu makaledeki ad\u0131mlar genel olarak platformdan ba\u011f\u0131ms\u0131z olsa da, shell komutlar\u0131 Linux\/macOS ortamlar\u0131na daha uygun olacakt\u0131r. Windows kullan\u0131c\u0131lar\u0131 WSL2 (Windows Subsystem for Linux 2) ile benzer bir deneyim elde edebilir.<\/li>\n
- VirtualBox:<\/strong> Sanal makineleri bar\u0131nd\u0131rmak i\u00e7in bir sanalla\u015ft\u0131rma yaz\u0131l\u0131m\u0131d\u0131r. \u00dccretsiz ve a\u00e7\u0131k kaynakl\u0131d\u0131r.<\/li>\n
- Vagrant:<\/strong> Sanal makineleri otomatik olarak yap\u0131land\u0131rmak i\u00e7in kulland\u0131\u011f\u0131m\u0131z ara\u00e7t\u0131r.<\/li>\n
- Git:<\/strong> Depomuzdaki dosyalar\u0131 kopyalamak i\u00e7in gereklidir (iste\u011fe ba\u011fl\u0131, dosyalar\u0131 manuel indirebilirsiniz).<\/li>\n
- \u0130nternet Ba\u011flant\u0131s\u0131:<\/strong> Vagrant box’lar\u0131n\u0131 ve di\u011fer paketleri indirmek i\u00e7in gereklidir.<\/li>\n<\/ol>\n
Donan\u0131m Gereksinimleri:<\/strong><\/p>\n\n- RAM:<\/strong> En az 8 GB RAM (16 GB \u00f6nerilir). Her sanal makine i\u00e7in belirli bir miktar RAM ayr\u0131lacakt\u0131r.<\/li>\n
- CPU:<\/strong> \u00c7ok \u00e7ekirdekli i\u015flemci (en az 2 \u00e7ekirdek, 4+ \u00f6nerilir). Sanal makineler i\u015flemci \u00e7ekirdeklerini payla\u015facakt\u0131r.<\/li>\n
- Disk Alan\u0131:<\/strong> En az 40 GB bo\u015f disk alan\u0131 (60 GB+ \u00f6nerilir). Sanal diskler ve i\u015fletim sistemi kurulumlar\u0131 i\u00e7in yer gereklidir.<\/li>\n<\/ul>\n
Uzman \u0130pucu: Sistem kaynaklar\u0131 ne kadar y\u00fcksek olursa, Kubernetes k\u00fcmeniz o kadar h\u0131zl\u0131 ve verimli \u00e7al\u0131\u015facakt\u0131r. \u00d6zellikle RAM, VM performans\u0131nda kritik bir rol oynar.<\/p>\n
Kurulum Ad\u0131mlar\u0131:<\/h3>\n
\u015eimdi yukar\u0131da bahsedilen yaz\u0131l\u0131mlar\u0131 s\u0131ras\u0131yla kural\u0131m:<\/p>\n
1. VirtualBox Kurulumu<\/h4>\n
VirtualBox’\u0131 resmi web sitesinden<\/a> i\u015fletim sisteminize uygun s\u00fcr\u00fcm\u00fcn\u00fc indirerek kurun. Kurulum ad\u0131mlar\u0131 genellikle basittir ve varsay\u0131lan se\u00e7enekleri kabul ederek ilerleyebilirsiniz. Kurulumdan sonra, sisteminizi yeniden ba\u015flatman\u0131z gerekebilir.<\/p>\n2. Vagrant Kurulumu<\/h4>\n
Vagrant’\u0131 resmi web sitesinden<\/a> i\u015fletim sisteminize uygun s\u00fcr\u00fcm\u00fcn\u00fc indirerek kurun. T\u0131pk\u0131 VirtualBox gibi, Vagrant’\u0131n kurulumu da genellikle bir y\u00fckleyici arac\u0131l\u0131\u011f\u0131yla basit\u00e7e tamamlan\u0131r. Kurulumdan sonra bir terminal a\u00e7\u0131n ve a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131rarak Vagrant’\u0131n do\u011fru \u015fekilde kuruldu\u011funu do\u011frulay\u0131n:<\/p>\n\nvagrant --version\n <\/pre>\n<\/code><\/p>\n
Bu komut, Vagrant'\u0131n kurulu s\u00fcr\u00fcm\u00fcn\u00fc g\u00f6stermelidir. E\u011fer komut bulunamazsa, sisteminizin PATH de\u011fi\u015fkenini kontrol etmeniz veya Vagrant y\u00fckleyicisini tekrar \u00e7al\u0131\u015ft\u0131rman\u0131z gerekebilir.<\/p>\n
3. Git Kurulumu (\u0130ste\u011fe Ba\u011fl\u0131 ama \u00d6nerilir)<\/h4>\n
Git, genellikle bir\u00e7ok sistemde zaten y\u00fckl\u00fcd\u00fcr. Y\u00fckl\u00fc olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in:<\/p>\n
\ngit --version\n <\/pre>\n<\/code><\/p>\n
E\u011fer y\u00fckl\u00fc de\u011filse, i\u015fletim sisteminize g\u00f6re a\u015fa\u011f\u0131daki komutlar\u0131 kullanabilirsiniz:<\/p>\n
\n- Ubuntu\/Debian:<\/strong>
sudo apt update && sudo apt install git -y<\/code><\/li>\n- CentOS\/RHEL:<\/strong>
sudo yum install git -y<\/code><\/li>\n- macOS:<\/strong>
brew install git<\/code> (Homebrew y\u00fckl\u00fc de\u011filse brew.sh<\/a> adresinden kurun)<\/li>\n- Windows:<\/strong> Git for Windows<\/a> adresinden indirin ve kurun.<\/li>\n<\/ul>\n
Bu \u00f6n haz\u0131rl\u0131k ad\u0131mlar\u0131n\u0131 tamamlad\u0131ktan sonra, art\u0131k Vagrant ve VirtualBox'\u0131n g\u00fcc\u00fcn\u00fc birle\u015ftirerek kendi \u00e7ok d\u00fc\u011f\u00fcml\u00fc Kubernetes k\u00fcmenizi olu\u015fturmaya haz\u0131rs\u0131n\u0131z. Bir sonraki b\u00f6l\u00fcmde, Vagrantfile'\u0131 nas\u0131l yap\u0131land\u0131raca\u011f\u0131m\u0131z\u0131 ve k\u00fcme bile\u015fenlerini nas\u0131l kuraca\u011f\u0131m\u0131z\u0131 ad\u0131m ad\u0131m inceleyece\u011fiz.<\/p>\n
Uygulamal\u0131 K\u0131s\u0131m: Vagrant ile \u00c7ok D\u00fc\u011f\u00fcml\u00fc Kubernetes K\u00fcmesi Nas\u0131l Kurulur?<\/h2>\n
\u015eimdi makalemizin en heyecanl\u0131 k\u0131sm\u0131na geldik: Vagrant ile \u00e7ok d\u00fc\u011f\u00fcml\u00fc Kubernetes k\u00fcmemizi ad\u0131m ad\u0131m kuraca\u011f\u0131z. Bu b\u00f6l\u00fcmde, bir Vagrantfile'\u0131 nas\u0131l olu\u015fturaca\u011f\u0131m\u0131z\u0131 ve hem master hem de worker d\u00fc\u011f\u00fcmleri i\u00e7in gerekli yap\u0131land\u0131rma betiklerini nas\u0131l yazaca\u011f\u0131m\u0131z\u0131 \u00f6\u011freneceksiniz. Bu kurulumda Ubuntu 20.04 i\u015fletim sistemi tabanl\u0131 sanal makineler kullanaca\u011f\u0131z ve Kubernetes'i kubeadm<\/code> arac\u0131yla bootstrap edece\u011fiz.<\/p>\n1. \u00c7al\u0131\u015fma Dizini Olu\u015fturma<\/h3>\n
\u00d6ncelikle, t\u00fcm proje dosyalar\u0131m\u0131z\u0131 i\u00e7erecek bir dizin olu\u015ftural\u0131m ve bu dizine ge\u00e7i\u015f yapal\u0131m:<\/p>\n
\nmkdir kubernetes-vagrant\ncd kubernetes-vagrant\n <\/pre>\n<\/code><\/p>\n
2. Vagrantfile Olu\u015fturma<\/h3>\n
Bu dizin i\u00e7inde, Vagrant'\u0131n sanal makinelerimizi nas\u0131l olu\u015fturaca\u011f\u0131n\u0131 ve yap\u0131land\u0131raca\u011f\u0131n\u0131 belirten bir Vagrantfile<\/code> olu\u015fturaca\u011f\u0131z. Bu dosya, k\u00fcmemizin topolojisini, her bir d\u00fc\u011f\u00fcm\u00fcn kaynaklar\u0131n\u0131 (RAM, CPU) ve a\u011f ayarlar\u0131n\u0131 tan\u0131mlayacak. \u0130\u00e7ine a\u015fa\u011f\u0131daki kodu yap\u0131\u015ft\u0131r\u0131n:<\/p>\n\n# -*- mode: ruby -*-\n# vi: set ft=ruby :\n\nVagrant.configure(\"2\") do |config|\n # Sanal makineler i\u00e7in temel box (Ubuntu 20.04)\n config.vm.box = \"ubuntu\/focal64\"\n config.vm.box_check_update = false\n\n # A\u011f ayarlar\u0131 i\u00e7in \u00f6zel IP aral\u0131\u011f\u0131\n # \u00d6NEML\u0130: Bu IP'lerin yerel a\u011f\u0131n\u0131zda \u00e7ak\u0131\u015fmad\u0131\u011f\u0131ndan emin olun.\n private_ip_prefix = \"172.16.16\"\n\n # Master d\u00fc\u011f\u00fcm tan\u0131m\u0131\n config.vm.define \"k8s-master\" do |master|\n master.vm.hostname = \"k8s-master\"\n master.vm.network \"private_network\", ip: \"#{private_ip_prefix}.100\"\n master.vm.provider \"virtualbox\" do |vb|\n vb.memory = \"2048\" # 2 GB RAM\n vb.cpus = \"2\" # 2 CPU \u00e7ekirde\u011fi\n end\n master.vm.provision \"shell\", path: \"scripts\/master_provision.sh\", privileged: true\n end\n\n # Worker d\u00fc\u011f\u00fcmler tan\u0131m\u0131\n (1..2).each do |i|\n config.vm.define \"k8s-worker-#{i}\" do |worker|\n worker.vm.hostname = \"k8s-worker-#{i}\"\n worker.vm.network \"private_network\", ip: \"#{private_ip_prefix}.10#{i}\"\n worker.vm.provider \"virtualbox\" do |vb|\n vb.memory = \"1024\" # 1 GB RAM\n vb.cpus = \"1\" # 1 CPU \u00e7ekirde\u011fi\n end\n worker.vm.provision \"shell\", path: \"scripts\/worker_provision.sh\", privileged: true\n end\n end\n\n # T\u00fcm sanal makineler i\u00e7in ortak ayarlar\n config.vm.synced_folder \".\", \"\/vagrant\", disabled: true # Payla\u015f\u0131lan klas\u00f6r\u00fc devre d\u0131\u015f\u0131 b\u0131rak\n config.ssh.insert_key = false # SSH anahtar\u0131n\u0131n otomatik eklenmesini devre d\u0131\u015f\u0131 b\u0131rak\nend\n <\/pre>\n<\/code><\/p>\n
Bu Vagrantfile, bir master ve iki worker d\u00fc\u011f\u00fcm olmak \u00fczere toplam \u00fc\u00e7 sanal makine olu\u015fturacakt\u0131r. Her d\u00fc\u011f\u00fcme statik bir \u00f6zel IP adresi atan\u0131r ve kaynaklar\u0131 (RAM, CPU) belirtilir. Ayr\u0131ca, her d\u00fc\u011f\u00fcm ba\u015flat\u0131ld\u0131\u011f\u0131nda belirli bir provisioning (haz\u0131rl\u0131k) beti\u011fini \u00e7al\u0131\u015ft\u0131r\u0131r.<\/p>\n
3. Provisioning Betikleri Olu\u015fturma<\/h3>\n
\u015eimdi, sanal makinelerin i\u00e7ine Kubernetes bile\u015fenlerini kuracak ve yap\u0131land\u0131racak betikleri yazal\u0131m. Bunun i\u00e7in scripts<\/code> ad\u0131nda bir dizin olu\u015ftural\u0131m:<\/p>\n\nmkdir scripts\n <\/pre>\n<\/code><\/p>\n
3.1. Master D\u00fc\u011f\u00fcm Yap\u0131land\u0131rmas\u0131: Kontrol D\u00fczlemini Haz\u0131rlama<\/h4>\n
scripts\/master_provision.sh<\/code> ad\u0131nda bir dosya olu\u015fturun ve i\u00e7ine a\u015fa\u011f\u0131daki kodu yap\u0131\u015ft\u0131r\u0131n. Bu betik, Kubernetes kontrol d\u00fczlemini (master) kurar, Flannel CNI'yi da\u011f\u0131t\u0131r ve kubeconfig dosyas\u0131n\u0131 haz\u0131rlar.<\/p>\n\n#!\/bin\/bash\n\n# Ortak Kubernetes kurulum ad\u0131mlar\u0131\necho \"Ortak Kubernetes kurulum ad\u0131mlar\u0131 ba\u015flat\u0131l\u0131yor...\"\nsudo apt update -y\nsudo apt install -y apt-transport-https ca-certificates curl gnupg lsb-release\n\n# Google Kubernetes GPG anahtar\u0131n\u0131 ekle\ncurl -fsSL https:\/\/packages.cloud.google.com\/apt\/doc\/apt-key.gpg | sudo gpg --dearmor -o \/etc\/apt\/keyrings\/kubernetes-archive-keyring.gpg\n\n# Kubernetes apt deposunu ekle\necho \"deb [signed-by=\/etc\/apt\/keyrings\/kubernetes-archive-keyring.gpg] https:\/\/apt.kubernetes.io\/ kubernetes-xenial main\" | sudo tee \/etc\/apt\/sources.list.d\/kubernetes.list > \/dev\/null\n\nsudo apt update -y\n# Kubernetes bile\u015fenlerini kur (kubelet, kubeadm, kubectl)\nsudo apt install -y kubelet kubeadm kubectl\nsudo apt-mark hold kubelet kubeadm kubectl\n\n# Containerd kurulumu\necho \"Containerd kurulumu ba\u015flat\u0131l\u0131yor...\"\nsudo apt install -y containerd\nsudo mkdir -p \/etc\/containerd\nsudo containerd config default | sudo tee \/etc\/containerd\/config.toml\nsudo sed -i 's\/SystemdCgroup = false\/SystemdCgroup = true\/' \/etc\/containerd\/config.toml\nsudo systemctl restart containerd\nsudo systemctl enable containerd\n\n# Swap'\u0131 kapat\necho \"Swap kapat\u0131l\u0131yor...\"\nsudo swapoff -a\nsudo sed -i '\/ swap \/ s\/^\/#\/' \/etc\/fstab\n\n# Kernel mod\u00fclleri ve sysctl ayarlar\u0131\necho \"Kernel mod\u00fclleri ve sysctl ayarlar\u0131 yap\u0131l\u0131yor...\"\nsudo modprobe overlay\nsudo modprobe br_netfilter\nsudo tee \/etc\/modules-load.d\/containerd.conf < \/vagrant\/join-command.sh\nchmod +x \/vagrant\/join-command.sh\n\necho \"Kubernetes Master d\u00fc\u011f\u00fcm\u00fc ba\u015far\u0131yla kuruldu ve yap\u0131land\u0131r\u0131ld\u0131!\"\n <\/pre>\n<\/code><\/p>\n
3.2. Worker D\u00fc\u011f\u00fcm Yap\u0131land\u0131rmas\u0131: Uygulamalar\u0131 \u00c7al\u0131\u015ft\u0131rma Katman\u0131<\/h4>\n
scripts\/worker_provision.sh<\/code> ad\u0131nda bir dosya olu\u015fturun ve i\u00e7ine a\u015fa\u011f\u0131daki kodu yap\u0131\u015ft\u0131r\u0131n. Bu betik, worker d\u00fc\u011f\u00fcmleri Kubernetes k\u00fcmesine kat\u0131lacak \u015fekilde yap\u0131land\u0131r\u0131r.<\/p>\n\n#!\/bin\/bash\n\n# Ortak Kubernetes kurulum ad\u0131mlar\u0131 (Master beti\u011findekiyle ayn\u0131)\necho \"Ortak Kubernetes kurulum ad\u0131mlar\u0131 ba\u015flat\u0131l\u0131yor...\"\nsudo apt update -y\nsudo apt install -y apt-transport-https ca-certificates curl gnupg lsb-release\n\ncurl -fsSL https:\/\/packages.cloud.google.com\/apt\/doc\/apt-key.gpg | sudo gpg --dearmor -o \/etc\/apt\/keyrings\/kubernetes-archive-keyring.gpg\n\necho \"deb [signed-by=\/etc\/apt\/keyrings\/kubernetes-archive-keyring.gpg] https:\/\/apt.kubernetes.io\/ kubernetes-xenial main\" | sudo tee \/etc\/apt\/sources.list.d\/kubernetes.list > \/dev\/null\n\nsudo apt update -y\nsudo apt install -y kubelet kubeadm kubectl\nsudo apt-mark hold kubelet kubeadm kubectl\n\necho \"Containerd kurulumu ba\u015flat\u0131l\u0131yor...\"\nsudo apt install -y containerd\nsudo mkdir -p \/etc\/containerd\nsudo containerd config default | sudo tee \/etc\/containerd\/config.toml\nsudo sed -i 's\/SystemdCgroup = false\/SystemdCgroup = true\/' \/etc\/containerd\/config.toml\nsudo systemctl restart containerd\nsudo systemctl enable containerd\n\necho \"Swap kapat\u0131l\u0131yor...\"\nsudo swapoff -a\nsudo sed -i '\/ swap \/ s\/^\/#\/' \/etc\/fstab\n\necho \"Kernel mod\u00fclleri ve sysctl ayarlar\u0131 yap\u0131l\u0131yor...\"\nsudo modprobe overlay\nsudo modprobe br_netfilter\nsudo tee \/etc\/modules-load.d\/containerd.conf <\n<\/code><\/p>\n
Uzman \u0130pucu: Provisioning betiklerinde yap\u0131lan t\u00fcm de\u011fi\u015fiklikler, vagrant reload --provision<\/code> komutuyla sanal makinelerinizi yeniden ba\u015flat\u0131p betikleri tekrar \u00e7al\u0131\u015ft\u0131rman\u0131z\u0131 sa\u011flar. Bu, hata ay\u0131klama ve iterasyon i\u00e7in \u00e7ok kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n4. K\u00fcreyi Ba\u015flatma<\/h3>\n
T\u00fcm Vagrantfile ve provisioning betiklerimiz haz\u0131r oldu\u011funa g\u00f6re, art\u0131k tek bir komutla Kubernetes k\u00fcmemizi ba\u015flatabiliriz:<\/p>\n
\nvagrant up\n <\/pre>\n<\/code><\/p>\n
Bu komut, master ve iki worker d\u00fc\u011f\u00fcm\u00fcn\u00fc VirtualBox \u00fczerinde olu\u015fturacak, Ubuntu i\u015fletim sistemini kuracak ve ard\u0131ndan provisioning betiklerini \u00e7al\u0131\u015ft\u0131racakt\u0131r. Bu i\u015flem, internet ba\u011flant\u0131n\u0131z\u0131n h\u0131z\u0131na ve makinenizin performans\u0131na ba\u011fl\u0131 olarak biraz zaman alabilir (genellikle 15-30 dakika). Komut sat\u0131r\u0131nda ilerlemeyi takip edebilirsiniz.<\/p>\n
Kurulum tamamland\u0131\u011f\u0131nda, master d\u00fc\u011f\u00fcmden kubeadm join<\/code> komutunun \u00e7\u0131kt\u0131s\u0131 kubernetes-vagrant<\/code> dizininizin i\u00e7ine join-command.sh<\/code> olarak kaydedilecektir. Worker d\u00fc\u011f\u00fcmler, bu dosyay\u0131 master'dan otomatik olarak al\u0131p k\u00fcreye kat\u0131lmak i\u00e7in kullanacakt\u0131r. T\u00fcm sanal makineler ba\u015flat\u0131l\u0131p yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda, k\u00fcmemiz kullan\u0131ma haz\u0131r hale gelecektir.<\/p>\nK\u00fcme Testi ve Temel Y\u00f6netim: Uygulama Da\u011f\u0131t\u0131m\u0131 ve \u0130zleme<\/h2>\n
K\u00fcmemizi Vagrant arac\u0131l\u0131\u011f\u0131yla ba\u015far\u0131yla ba\u015flatt\u0131ktan sonra, her \u015feyin beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in baz\u0131 temel testler yapmam\u0131z gerekiyor. Bu b\u00f6l\u00fcmde, k\u00fcmemizin durumunu nas\u0131l kontrol edece\u011fimizi, basit bir uygulama da\u011f\u0131tarak nas\u0131l test edece\u011fimizi ve temel Kubernetes y\u00f6netim komutlar\u0131n\u0131 inceleyece\u011fiz.<\/p>\n
1. Kubernetes K\u00fcmesini Kontrol Etme<\/h3>\n
\u00d6ncelikle, SSH arac\u0131l\u0131\u011f\u0131yla master d\u00fc\u011f\u00fcme ba\u011flanal\u0131m. Bu, Kubernetes k\u00fcmesiyle etkile\u015fim kurmak i\u00e7in ana yerimiz olacakt\u0131r, \u00e7\u00fcnk\u00fc kubectl<\/code> komutu master d\u00fc\u011f\u00fcmde yap\u0131land\u0131r\u0131lm\u0131\u015ft\u0131r:<\/p>\n\nvagrant ssh k8s-master\n <\/pre>\n<\/code><\/p>\n
Master d\u00fc\u011f\u00fcm\u00fcn i\u00e7ine girdikten sonra, k\u00fcmemizin d\u00fc\u011f\u00fcmlerini kontrol edebiliriz:<\/p>\n
\nkubectl get nodes\n <\/pre>\n<\/code><\/p>\n
Bu komutun \u00e7\u0131kt\u0131s\u0131, master ve iki worker d\u00fc\u011f\u00fcm\u00fcn\u00fcz\u00fc \"Ready\" (Haz\u0131r) durumunda g\u00f6stermelidir. E\u011fer herhangi bir d\u00fc\u011f\u00fcm \"NotReady\" durumundaysa, provisioning betiklerinde bir sorun veya a\u011f yap\u0131land\u0131rmas\u0131nda bir problem olabilir. Genellikle, k\u0131sa bir s\u00fcre beklemek ve komutu tekrar \u00e7al\u0131\u015ft\u0131rmak sorunu \u00e7\u00f6zebilir, \u00e7\u00fcnk\u00fc bile\u015fenlerin tamamen ba\u015flat\u0131lmas\u0131 biraz zaman alabilir.<\/p>\n
\nNAME STATUS ROLES AGE VERSION\nk8s-master Ready control-plane 5m v1.27.3\nk8s-worker-1 Ready 4m v1.27.3\nk8s-worker-2 Ready 4m v1.27.3\n <\/pre>\n<\/code><\/p>\n
Ayr\u0131ca, k\u00fcmenin i\u00e7indeki t\u00fcm pod'lar\u0131n durumunu kontrol etmek i\u00e7in a\u015fa\u011f\u0131daki komutu kullanabiliriz:<\/p>\n
\nkubectl get pods --all-namespaces\n <\/pre>\n<\/code><\/p>\n
Bu komut, sistem pod'lar\u0131n\u0131 (kube-system namespace'inde \u00e7al\u0131\u015fanlar) ve Flannel gibi CNI pod'lar\u0131n\u0131 g\u00f6stermelidir. Hepsinin \"Running\" (\u00c7al\u0131\u015f\u0131yor) durumunda olmas\u0131 gerekir.<\/p>\n
2. Basit Bir Uygulama Da\u011f\u0131t\u0131m\u0131<\/h3>\n
K\u00fcmemizin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulad\u0131ktan sonra, \u00fczerine basit bir Nginx web sunucusu da\u011f\u0131tarak tam i\u015flevselli\u011fini test edelim. Nginx da\u011f\u0131t\u0131m\u0131 i\u00e7in bir YAML dosyas\u0131 olu\u015ftural\u0131m. Master d\u00fc\u011f\u00fcmde, nginx-deployment.yaml<\/code> ad\u0131nda bir dosya olu\u015fturun ve i\u00e7ine a\u015fa\u011f\u0131daki i\u00e7eri\u011fi yap\u0131\u015ft\u0131r\u0131n:<\/p>\n\n# nginx-deployment.yaml\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n name: nginx-deployment\n labels:\n app: nginx\nspec:\n replicas: 2\n selector:\n matchLabels:\n app: nginx\n template:\n metadata:\n labels:\n app: nginx\n spec:\n containers:\n - name: nginx\n image: nginx:latest\n ports:\n - containerPort: 80\n---\napiVersion: v1\nkind: Service\nmetadata:\n name: nginx-service\nspec:\n selector:\n app: nginx\n ports:\n - protocol: TCP\n port: 80\n targetPort: 80\n type: NodePort\n <\/pre>\n<\/code><\/p>\n
Bu YAML dosyas\u0131, iki adet Nginx pod'u \u00e7al\u0131\u015ft\u0131ran bir Deployment ve bu pod'lar\u0131 d\u0131\u015far\u0131ya a\u00e7an bir NodePort Service tan\u0131mlar. Da\u011f\u0131t\u0131m\u0131 uygulamak i\u00e7in:<\/p>\n
\nkubectl apply -f nginx-deployment.yaml\n <\/pre>\n<\/code><\/p>\n
Da\u011f\u0131t\u0131m\u0131n durumunu kontrol edelim:<\/p>\n
\nkubectl get deployments\nkubectl get pods -o wide\nkubectl get service nginx-service\n <\/pre>\n<\/code><\/p>\n
kubectl get service nginx-service<\/code> komutunun \u00e7\u0131kt\u0131s\u0131, Nginx servisinin bir NodePort \u00fczerinde \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6sterecektir. \u00d6rne\u011fin, \u00e7\u0131kt\u0131da NodePort: 3XXXX\/TCP<\/code> gibi bir de\u011fer g\u00f6receksiniz. Bu, Nginx uygulaman\u0131za herhangi bir worker d\u00fc\u011f\u00fcm\u00fcn IP adresi ve bu port numaras\u0131 \u00fczerinden eri\u015febilece\u011finiz anlam\u0131na gelir.<\/p>\nMaster d\u00fc\u011f\u00fcmden \u00e7\u0131k\u0131n (exit<\/code> yazarak) ve yerel makinenizden bir worker d\u00fc\u011f\u00fcm\u00fcn IP adresini (\u00f6rne\u011fin, 172.16.16.101<\/code>) ve NodePort de\u011ferini kullanarak taray\u0131c\u0131n\u0131zdan veya curl<\/code> ile eri\u015fmeyi deneyin:<\/p>\n\n# Yerel makinenizden (master d\u00fc\u011f\u00fcm\u00fcn d\u0131\u015f\u0131ndan)\ncurl 172.16.16.101:3XXXX # Buradaki 3XXXX, kubectl get service<\/code> \u00e7\u0131kt\u0131s\u0131ndaki NodePort de\u011feridir.\n <\/pre>\n<\/code><\/p>\n
E\u011fer Nginx'in varsay\u0131lan \"Welcome to nginx!\" sayfas\u0131n\u0131 g\u00f6r\u00fcyorsan\u0131z, Kubernetes k\u00fcmeniz ba\u015far\u0131yla \u00e7al\u0131\u015f\u0131yor ve uygulamalar\u0131 da\u011f\u0131tabilir durumdas\u0131n\u0131z demektir! Bu, hem geli\u015ftirme hem de \u00f6\u011frenme s\u00fcre\u00e7leriniz i\u00e7in harika bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/p>\n
\u0130leri D\u00fczey \u0130pu\u00e7lar\u0131 ve En \u0130yi Uygulamalar: Performans ve Geli\u015ftirme<\/h2>\n
Vagrant ile temel bir Kubernetes k\u00fcmesi kurmay\u0131 \u00f6\u011frendik. Ancak, bu kurulumu daha verimli hale getirmek, geli\u015ftirme deneyiminizi zenginle\u015ftirmek ve ger\u00e7ek d\u00fcnya senaryolar\u0131na daha uygun hale getirmek i\u00e7in baz\u0131 ileri d\u00fczey ipu\u00e7lar\u0131 ve en iyi uygulamalar mevcuttur. Bu b\u00f6l\u00fcmde, Vagrantfile'\u0131 \u00f6zelle\u015ftirmekten, a\u011f yap\u0131land\u0131rmas\u0131n\u0131 optimize etmeye ve hata ay\u0131klama tekniklerine kadar \u00e7e\u015fitli konular\u0131 ele alaca\u011f\u0131z.<\/p>\n
1. Vagrantfile'\u0131 \u00d6zelle\u015ftirme: Kaynak Optimizasyonu<\/h3>\n
Yukar\u0131daki \u00f6rnekte her d\u00fc\u011f\u00fcme belirli miktarda RAM ve CPU atad\u0131k. Ancak, projenizin veya makinenizin ihtiya\u00e7lar\u0131na g\u00f6re bu de\u011ferleri ayarlayabilirsiniz. \u00d6rne\u011fin, daha fazla worker d\u00fc\u011f\u00fcmle \u00e7al\u0131\u015f\u0131yorsan\u0131z veya daha fazla bellek t\u00fcketen uygulamalar \u00e7al\u0131\u015ft\u0131r\u0131yorsan\u0131z, ilgili d\u00fc\u011f\u00fcmlerin kaynaklar\u0131n\u0131 art\u0131rman\u0131z gerekebilir:<\/p>\n
\n# Vagrantfile i\u00e7indeki bir \u00f6rnek\nmaster.vm.provider \"virtualbox\" do |vb|\n vb.memory = \"4096\" # 4 GB RAM\n vb.cpus = \"4\" # 4 CPU \u00e7ekirde\u011fi\nend\n\nworker.vm.provider \"virtualbox\" do |vb|\n vb.memory = \"2048\" # 2 GB RAM\n vb.cpus = \"2\" # 2 CPU \u00e7ekirde\u011fi\nend\n <\/pre>\n<\/code><\/p>\n
Uzman \u0130pucu: Sanal makinelere \u00e7ok fazla kaynak atamak, host makinenizin performans\u0131n\u0131 d\u00fc\u015f\u00fcrebilir. Dengeli bir yakla\u015f\u0131m benimseyerek, hem VM'lerin yeterli kayna\u011fa sahip olmas\u0131n\u0131 sa\u011flay\u0131n hem de host makinenizin g\u00fcnl\u00fck g\u00f6revleri i\u00e7in yeterli kayna\u011f\u0131 kalmas\u0131n\u0131 sa\u011flay\u0131n.<\/p>\n
2. A\u011f Yap\u0131land\u0131rmas\u0131 ve Y\u00fck Dengeleme<\/h3>\n
Varsay\u0131lan kurulumumuzda, NodePort servisleri ile uygulamalara eri\u015fiyorduk. Ancak \u00fcretim ortamlar\u0131nda genellikle bir LoadBalancer (Y\u00fck Dengeleyici) kullan\u0131l\u0131r. Vagrant ortam\u0131nda ger\u00e7ek bir donan\u0131m y\u00fck dengeleyiciye sahip olmasak da, MetalLB gibi yaz\u0131l\u0131msal y\u00fck dengeleyicilerle Kubernetes servisleri i\u00e7in ger\u00e7ek LoadBalancer tipi IP adresleri edinebiliriz. MetalLB kurulumu, k\u00fcmenizin servislerini daha tutarl\u0131 ve kolay eri\u015filebilir hale getirir.<\/p>\n
\n# Master d\u00fc\u011f\u00fcmde SSH ile ba\u011flan\u0131p \u00e7al\u0131\u015ft\u0131r\u0131labilir.\n# MetalLB kurulumu i\u00e7in IP adresi aral\u0131\u011f\u0131n\u0131 kendi \u00f6zel a\u011f\u0131n\u0131za g\u00f6re ayarlay\u0131n\nkubectl apply -f https:\/\/raw.githubusercontent.com\/metallb\/metallb\/main\/config\/manifests\/metallb.yaml\n# Daha sonra bir ConfigMap olu\u015fturarak MetalLB i\u00e7in IP aral\u0131\u011f\u0131n\u0131 belirtmeniz gerekir.\n# \u00d6rne\u011fin:\n# apiVersion: v1\n# kind: ConfigMap\n# metadata:\n# namespace: metallb-system\n# name: config\n# data:\n# config: |\n# address-pools:\n# - name: default\n# protocol: layer2\n# addresses:\n# - 172.16.16.200-172.16.16.210 # Vagrant k\u00fcmenizin IP aral\u0131\u011f\u0131na uygun\n <\/pre>\n<\/code><\/p>\n
Bu, NodePort yerine LoadBalancer tipi servisler tan\u0131mlaman\u0131za ve bu servislerin belirlenen IP aral\u0131\u011f\u0131ndan bir IP adresi almas\u0131n\u0131 sa\u011flar.<\/p>\n
3. Kal\u0131c\u0131 Depolama (Persistent Storage) \u00c7\u00f6z\u00fcmleri<\/h3>\n
Vagrant k\u00fcmeniz \u00fczerinde stateful uygulamalar \u00e7al\u0131\u015ft\u0131rmay\u0131 planl\u0131yorsan\u0131z, kal\u0131c\u0131 depolama \u00e7\u00f6z\u00fcmleri entegre etmeniz gerekecektir. Dinamik depolama sa\u011flamak i\u00e7in NFS veya Longhorn gibi \u00e7\u00f6z\u00fcmler pop\u00fclerdir. \u00d6rne\u011fin, NFS Server'\u0131 master d\u00fc\u011f\u00fcme kurup, worker d\u00fc\u011f\u00fcmlerin NFS istemcisi olarak ba\u011flanmas\u0131n\u0131 sa\u011flayabilir ve Kubernetes i\u00e7inde NFS Provisioner<\/code> kullanarak PersistentVolume'lar\u0131 dinamik olarak sa\u011flayabilirsiniz.<\/p>\n4. Hata Ay\u0131klama ve Sorun Giderme<\/h3>\n
Kurulum veya uygulama da\u011f\u0131t\u0131m\u0131 s\u0131ras\u0131nda sorunlarla kar\u015f\u0131la\u015fmak do\u011fald\u0131r. \u0130\u015fte baz\u0131 hata ay\u0131klama ipu\u00e7lar\u0131:<\/p>\n
\n- G\u00fcnl\u00fckleri Kontrol Edin:<\/strong>
vagrant ssh k8s-master<\/code> komutuyla master d\u00fc\u011f\u00fcme ba\u011flan\u0131n ve sudo journalctl -u kubelet<\/code> veya sudo journalctl -u containerd<\/code> komutlar\u0131yla ilgili servislerin g\u00fcnl\u00fcklerini kontrol edin.<\/li>\n- Kubernetes Olaylar\u0131:<\/strong>
kubectl get events --all-namespaces<\/code> komutu, k\u00fcme i\u00e7indeki olaylar\u0131 listeler ve sorunlar\u0131n kayna\u011f\u0131n\u0131 anlaman\u0131za yard\u0131mc\u0131 olabilir.<\/li>\n- Pod A\u00e7\u0131klamalar\u0131:<\/strong> Bir pod sorun ya\u015f\u0131yorsa,
kubectl describe pod <\/code> komutuyla detayl\u0131 bilgilere (olaylar, konteyner durumlar\u0131) ula\u015fabilirsiniz.<\/li>\n- A\u011f Ba\u011flant\u0131s\u0131:<\/strong> D\u00fc\u011f\u00fcmler aras\u0131 a\u011f ba\u011flant\u0131s\u0131n\u0131
ping<\/code> veya curl<\/code> ile test edin. G\u00fcvenlik duvar\u0131 (ufw) ayarlar\u0131n\u0131n kapal\u0131 veya do\u011fru yap\u0131land\u0131r\u0131lm\u0131\u015f oldu\u011fundan emin olun.<\/li>\n<\/ul>\n5. Mobil Uyumlu HTML Geli\u015ftirme Notu<\/h3>\n
Her ne kadar bu makale sunumu sadece <\/code> i\u00e7eri\u011fi sa\u011flasa da, genel olarak web tabanl\u0131 Kubernetes dashboard'lar\u0131 veya kendi geli\u015ftirdi\u011finiz y\u00f6netim aray\u00fczleri i\u00e7in mobil uyumluluk \u00f6nemlidir. CSS media query'ler, farkl\u0131 ekran boyutlar\u0131na ve cihazlara g\u00f6re aray\u00fcz\u00fcn\u00fcz\u00fc adapte etmenizi sa\u011flar. \u0130\u015fte temel bir media query \u00f6rne\u011fi:<\/p>\n\n