Konu ba\u015fl\u0131klar\u0131 s\u0131ras\u0131yla:<\/p>\n
- \n
- Docker Image’i Olu\u015fturma ve Docker Hub \u00dczerine Push Etmek<\/li>\n
- Azure Container Service Kullanarak Kubernetes Cluster’\u0131 Olu\u015fturmak\n
- \n
- SSH RSA Public Key Olu\u015fturma<\/li>\n
- Service Principal Client ID and Secret Olu\u015fturma<\/li>\n
- Kubernetes Cluster’\u0131 Olu\u015fturma<\/li>\n
- Kubernetes Cluster’\u0131na Ba\u011flanmak<\/li>\n
- Kubernetes Cluster’\u0131 \u0130\u00e7erisindeki Bir Pod’da ASP.NET Core RESTful API’\u0131n\u0131 \u00c7al\u0131\u015ft\u0131rma<\/li>\n
- Kubernetes Service ile Pod’u Expose Etmek<\/li>\n
- Kubernetes Deployment Controller’\u0131 Olu\u015fturma ve Expose Etme<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
![\"\"](\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\")
<\/a><\/p>\nNOT<\/strong>: Bu makale i\u00e7erisinde detayl\u0131 olarak\u00a0Docker<\/em> nedir, neden ihtiya\u00e7 duyar\u0131z gibi konulara de\u011finmeyece\u011fim. Bu makale i\u00e7in\u00a0Docker<\/em> hakk\u0131nda biraz bilgiye sahip olman\u0131z gerekmektedir.<\/p><\/blockquote>\n
Bildi\u011fimiz gibi container image’i\u00a0lightweight<\/strong>,\u00a0stand-alone<\/strong>\u00a0ve her an \u00e7al\u0131\u015fmaya haz\u0131r\u00a0<\/strong>application par\u00e7alar\u0131d\u0131r. Container’lar ile uygulamalar\u0131m\u0131z, ayn\u0131 infrastructure alt\u0131nda birbirlerinden izole bir \u015fekilde \u00a0\u00e7al\u0131\u015fabilmektedir. B\u00f6ylece development ve\u00a0staging ortam farkl\u0131l\u0131klar\u0131 birbirlerinden ayr\u0131labilece\u011fi i\u00e7in, olu\u015fabilecek\u00a0conflict’lerin azalt\u0131lmas\u0131na da yard\u0131mc\u0131 olmaktad\u0131r.<\/p>\n
Containerizing i\u015flemi i\u00e7in “ASP.NET Core Serisi 01: Dapper ile RESTful API Tasarlama ve Azure App Services\u2019e Deploy<\/em><\/a>” isimli makale i\u00e7erisinde geli\u015ftirdi\u011fimiz \u00f6rnek projeyi kullanaca\u011f\u0131z. \u00d6rnek projeyi GitHub<\/a><\/em> \u00fczerinden download edelim ve masa\u00fcst\u00fcne unzip i\u015flemini ger\u00e7ekle\u015ftirelim.<\/p>\n
1. B\u00f6l\u00fcm – Docker Image’i Olu\u015fturma ve Docker Hub \u00dczerine Push Etmek<\/h5>\n
NOT<\/strong>: Ger\u00e7ekle\u015ftirece\u011fim i\u015flemler i\u00e7in, Windows<\/strong> <\/em>platformu \u00fczerinde DockerToolbox<\/strong> <\/em>kullanmaktay\u0131m.<\/p><\/blockquote>\n
<\/a><\/p>\nBu a\u015famada ilk olarak, bir image build edebilmemiz i\u00e7in unzip yapt\u0131\u011f\u0131m\u0131z projenin root dizininde, a\u015fa\u011f\u0131daki gibi bir Dockerfile<\/strong> olu\u015ftural\u0131m.<\/p>\n
FROM microsoft\/aspnetcore:1.1\r\nENTRYPOINT [\"dotnet\", \"aspnetcore-rest-api-with-dapper.dll\"]\r\nARG source=.\r\nWORKDIR \/app\r\nEXPOSE 5000\r\nCOPY $source .<\/pre>\n
Dockerfile i\u00e7erisinde base olarak offical compiled ASP.NET Core<\/em> image’ini kullanaca\u011f\u0131m\u0131z\u0131 ve “5000<\/em>” port’u \u00fczerinden ise expose edece\u011fimizi tan\u0131mlad\u0131k. Entrypoint olarak ise, projeyi publish ettikten sonra elde edecek oldu\u011fumuz “aspnetcore-rest-api-with-dapper.dll<\/em>” dosyas\u0131n\u0131 belirttik. \u00a0\u015eimdi projenin root dizinine herhangi bir command tool’u ile girelim ve projeyi a\u015fa\u011f\u0131daki gibi build edelim.<\/p>\n
dotnet build<\/pre>\n
<\/a><\/p>\nNOT<\/strong>: “dotnet restore<\/em>” komutu ile package’lar\u0131 restore etmeyi unutmay\u0131n.<\/p><\/blockquote>\n
Build i\u015fleminin ba\u015far\u0131yla ger\u00e7ekle\u015fmesinden sonra, a\u015fa\u011f\u0131daki komutu kullanarak projeyi publish edelim.<\/p>\n
dotnet publish -c release<\/pre>\n
<\/a><\/p>\nArt\u0131k, publish i\u015fleminin ard\u0131ndan Dockerfile’\u0131 kullanarak bir image build edebiliriz. Image build edebilmemiz i\u00e7in a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131rmam\u0131z yeterli olacakt\u0131r.<\/p>\n
docker build bin\\Release\\netcoreapp1.1\\publish -t aspnetcorerestapionlinux<\/pre>\n
<\/a><\/p>\nPublish sonras\u0131 elde etti\u011fimiz “bin\\Release\\netcoreapp1.1\\publish<\/em>” path’ini kullanarak, “aspnetcorerestapionlinux<\/em>” isminde bir image build ettik. A\u015fa\u011f\u0131daki komutu kullanarak, olu\u015fturulan image’leri g\u00f6rebiliriz.<\/p>\n
docker images<\/pre>\n
<\/a><\/p>\nYukar\u0131daki resimde, “aspnetcorerestapionlinux<\/em>” ismi ile image’in olu\u015ftu\u011funu g\u00f6rebiliriz.<\/p>\n
\u015eimdi, yapt\u0131\u011f\u0131m\u0131z i\u015flemlerin do\u011fru gitti\u011finden emin olabilmek i\u00e7in olu\u015fturmu\u015f oldu\u011fumuz image’i, bir container i\u00e7erisinde a\u015fa\u011f\u0131daki gibi \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n
docker run -d -p 5000:5000 aspnetcorerestapionlinux<\/pre>\n
<\/a><\/p>\nOlu\u015fturmu\u015f oldu\u011fumuz “aspnetcorerestapionlinux<\/em>” image’ini, bir container i\u00e7erisinde “5000<\/em>” port’u \u00fczerinden expose ederek \u00e7al\u0131\u015ft\u0131rd\u0131k. \u015eimdi browser \u00fczerinden “http:\/\/192.168.99.100:5000\/swagger<\/em>” URL’ine girelim ve projenin \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olal\u0131m.<\/p>\n
<\/a><\/p>\nTadaa! Olu\u015fturmu\u015f oldu\u011fumuz image, container i\u00e7erisinde ba\u015far\u0131l\u0131 bir \u015fekilde \u00e7al\u0131\u015fmaktad\u0131r. Buraya kadar olan k\u0131s\u0131mda, ASP.NET Core<\/em> ile geli\u015ftirmi\u015f oldu\u011fumuz RESTful bir API’\u0131n containerizing i\u015flemini tamamlad\u0131k.<\/p>\n
\u015eimdi ise olu\u015fturmu\u015f oldu\u011fumuz bu “aspnetcorerestapionlinux<\/em>” image’ini,\u00a0Docker Hub<\/em> \u00fczerine push edece\u011fiz. Bu sayede Azure Container Service<\/em> i\u00e7erisinde bu image’i pull ederek, Kubernetes<\/em> cluster’\u0131 i\u00e7erisinde \u00e7al\u0131\u015ft\u0131raca\u011f\u0131z. \u00d6ncelikle push i\u015flemini ger\u00e7ekle\u015ftirebilmemiz i\u00e7in, Docker Hub<\/em> account’\u0131na sahip olmam\u0131z gerekmektedir. E\u011fer account’a sahip de\u011filsek, buradan<\/a><\/em> olu\u015fturabiliriz.<\/p>\n
\u0130lk olarak olu\u015fturmu\u015f oldu\u011fumuz image’e, a\u015fa\u011f\u0131daki gibi bir tag eklememiz gerekmektedir.<\/p>\n
docker tag aspnetcorerestapionlinux gokgokalp\/aspnetcorerestapionlinux<\/pre>\n
NOT<\/strong>: “gokgokalp<\/em>” olan k\u0131sm\u0131, kendi Docker Hub<\/em> kullan\u0131c\u0131 ad\u0131n\u0131z ile de\u011fi\u015ftirmeyi unutmay\u0131n.<\/p><\/blockquote>\n
\u015eimdi ise Docker Hub<\/em> \u00fczerine login olmam\u0131z gerekmektedir.<\/p>\n
docker login<\/pre>\n
Login olma i\u015flemi ba\u015far\u0131yla ger\u00e7ekle\u015ftikten sonra a\u015fa\u011f\u0131daki gibi olu\u015fturmu\u015f oldu\u011fumuz image’i, Docker Hub<\/em> \u00fczerine push edelim.<\/p>\n
docker push gokgokalp\/aspnetcorerestapionlinux<\/pre>\n
<\/a><\/p>\n2. B\u00f6l\u00fcm – Azure Container Service Kullanarak Kubernetes Cluster’\u0131 Olu\u015fturmak<\/h5>\n
<\/a><\/p>\nAzure Container Service<\/em>,\u00a0containerize hale getirdi\u011fimiz uygulamalar i\u00e7in basit ve h\u0131zl\u0131 bir \u015fekilde sanal makineler olu\u015fturabilmemizi, yap\u0131land\u0131rabilmemizi ve cluster yap\u0131m\u0131z\u0131 y\u00f6netebilmemizi kolayla\u015ft\u0131rmak i\u00e7in \u00e7\u00f6z\u00fcmler sunmaktad\u0131r. Microsoft<\/em>‘un bir ka\u00e7 ay \u00f6nce\u00a0Kubernetes<\/em> container\u00a0orchestration service’ini de tamamen available hale getirmesiyle beraber, efficiently bir \u015fekilde containerize edilmi\u015f uygulamalar\u0131m\u0131z\u0131 deploy ve on the fly olarak scale edebilmek kolay bir hal alm\u0131\u015ft\u0131r.<\/p>\n
\u015eimdi Azure Container Service<\/em>‘ini kullanarak, basic bir \u015fekilde Kubernetes<\/em> cluster’\u0131 olu\u015fturaca\u011f\u0131z. Cluster olu\u015fturabilmek i\u00e7in \u00f6ncelikle a\u015fa\u011f\u0131daki maddelere ihtiya\u00e7 duymaktay\u0131z:<\/p>\n
- \n
- Azure subscription<\/strong> – “ASP.NET Core Serisi 01<\/em><\/a>” makalesinde, nas\u0131l elde edece\u011fimizden bahsetmi\u015ftim.<\/li>\n
- SSH RSA public key<\/strong> – Virtual machine’lere authenticate olabilmek i\u00e7in olu\u015fturmam\u0131z gerekmektedir.<\/li>\n
- Service Principal client ID and secret<\/strong> –\u00a0Orchestrator olarak Kubernetes<\/em> kullanaca\u011f\u0131m\u0131z i\u00e7in “Azure Active Directory service principal client ID” ye ve “secret” a ihtiyac\u0131m\u0131z var.<\/li>\n<\/ul>\n
Haydi ozaman ba\u015flayal\u0131m.<\/p>\n
2.1 SSH RSA Public Key Olu\u015fturma<\/strong><\/p>\n
Windows<\/em> \u00fczerinde olu\u015fturabilmek i\u00e7in, Git for Windows<\/em>‘un kurulu olmas\u0131 gerekmektedir. E\u011fer kurulu de\u011filse:\u00a0https:\/\/git-for-windows.github.io\/<\/em><\/a><\/p><\/blockquote>\n
Git Bash<\/em>‘i a\u00e7al\u0131m ve a\u015fa\u011f\u0131daki komut sat\u0131r\u0131 ile “openssl.exe<\/em>” yi kullanarak, “myPrivateKey<\/em>” ve “myCert<\/em>”\u00a0certificate’ini olu\u015ftural\u0131m.<\/p>\n
openssl.exe req -x509 -nodes -days 365 -newkey rsa:2048 \\-keyout myPrivateKey.key -out myCert.pem<\/pre>\n
<\/a><\/p>\nBu i\u015flem s\u0131ras\u0131nda size “Country Name, State, E-mail, Organization Name” gibi bir ka\u00e7 bilgi soracakt\u0131r. Gerekli bilgileri girdikten sonra,\u00a0“myPrivateKey<\/em>” ve “myCert<\/em>”\u00a0certificate’i, ilgili path alt\u0131nda olu\u015facakt\u0131r.<\/p>\n
\u015eimdi ise a\u015fa\u011f\u0131daki komutu kullanarak, olu\u015fturmu\u015f oldu\u011fumuz private key ile “myPublicKey<\/em>” ad\u0131nda bir public key olu\u015fturaca\u011f\u0131z.<\/p>\n
openssl.exe rsa -pubout -in myPrivateKey.key -out myPublicKey.key<\/pre>\n
<\/a><\/p>\nPuTTY<\/em> SSH client’\u0131n\u0131 kullanabilmemiz i\u00e7in, ek bir key daha olu\u015fturmam\u0131z gerekmektedir. Bunun i\u00e7in:ddddddd<\/p>\n
openssl rsa -in .\/myPrivateKey.key -out myPrivateKey_rsa<\/pre>\n
<\/a><\/p>\nBununla birlikte “myPrivateKey_rsa<\/em>” isminde bir\u00a0private key daha elde ettik.<\/p>\n
\u015eimdi olu\u015fturmu\u015f oldu\u011fumuz bu “myPrivateKey_rsa<\/em>”\u00a0key’ini kullanarak, Azure<\/em> portal \u00fczerinde Linux<\/em> VM yarat\u0131rken kullanaca\u011f\u0131m\u0131z public key’i olu\u015fturaca\u011f\u0131z. Bunun i\u00e7in \u00f6ncelikle buradan<\/a><\/em>,\u00a0PuTTY<\/em>\u00a0‘i indirelim ve kural\u0131m. Kurulum i\u015fleminin ard\u0131ndan “PuTTYgen” uygulamalas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131ral\u0131m ve “Load” k\u0131sm\u0131ndan olu\u015fturmu\u015f oldu\u011fumuz\u00a0“myPrivateKey_rsa<\/em>” key’ini se\u00e7elim.<\/p>\n
<\/a><\/p>\nYukar\u0131daki resimde g\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi “ssh-rsa” prefix’i ile ba\u015flayan bir public key daha elde etmi\u015f olduk. Makalenin ilerleyen b\u00f6l\u00fcm\u00fcnde kullanabilmek i\u00e7in, bu key bilgisini de kaydedelim.<\/p>\n
2.2\u00a0Service Principal Client ID and Secret Olu\u015fturma<\/strong><\/p>\n
Bu noktada Azure AD (Active Directory)<\/em>\u00a0service principal olu\u015fturma i\u015flemini, portal \u00fczerindeki terminal’den\u00a0<\/i>ger\u00e7ekle\u015ftirece\u011fiz. Azure portal<\/a><\/em>‘a login olduktan sonra, sa\u011f \u00fcst men\u00fcde bulunan “Cloud Shell<\/em>” i a\u00e7al\u0131m.<\/p>\n
<\/a><\/p>\n“Cloud Shell<\/em>” i a\u00e7t\u0131ktan sonra, \u00f6ncelikle a\u015fa\u011f\u0131daki komut ile “aspnetcore-test-restapi<\/em>” ad\u0131nda bir resource group olu\u015ftural\u0131m.<\/p>\n
az group create -n \"aspnetcore-test-restapi\" -l \"westeurope\"<\/pre>\n
Resource group’u olu\u015fturman\u0131n ard\u0131ndan, a\u015fa\u011f\u0131daki komut i\u00e7erisindeki “mySubscriptionID<\/em>” b\u00f6l\u00fcm\u00fcne kendi subscription ID bilgimizi girelim \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n
az ad sp create-for-rbac --role=\"Contributor\" --scopes=\"\/subscriptions\/mySubscriptionID\/resourceGroups\/aspnetcore-test-restapi\"<\/pre>\n
Bu i\u015flemin ard\u0131ndan a\u015fa\u011f\u0131daki gibi bir output elde edece\u011fiz.<\/p>\n
<\/a><\/p>\nBuradaki “appId” yi principal client ID olarak, “password” u ise secret olarak kullanaca\u011f\u0131z.<\/p>\n
2.3 Kubernetes Cluster’\u0131 Olu\u015fturma<\/strong><\/p>\n
- \n
- Azure portal<\/a><\/em>\u00a0\u00fczerine login olal\u0131m.<\/li>\n
- Sol \u00fcst men\u00fcden \u201cNew<\/em><\/strong>\u201d k\u0131sm\u0131na t\u0131klayal\u0131m.<\/li>\n
- A\u00e7\u0131lan men\u00fcden a\u015fa\u011f\u0131daki gibi \u201cContainers > Azure Container Service<\/strong><\/em>\u201d k\u0131sm\u0131n\u0131 se\u00e7elim.
\n
\n<\/a><\/li>\n- “Basics<\/em>” k\u0131sm\u0131nda, resource group alt\u0131ndaki “Use existing”\u00a0butonuna t\u0131klayal\u0131m ve daha \u00f6nce olu\u015fturmu\u015f oldu\u011fumuz resource group olan “aspnetcore-test-restapi<\/em>” \u0131 se\u00e7elim ve di\u011fer alanlar\u0131 da a\u015fa\u011f\u0131daki gibi doldural\u0131m. (Sizler de kendinize uygun doldurabilirsiniz)
\n<\/a><\/li>\n- \u015eimdi ise “Master configuration<\/em>” k\u0131sm\u0131ndan orchestrator gibi \u00f6nemli bilgileri tan\u0131mlayaca\u011f\u0131z. “Orchestrator<\/em>” olarak “Kubernetes<\/em>” i se\u00e7elim ve ard\u0131ndan “DNS name prefix<\/em>” gibi field’lar\u0131 a\u015fa\u011f\u0131daki gibi doldural\u0131m.
<\/a>
\nDevam\u0131nda ise “SSH public key<\/em>” ve “Service principal<\/em>” b\u00f6l\u00fcmlerini yukar\u0131da elde etti\u011fimiz bilgiler do\u011frultusunda tamamlayal\u0131m.<\/li>\n- “Agent configuration<\/em>” b\u00f6l\u00fcm\u00fc \u00fczerinden de demo oldu\u011fu i\u00e7in “Agent count<\/em>” olarak “1” ve “Standard DS2<\/em>” se\u00e7iyorum.
<\/a><\/li>\n<\/ol>\nArt\u0131k bir Kubernetes<\/em> cluster’\u0131na sahibiz.<\/p>\n
2.4 Kubernetes Cluster’\u0131na Ba\u011flanmak<\/strong><\/p>\n
Local makinemizden Kubernetes<\/em> cluster’\u0131na ba\u011flanabilmemiz i\u00e7in, “kubectl<\/em>” i kurmam\u0131z gerekmektedir. Bunun i\u00e7in buradan<\/a><\/em>, ilgili i\u015fletim sistemimize g\u00f6re Azure CLI<\/em>‘\u0131 indirelim ve kural\u0131m. Kurulum i\u015fleminin ard\u0131ndan, command tool a\u00e7al\u0131m ve a\u015fa\u011f\u0131daki komut ile “kubectl<\/em>” in kurulumunu ger\u00e7ekle\u015ftirelim.<\/p>\n
az acs kubernetes install-cli<\/pre>\n
<\/a><\/h6>\n\u015eimdi ise Kubernetes<\/em> cluster configuration bilgilerini download etmemiz gerekmektedir. \u00d6ncelikle a\u015fa\u011f\u0131daki komut ile, portal bilgilerimizi kullanarak Azure<\/em> \u00fczerine login olal\u0131m.<\/p>\n
az login<\/pre>\n
Login olduktan sonra, a\u015fa\u011f\u0131daki komut \u00fczerinde gerekli de\u011fi\u015fiklikleri yapal\u0131m ve \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n
az acs kubernetes get-credentials --resource-group=aspnetcore-test-restapi --name=aspnetcore-container-service --ssh-key-file=C:\\Users\\GOKGOKALP\\myPrivateKey_rsa<\/pre>\n
Cluster configuration bilgilerinin ba\u015far\u0131yla download edildi\u011finden emin olabilmek i\u00e7in, a\u015fa\u011f\u0131daki komutu da \u00e7al\u0131\u015ft\u0131ral\u0131m ve node listesini g\u00f6relim.<\/p>\n
kubectl get nodes<\/pre>\n
<\/a><\/p>\n2.5 Kubernetes Cluster’\u0131 \u0130\u00e7erisindeki Bir Pod’da ASP.NET Core RESTful API’\u0131n\u0131 \u00c7al\u0131\u015ft\u0131rma<\/strong><\/p>\n
Dok\u00fcmantasyonunda da oldu\u011fu gibi, Pod’u tek bir c\u00fcmle ile tan\u0131mlamak gerekirse e\u011fer:<\/p>\n
Kubernetes<\/em> i\u00e7erisindeki k\u00fc\u00e7\u00fck, deployable\u00a0computing birimleridir.<\/p><\/blockquote>\n
Pod, bir veya birden fazla application container’lar\u0131n\u0131 i\u00e7erebilmektedir. \u015eimdi\u00a0Kubernetes<\/em> cluster’\u0131 i\u00e7erisinde bir pod olu\u015fturabilmemiz i\u00e7in, projenin root klas\u00f6r\u00fc alt\u0131nda “aspnetcore-rest-api-pod.yaml<\/em>” ad\u0131nda a\u015fa\u011f\u0131daki gibi bir YAML<\/em> file’\u0131 tan\u0131mlayal\u0131m.<\/p>\n
apiVersion: v1\r\nkind: Pod\r\nmetadata:\r\n name: aspnetcore-restapi\r\n labels:\r\n app: aspnetcore-restapi\r\nspec:\r\n containers:\r\n - name: aspnetcore-container\r\n image: \"gokgokalp\/aspnetcorerestapionlinux\"\r\n ports:\r\n - containerPort: 5000<\/pre>\n
Yukar\u0131da tan\u0131mlam\u0131\u015f oldu\u011fumuz\u00a0YAML<\/em> file’\u0131 i\u00e7erisindeki “image<\/em>” k\u0131sm\u0131na, Docker<\/em> repo’ya push yapt\u0131\u011f\u0131m\u0131z image’i belirtiyoruz. Hat\u0131rlarsak API<\/em>‘\u0131 container i\u00e7erisinde de “5000<\/em>” port’u \u00fczerinden expose etmi\u015ftik.<\/p>\n
\u015eimdi a\u015fa\u011f\u0131daki komutu, projenin root dizini alt\u0131nda command tool’u \u00fczerinden \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n
kubectl create -f aspnetcore-rest-api-pod.yaml<\/pre>\n
<\/a><\/p>\nG\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi pod’u ba\u015far\u0131yla olu\u015fturduk. \u015eimdi a\u015fa\u011f\u0131daki komut ile olu\u015fturmu\u015f oldu\u011fumuz pod’a bir bakal\u0131m.,<\/p>\n
kubectl get pods<\/pre>\n
<\/a><\/p>\nYukar\u0131daki resimde olu\u015fturmu\u015f oldu\u011fumuz
- Sol \u00fcst men\u00fcden \u201cNew<\/em><\/strong>\u201d k\u0131sm\u0131na t\u0131klayal\u0131m.<\/li>\n
- SSH RSA public key<\/strong> – Virtual machine’lere authenticate olabilmek i\u00e7in olu\u015fturmam\u0131z gerekmektedir.<\/li>\n
- Azure subscription<\/strong> – “ASP.NET Core Serisi 01<\/em><\/a>” makalesinde, nas\u0131l elde edece\u011fimizden bahsetmi\u015ftim.<\/li>\n
![\"\"](\"\/wp-content\/uploads\/2017\/07\/asp.net-core-kubernetes-azure-cloud-service.jpg\")
<\/a><\/p>\n