Durum b\u00f6yle olunca, yeni geli\u015ftirdi\u011fimiz uygulamalar\u0131n olabildi\u011fince containerize edilmi\u015f cloud-native uygulamalar\u0131 olmas\u0131na gayret g\u00f6steriyoruz. Kubernetes<\/strong> gibi container-orchestration platform’lar\u0131 ile de, uygulamalar\u0131n y\u00f6netim i\u015flemlerini ger\u00e7ekle\u015ftiriyoruz.<\/p>\n .NET Core<\/em> ile yeni geli\u015ftirdi\u011fimiz uygulamalar i\u00e7in kubernetes gibi platform’lara migration i\u015flemleri kolayl\u0131kla yap\u0131labiliyorken, bu s\u00fcre\u00e7 .NET Framework<\/em> ile geli\u015ftirilmi\u015f olan mevcut uygulamalar i\u00e7in biraz daha zorlu olabiliyor.<\/p>\n Genelde uygulamalar\u0131n \u00f6ncelikle .NET Core<\/em>‘a transformation i\u015flemi olduk\u00e7a tercih edilen bir se\u00e7enek olabiliyorken, bazen de zaman ve maliyetler g\u00f6z \u00f6n\u00fcnde al\u0131nd\u0131\u011f\u0131nda maalesef bir se\u00e7enek olam\u0131yor.<\/p>\n Bu makale kapsam\u0131nda ise mevcut .NET Framework<\/em> uygulamalar\u0131m\u0131z\u0131, redesign\/redevelopment yapmadan nas\u0131l containerize edilmi\u015f bir \u015fekilde Azure Kubernetes Service<\/strong><\/em> \u00fczerinde host edebiliz konusuna de\u011finmek istiyorum.<\/p>\n Azure Kubernetes Service<\/em> \u00fczerinde mevcut .NET Framework<\/em> uygulamalar\u0131n\u0131, .NET Core’a port etmeden windows container’lar olu\u015fturarak host edebilmek m\u00fcmk\u00fcn.<\/p>\n Sadece .NET Core<\/em>‘a oranla base image size’\u0131, container i\u00e7erisinde Windows Server Core<\/em> image’i kullan\u0131ld\u0131\u011f\u0131 i\u00e7in olduk\u00e7a b\u00fcy\u00fck durumda. Neyseki 2019 y\u0131l\u0131 sonlar\u0131nda ise bu image size’\u0131, %40<\/strong> gibi ciddi bir oranda daha k\u00fc\u00e7\u00fck bir hale getirildi. Bu konu hakk\u0131ndaki detayl\u0131 bilgiye, buradan<\/a> <\/em>eri\u015febilirsiniz.<\/p>\n \u00d6ncelikle AKS <\/em>\u00fczerinde Windows Server <\/em>container’lar olu\u015fturabilmek ve kullanabilmek i\u00e7in, “aks-preview CLI<\/em>” extension’\u0131n\u0131n ve “WindowsPreview<\/em>” feature’\u0131n\u0131n etkinle\u015ftirilmesi gerekiyor.<\/p>\n Bu feature ile node pool i\u00e7erisine, windows server node’lar ekleyebilece\u011fiz.<\/p>\n Bunun i\u00e7in buraya<\/a><\/em> t\u0131klayarak, “Install aks-preview CLI extension<\/em>” ve “Register Windows preview feature<\/em>” ba\u015fl\u0131klar\u0131 alt\u0131ndaki i\u015flemleri ger\u00e7ekle\u015ftirelim.<\/p>\n NOT<\/strong><\/em>: Azure subscription’\u0131n\u0131n i\u00e7erisinde “WindowsPreview<\/em>” feature’\u0131n\u0131n etkinle\u015ftirilmesi, birka\u00e7 dakika s\u00fcrebilir.<\/p><\/blockquote>\n Extension ve feature’\u0131n etkinle\u015ftirme i\u015fleminden sonra, a\u015fa\u011f\u0131daki gibi bir resource group olu\u015fturarak i\u00e7erisinde AKS<\/em> cluster olu\u015fturma i\u015flemine CLI<\/em> yard\u0131m\u0131yla ba\u015flayabiliriz.<\/p>\n NOT<\/strong><\/em>: \u00d6ncesinde CLI<\/em> \u00fczerinden ilgili Azure <\/em>subscription’a login olmay\u0131 unutmay\u0131n.<\/p><\/blockquote>\n AKS cluster olu\u015fturma i\u015flemi ba\u015far\u0131yla tamamland\u0131ktan sonra, a\u015fa\u011f\u0131daki gibi bir response g\u00f6r\u00fcyor olmal\u0131y\u0131z.<\/p>\n \u015eimdi olu\u015fturdu\u011fumuz cluster i\u00e7erisine windows node ekleyebilmek i\u00e7in, a\u015fa\u011f\u0131daki komut sat\u0131r\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmam\u0131z gerekmektedir.<\/p>\n Windows node ekleme i\u015flemi tamamland\u0131ktan sonra, cluster’a ba\u011flanabilmemiz i\u00e7in a\u015fa\u011f\u0131daki gibi kubectl’i configure edelim.<\/p>\n Ard\u0131ndan eklemi\u015f oldu\u011fumuz node’lar\u0131 “OS<\/em>” label’\u0131 ile g\u00f6rebilmek i\u00e7in ise, a\u015fa\u011f\u0131daki komut sat\u0131r\u0131n\u0131 kullanal\u0131m.<\/p>\n Yukar\u0131daki resimde de g\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi, windows node ba\u015far\u0131yla eklenmi\u015f durumda. B\u00f6ylece windows node’lu AKS<\/em> cluster olu\u015fturma i\u015flemini tamamlam\u0131\u015f olduk.<\/p>\n Ben \u00f6rnek ama\u00e7l\u0131 “MyOldTodoAPP<\/em>” ad\u0131nda basit bir ASP.NET Framework Web Application(4.8)<\/em> projesi olu\u015fturaca\u011f\u0131m. Dilerseniz siz mevcut .NET Framework<\/strong> uygulamalar\u0131n\u0131z\u0131 kullanabilirsiniz.<\/p>\n Uygulamay\u0131 dockerize etmeden \u00f6nce, build ve publish i\u015flemlerini a\u015fa\u011f\u0131daki gibi container d\u0131\u015f\u0131nda ger\u00e7ekle\u015ftirelim.<\/p>\n Container d\u0131\u015far\u0131s\u0131nda build i\u015flemi, windows container case’i i\u00e7in daha do\u011fru bir tercih olacakt\u0131r.<\/p>\n Publish i\u015fleminden sonra, ilgili publish folder’\u0131 alt\u0131nda a\u015fa\u011f\u0131daki gibi bir “Dockerfile<\/em>” olu\u015ftural\u0131m.<\/p>\n Burada dikkat etmemiz gereken tek nokta, kullanacak oldu\u011fumuz base image OS<\/em> versiyonunun, host OS<\/em> versiyonu ile uyumlu olmas\u0131d\u0131r. Detayl\u0131 bilgiye ise, buradan<\/a><\/em> eri\u015febilirsiniz.<\/p>\n Windows node’un OS<\/em> versiyonuna ise, Azure<\/em> portal’dan veya a\u015fa\u011f\u0131daki komut sat\u0131r\u0131 \u00fczerinden eri\u015filebilmektedir.<\/p>\n Bu base image ile, “.NET Framework Web<\/em>“, “MVC<\/em>“, “Web API<\/em>” ve “SignalR<\/em>” uygulamalar\u0131 container i\u00e7erisinde \u00e7al\u0131\u015ft\u0131r\u0131labilmekte.<\/p>\n Ayr\u0131ca “ASPNET<\/em>” base image’i i\u00e7erisinde IIS<\/em> process’i “entrypoint” olarak configure edildi\u011fi i\u00e7in, dockerfile i\u00e7erisinde bir entrypoint configure etmedik.<\/p>\n \u015eimdi uygulamay\u0131 dockerize etmeye ba\u015flayabiliriz. Bunun i\u00e7in, ilgili publish folder path’ine girerek, CLI<\/em> \u00fczerinden a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n AKS<\/em>‘e deploy etmeden \u00f6nce her \u015feyin do\u011fru gitti\u011finden emin olabilmek i\u00e7in, dockerize etti\u011fimiz uygulamay\u0131 “8080<\/em>” port’u \u00fczerinden a\u015fa\u011f\u0131daki gibi \u00e7al\u0131\u015ft\u0131r\u0131p test edelim.<\/p>\n Her \u015fey yolunda gitti ise, a\u015fa\u011f\u0131daki gibi default ASP.NET<\/em> response’unu g\u00f6r\u00fcyor olmal\u0131y\u0131z.<\/p>\n \u015eimdi container’\u0131 a\u015fa\u011f\u0131daki gibi tag’leyip, ard\u0131ndan container registry’e g\u00f6nderelim.<\/p>\n Olu\u015fturmu\u015f oldu\u011fumuz container’\u0131 AKS<\/em>‘e deploy edebilmek i\u00e7in, a\u015fa\u011f\u0131daki gibi “deploy-to-aks<\/em>” ad\u0131nda bir “yaml<\/em>” file’\u0131 olu\u015ftural\u0131m.<\/p>\n Burada \u00f6nemli olan nokta ise “spec<\/em>” alt\u0131ndaki “nodeSelector<\/em>” de\u011ferinin, “windows<\/em>” olarak set edilmi\u015f olmas\u0131d\u0131r. B\u00f6ylece container, windows olan node pool i\u00e7erisinde \u00e7al\u0131\u015ft\u0131r\u0131lacakt\u0131r. Ayr\u0131ca “containers<\/em>” alt\u0131ndaki “image<\/em>” de\u011ferini de, tag’ledi\u011fimiz container de\u011feri ile g\u00fcncellemeyi unutmayal\u0131m.<\/p>\n \u015eimdi olu\u015fturmu\u015f oldu\u011fumuz bu yaml file’\u0131n\u0131, CLI<\/em> \u00fczerinden a\u015fa\u011f\u0131daki gibi execute edelim ve deployment i\u015flemini ba\u015flatal\u0131m.<\/p>\n Ard\u0131ndan a\u015fa\u011f\u0131daki komut ile de ilgili pod’un, “Running<\/em>” durumuna gelmesini bekleyelim. AKS<\/em> ilgili container image’ini ilk kez \u00e7ekece\u011fi ve ilgili image size’\u0131 biraz b\u00fcy\u00fck oldu\u011fu i\u00e7in, bu i\u015flem birka\u00e7 dakika s\u00fcrebilir.<\/p>\n Container “Running<\/em>” status’\u00fcne ge\u00e7tikten sonra ise, container’\u0131n expose oldu\u011fu load-balancer IP<\/em> adresini de a\u015fa\u011f\u0131daki komut vas\u0131tas\u0131yla al\u0131p, browser vas\u0131tas\u0131yla test edelim.<\/p>\n G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi external IP<\/em> adresi \u00fczerinden ba\u015far\u0131yla containerize etti\u011fimiz .NET Framework<\/strong> uygulamas\u0131na AKS<\/em> \u00fczerinden eri\u015febildik.<\/p>\n Windows node \u00f6zelli\u011fi AKS<\/em> i\u00e7in her ne kadar \u015fimdilik preview olsa da, san\u0131r\u0131m \u00f6n\u00fcm\u00fczdeki birka\u00e7 ay i\u00e7erisinde global available hale getirilmesi bekleniyor. Ayr\u0131ca k\u0131smi de olsa, Microsoft<\/em> taraf\u0131ndan m\u00fc\u015fteri deste\u011fi de verilmektedir. Bence, eski uygulamalar\u0131m\u0131z\u0131 herhangi bir ekstra efor sarfetmeden containerize edebilmek i\u00e7in harika bir se\u00e7enek.<\/p>\n https:\/\/docs.microsoft.com\/en-us\/azure\/aks\/windows-container-cli?WT.mc_id=AZ-MVP-5003382<\/em><\/a> G\u00fcn\u00fcm\u00fcz teknoloji \u00e7a\u011f\u0131nda, \u00f6zellikle b\u00fcy\u00fck \u00f6l\u00e7ekli firmalar i\u00e7in uygulamalar\u0131 cloud ortam\u0131nda host etmenin ne kadar da \u00f6nemli oldu\u011funu hepimiz biliyoruz. Bir \u00e7ok anket verilerine g\u00f6re de, \u00f6zellikle ge\u00e7ti\u011fimiz 2 y\u0131l i\u00e7erisinde hem public hem de private cloud kullan\u0131m oranlar\u0131 olduk\u00e7a artm\u0131\u015f durumda. Ba\u015fl\u0131ca birka\u00e7 sebebi…<\/p>\n![\"\"](\"\/wp-content\/uploads\/2020\/01\/cloud-computing.png\")
<\/a>
\nREF<\/strong>: https:\/\/vmokshagroup.com\/wp-content\/uploads\/2015\/08\/Save-money-date-and-time-using-cloud.png<\/code><\/em><\/p>\nPeki, ya mevcut uygulamalar?<\/h2>\n
.NET Framework Uygulamalar\u0131n\u0131 AKS’e Migrate Etmek<\/h2>\n
<\/a><\/p>\nAKS Cluster’\u0131n\u0131n Olu\u015fturulmas\u0131<\/h3>\n
az group create -n my-aks-rg -l westeurope<\/pre>\n
az aks create \\\r\n --kubernetes-version 1.14.7 \\\r\n --resource-group my-aks-rg \\\r\n --name my-test-aks \\\r\n --node-vm-size Standard_D2_v2 \\\r\n --node-count 1 \\\r\n --max-pods=250 \\\r\n --location westeurope \\\r\n --generate-ssh-keys \\\r\n --windows-admin-username testadmin \\\r\n --windows-admin-password P@ssw0rd1234 \\\r\n --vm-set-type VirtualMachineScaleSets \\\r\n --network-plugin azure\r\n<\/pre>\n
<\/a><\/p>\naz aks nodepool add \r\n --resource-group my-aks-rg \\\r\n --cluster-name my-test-aks \\ \r\n --os-type Windows\r\n --name npool2 \\\r\n --node-vm-size Standard_D2_v2 \\\r\n --node-count 1 \\\r\n --kubernetes-version 1.14.7<\/pre>\n
az aks get-credentials --resource-group my-aks-rg --name my-test-aks<\/pre>\n
kubectl get nodes --label-columns beta.kubernetes.io\/os<\/pre>\n
<\/a><\/p>\nASP.NET Framework Web Uygulamas\u0131n\u0131n Containerize Edilmesi<\/h3>\n
<\/a><\/p>\nFROM mcr.microsoft.com\/dotnet\/framework\/aspnet:4.8-20191210-windowsservercore-ltsc2019\r\nCOPY . \/inetpub\/wwwroot<\/pre>\n
kubectl get nodes -o wide\r\n\r\nNAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME\r\naks-nodepool1-42915174-vmss000000 Ready agent 3d11h v1.14.7 10.240.0.4 Ubuntu 16.04.6 LTS 4.15.0-1066-azure docker:\/\/3.0.8\r\naksnpool2000000 Ready agent 2d12h v1.14.7 10.240.0.255 Windows Server 2019 Datacenter 10.0.17763.737 docker:\/\/19.3.2<\/pre>\n
docker build -t my-existing-app .<\/pre>\n
<\/a><\/p>\ndocker run -d -p 8080:80 my-existing-app<\/pre>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nContainer’\u0131n AKS’e Deployment \u0130\u015flemi<\/h3>\n
apiVersion: apps\/v1\r\nkind: Deployment\r\nmetadata:\r\n name: sample\r\n labels:\r\n app: sample\r\nspec:\r\n replicas: 1\r\n template:\r\n metadata:\r\n name: sample\r\n labels:\r\n app: sample\r\n spec:\r\n nodeSelector:\r\n \"beta.kubernetes.io\/os\": windows\r\n containers:\r\n - name: my-app\r\n image: mytestaksregistry.azurecr.io\/my-existing-app:1.0\r\n resources:\r\n limits:\r\n cpu: 1\r\n memory: 800M\r\n requests:\r\n cpu: .1\r\n memory: 300M\r\n ports:\r\n - containerPort: 80\r\n selector:\r\n matchLabels:\r\n app: sample\r\n---\r\napiVersion: v1\r\nkind: Service\r\nmetadata:\r\n name: sample\r\nspec:\r\n type: LoadBalancer\r\n ports:\r\n - protocol: TCP\r\n port: 80\r\n selector:\r\n app: sample<\/pre>\n
kubectl apply -f deploy-to-aks.yaml<\/em><\/pre>\n
kubectl get pods -w<\/pre>\n
<\/a><\/p>\nkubectl get svc<\/pre>\n
<\/a><\/p>\n<\/a><\/p>\nSonu\u00e7<\/h2>\n
Referanslar<\/h2>\n
\nhttps:\/\/docs.microsoft.com\/en-us\/aspnet\/mvc\/overview\/deployment\/docker-aspnetmvc?WT.mc_id=AZ-MVP-5003382<\/em><\/a><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"