{"id":83787,"date":"2020-06-03T07:42:26","date_gmt":"2020-06-03T05:42:26","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/devoxx-uk-kubernetes-v-prodakshene-blue-green-deployment-avtomasshtabirovanie-i-avtomatizacziya-razvertyvaniya-chast-2"},"modified":"2020-06-03T07:42:26","modified_gmt":"2020-06-03T05:42:26","slug":"devoxx-uk-kubernetes-v-prodakshene-blue-green-deployment-avtomasshtabirovanie-i-avtomatizacziya-razvertyvaniya-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devoxx-uk-kubernetes-v-prodakshene-blue-green-deployment-avtomasshtabirovanie-i-avtomatizacziya-razvertyvaniya-chast-2","title":{"rendered":"DEVOXX UK. Kubernetes n\u00eb prodhim: Blue\/Green deployment, automatik\u00eb dhe automatizimi i implementimit. Pjesa 2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Kubernetes \u00ebsht\u00eb nj\u00eb mjet i shk\u00eblqyer p\u00ebr t\u00eb nisur konteiner\u00ebt Docker n\u00eb nj\u00eb mjedis prodhimi t\u00eb klasterizuar. Megjithat\u00eb, ekzistojn\u00eb detyra q\u00eb Kubernetes nuk mund t'i zgjidh\u00eb. Kur b\u00ebhet fjal\u00eb p\u00ebr dispunimin e shpesht\u00eb n\u00eb mjedisin e pun\u00ebs, na nevojitet nj\u00eb proces i plot\u00eb i automatizuar i Blue\/Green deployment p\u00ebr t\u00eb shmangur ndalimet, i cili gjithashtu k\u00ebrkon trajtimin e k\u00ebrkesave HTTP nga jasht\u00eb dhe shkarkimin e SSL. Kjo k\u00ebrkon integrimin me nj\u00eb balancues ngarkese, si ha-proxy. Nj\u00eb detyr\u00eb tjet\u00ebr \u00ebsht\u00eb shkall\u00ebzimi gjysm\u00eb-automatizuar i vet\u00eb klasterit Kubernetes gjat\u00eb pun\u00ebs n\u00eb nj\u00eb mjedis cloud, p\u00ebr shembull, zvog\u00eblimi i pjessh\u00ebm i klasterit gjat\u00eb nat\u00ebs.<\/p>\n

Megjith\u00ebse Kubernetes nuk ka k\u00ebto funksione menj\u00ebher\u00eb \"nga kutia\", ai ofron nj\u00eb API t\u00eb cilin mund ta shfryt\u00ebzoni p\u00ebr t\u00eb zgjidhur ngjashme detyra. Mjetet p\u00ebr automatizimin e Blue\/Green deployment dhe shkall\u00ebzimin e klasterit Kubernetes jan\u00eb zhvilluar n\u00eb kuad\u00ebr t\u00eb projektit Cloud RTI, i cili \u00ebsht\u00eb nd\u00ebrtuar mbi open-source.<\/p>\n

N\u00eb k\u00ebt\u00eb artikull, transkriptim video, flitet p\u00ebr m\u00ebnyr\u00ebn se si t\u00eb konfiguroni Kubernetes s\u00eb bashku me komponent\u00ebt e tjer\u00eb open-source p\u00ebr t\u00eb krijuar nj\u00eb mjedis t\u00eb gatsh\u00ebm p\u00ebr prodhim, i cili pa ndalime n\u00eb prodhim pranon kodin nga angazhimi git commit.<\/p>\n

\"DEVOXX<\/a><\/noindex><\/p>\n

DEVOXX UK. Kubernetes n\u00eb prodhim: Blue\/Green deployment, automatik shkall\u00ebzim dhe automatizimi i dispunimit. Pjesa 1<\/a><\/noindex><\/p>\n

Pra, pasi keni fituar akses n\u00eb aplikacionet tuaja nga bota e jashtme, mund t\u00eb filloni konfigurimin e plot\u00eb t\u00eb automatizimit, q\u00eb do t\u00eb thot\u00eb ta \u00e7oni at\u00eb n\u00eb nj\u00eb faz\u00eb ku mund t\u00eb kryeni git commit dhe t\u00eb siguroheni q\u00eb ky git commit p\u00ebrfundon n\u00eb prodhim. Natyrisht, gjat\u00eb realizimit t\u00eb k\u00ebtyre hapave, gjat\u00eb dispunimit, nuk duam t\u00eb hasim ndalime. Pra, \u00e7do automatizim n\u00eb Kubernetes fillon me API. <\/p>\n

\"DEVOXX
\n
\nKubernetes nuk \u00ebsht\u00eb mjeti q\u00eb mund t\u00eb p\u00ebrdoret produktivisht \"drejt nga kutia\". Sigurisht, mund ta b\u00ebni k\u00ebt\u00eb, t\u00eb p\u00ebrdorni kubectl etj., por prap\u00ebseprap\u00eb, API \u00ebsht\u00eb gj coisa m\u00eb interesante dhe e dobishme e k\u00ebsaj platforme. Duke p\u00ebrdorur API si nj\u00eb set funksionesh, mund t\u00eb aksesoni praktikisht gjith\u00e7ka q\u00eb d\u00ebshironi t\u00eb b\u00ebni n\u00eb Kubernetes. Vet\u00eb kubectl gjithashtu p\u00ebrdor REST API. <\/p>\n

Kjo \u00ebsht\u00eb nj\u00eb API REST, prandaj mund t\u00eb p\u00ebrdorni \u00e7do gjuh\u00eb dhe mjet p\u00ebr t\u00eb punuar me t\u00eb, megjithat\u00eb bibliotekat e p\u00ebrdoruesve do ta leht\u00ebsojn\u00eb ndjesh\u00ebm jet\u00ebn tuaj. Ekipi im ka shkruar 2 t\u00eb tilla: nj\u00eb p\u00ebr Java \/ OSGi dhe nj\u00eb p\u00ebr Go. E dyta nuk p\u00ebrdoret shpesh, por n\u00eb \u00e7do rast keni k\u00ebto gj\u00ebra t\u00eb dobishme n\u00eb dispozicionin tuaj. Ato p\u00ebrb\u00ebjn\u00eb nj\u00eb projekt pjes\u00ebrisht me licenc\u00eb open-source. Ekzistojn\u00eb shum\u00eb biblioteka t\u00eb tilla p\u00ebr gjuh\u00eb t\u00eb ndryshme, k\u00ebshtu q\u00eb mund t\u00eb zgjidhni ato m\u00eb t\u00eb p\u00ebrshtatshme. <\/p>\n

\"DEVOXX
\n
\nPra, p\u00ebrpara se t\u00eb nisim automatizimin e p\u00ebrhapjes, \u00ebsht\u00eb e nevojshme t\u00eb sigurohemi se ky proces nuk do t\u00eb privohet nga ndonj\u00eb pezullim. P\u00ebr shembull, ekipi yn\u00eb b\u00ebn shp\u00ebrndarjen n\u00eb prodhim n\u00eb mes t\u00eb dit\u00ebs, kur njer\u00ebzit e p\u00ebrdorin aplikacionet n\u00eb maksimum, prandaj \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme t\u00eb shmangen vonesat n\u00eb k\u00ebt\u00eb proces. P\u00ebr t\u00eb shmangur pezullimet, p\u00ebrdoren 2 metoda: shp\u00ebrndarja blue\/green ose rifreskimi i vazhduesh\u00ebm rolling update. N\u00eb rastin e fundit, n\u00ebse keni 5 replika t\u00eb aplikacionit, ato p\u00ebrdit\u00ebsohen nj\u00eb pas nj\u00eb. Ky metod \u00ebsht\u00eb shum\u00eb efektiv, por nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm n\u00ebse gjat\u00eb procesit t\u00eb p\u00ebrhapjes keni versione t\u00eb ndryshme t\u00eb aplikacionit t\u00eb ekzekutuar nj\u00ebkoh\u00ebsisht. N\u00eb k\u00ebt\u00eb rast, mund t\u00eb p\u00ebrdit\u00ebsoni nd\u00ebrfaqen e p\u00ebrdoruesit nd\u00ebrsa backend po punon me versionin e vjet\u00ebr, duke e ndaluar funksionimin e aplikacionit. Prandaj, nga pik\u00ebpamja e programimit, puna n\u00eb kushte t\u00eb till\u00eb \u00ebsht\u00eb mjaft sfiduese. <\/p>\n

Kjo \u00ebsht\u00eb nj\u00eb nga arsyet pse ne preferojm\u00eb t\u00eb p\u00ebrdorim shp\u00ebrndarjen blue\/green p\u00ebr automatizimin e shp\u00ebrndarjes s\u00eb aplikacioneve tona. Me k\u00ebt\u00eb metod\u00eb, duhet t\u00eb siguroheni se n\u00eb nj\u00eb moment t\u00eb caktuar \u00ebsht\u00eb aktive vet\u00ebm nj\u00eb version i aplikacionit. <\/p>\n

Mekanizmi i shp\u00ebrndarjes blue\/green duket si m\u00eb posht\u00eb. Ne marrim trafik p\u00ebr aplikacionet tona p\u00ebrmes ha-proxy, i cili e drejton at\u00eb te replika q\u00eb jan\u00eb aktive t\u00eb aplikacionit t\u00eb t\u00eb nj\u00ebjt\u00ebs version. <\/p>\n

Kur p\u00ebr t'u kryer nj\u00eb dep\u00ebrtim t\u00eb ri, ne p\u00ebrdorim Deployer, i cili merr komponent\u00ebt e rinj dhe b\u00ebn deploy t\u00eb versionit t\u00eb ri. B\u00ebrja deploy e versionit t\u00eb ri t\u00eb aplikacionit do t\u00eb thot\u00eb se nj\u00eb grup i ri replikash 'ngrihet', pas s\u00eb cil\u00ebs k\u00ebto replika t\u00eb versionit t\u00eb ri fillojn\u00eb n\u00eb nj\u00eb pod t\u00eb ri, t\u00eb ve\u00e7ant\u00eb. Megjithat\u00eb, ha-proxy nuk ka informacion p\u00ebr to dhe p\u00ebr momentin nuk i drejton asnj\u00eb ngarkes\u00eb pune.<\/p>\n

Prandaj, n\u00eb radh\u00eb t\u00eb par\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb kryhet nj\u00eb kontroll funksionaliteti p\u00ebr versionet e reja t\u00eb health checking, p\u00ebr t\u00eb siguruar q\u00eb replikat jan\u00eb gati t\u00eb sh\u00ebrbejn\u00eb ngarkes\u00ebn.<\/p>\n

\"DEVOXX
\n
\nT\u00eb gjitha komponent\u00ebt e deploy-it duhet t\u00eb mb\u00ebshtesin nj\u00eb form\u00eb t\u00eb health check. Kjo mund t\u00eb jet\u00eb nj\u00eb verifikim shum\u00eb i thjesht\u00eb HTTP me nj\u00eb thirrje, kur merrni nj\u00eb kod me status 200, ose nj\u00eb kontroll m\u00eb t\u00eb thell\u00eb, ku kontrolloni lidhjen e replikave me baz\u00ebn e t\u00eb dh\u00ebnave dhe sh\u00ebrbime t\u00eb tjera, q\u00eb lidhjet e mjedisit dinamik jan\u00eb t\u00eb q\u00ebndrueshme, dhe n\u00ebse gjith\u00e7ka ngrihet dhe funksionon n\u00eb m\u00ebnyr\u00eb t\u00eb sakt\u00eb. Ky proces mund t\u00eb jet\u00eb mjaft i komplikuar. <\/p>\n

\"DEVOXX
\n
\nPas konfirmimit t\u00eb funksionimit nga sistemi p\u00ebr t\u00eb gjitha replikat e p\u00ebrdit\u00ebsuara, Deployer do t\u00eb azhurnoj\u00eb konfigurimin dhe do t'i jap\u00eb confd-in e duhur, i cili do t\u00eb ri-konfiguroj\u00eb ha-proxy. <\/p>\n

\"DEVOXX
\n
\nVet\u00ebm pas k\u00ebsaj, trafiku do t\u00eb drejtohet n\u00eb pod-in me replikat e versionit t\u00eb ri, dhe pod-i i vjet\u00ebr do t\u00eb largohet. <\/p>\n

\"DEVOXX
\n
\nKy mekaniz\u00ebm nuk \u00ebsht\u00eb nj\u00eb ve\u00e7ori e Kubernetes. Koncepti i Blue\/green deployment ekziston p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb dhe gjithmon\u00eb ka p\u00ebrdorur nj\u00eb balancues ngarkese. Fillimisht, ju drejtoni t\u00eb gjith\u00eb trafikun n\u00eb versionin e vjet\u00ebr t\u00eb aplikacionit, dhe pas p\u00ebrdit\u00ebsimit, plot\u00ebsisht e transferoni at\u00eb n\u00eb versionin e ri. Ky parim p\u00ebrdoret jo vet\u00ebm n\u00eb Kubernetes.<\/p>\n

Tani do t'ju prezantoj nj\u00eb komponent t\u00eb ri t\u00eb deploy-it \u2013 Deployer, i cili kryen kontrollin e funksionalitetit, ri-konfiguron proxy dhe k\u00ebshtu me radh\u00eb. Ky \u00ebsht\u00eb nj\u00eb koncept q\u00eb nuk lidhet me bot\u00ebn e jashtme dhe ekziston brenda Kubernetes. Do t'ju tregoj se si mund t\u00eb krijoni konceptin tuaj t\u00eb Deployer duke p\u00ebrdorur mjete open-source. <\/p>\n

Pra, gj\u00ebja e par\u00eb q\u00eb b\u00ebn Deployer \u00ebsht\u00eb t\u00eb krijoj\u00eb nj\u00eb kontrollues replikimi RC duke p\u00ebrdorur API-n\u00eb e Kubernetes. Kjo API krijon pod-e dhe sh\u00ebrbime p\u00ebr dislokimin e m\u00ebtejsh\u00ebm, pra krijon nj\u00eb grumbull t\u00eb ri t\u00eb plot\u00eb p\u00ebr aplikacionet tona. Sapo RC t\u00eb sigurohet q\u00eb replikat kan\u00eb nisur, do t\u00eb kryej\u00eb kontrollin e funksionimit t\u00eb tyre, Health check. P\u00ebr k\u00ebt\u00eb, n\u00eb Deployer p\u00ebrdoret komanda GET \/health. Ajo aktivizon komponent\u00ebt p\u00ebrkat\u00ebs t\u00eb kontrollit dhe kontrollon t\u00eb gjith\u00eb element\u00ebt q\u00eb sigurojn\u00eb funksionimin e grumbullit. <\/p>\n

\"DEVOXX
\n
\nPasi t\u00eb gjitha pod-et t\u00eb raportojn\u00eb p\u00ebr \"sh\u00ebndetin\" e tyre, Deployer krijon nj\u00eb element t\u00eb ri konfigurationsh \u2013 ruajtja e shp\u00ebrndar\u00eb etcd, e cila p\u00ebrdoret brenda Kubernetes, p\u00ebrfshir\u00eb p\u00ebr ruajtjen e konfigurimit t\u00eb balancuesit t\u00eb ngarkes\u00ebs. Ne shkruajm\u00eb t\u00eb dh\u00ebna n\u00eb etcd, dhe nj\u00eb mjet i vog\u00ebl confd ndjek etcd p\u00ebr shfaqjen e t\u00eb dh\u00ebnave t\u00eb reja. <\/p>\n

N\u00ebse ai zbulon ndonj\u00eb ndryshim n\u00eb konfigurimin fillestar, krijon nj\u00eb skedar t\u00eb ri konfigurimi dhe ia transmeton ha-proxy. N\u00eb k\u00ebt\u00eb rast, ha-proxy rindez pa humbur ndonj\u00eb lidhje dhe adreson ngarkes\u00ebn n\u00eb sh\u00ebrbimet e reja, t\u00eb cilat sigurojn\u00eb funksionimin e versionit t\u00eb ri t\u00eb aplikacioneve tona. <\/p>\n

\"DEVOXX
\n
\nSi\u00e7 e shihni, pavar\u00ebsisht nga numri i madh i komponent\u00ebve, k\u00ebtu nuk ka asgj\u00eb t\u00eb komplikueshme. Thjesht keni nevoj\u00eb t\u00eb kushtoni m\u00eb shum\u00eb v\u00ebmendje API-s\u00eb dhe etcd. Dua t\u00eb ju flas p\u00ebr nj\u00eb deployer open-source q\u00eb ne vet\u00eb p\u00ebrdorim \u2013 kjo \u00ebsht\u00eb Amdatu Kubernetes Deployer.<\/p>\n

\"DEVOXX
\n
\nKy \u00ebsht\u00eb nj\u00eb mjet p\u00ebr orkestrimin e dislokimeve Kubernetes, q\u00eb ka k\u00ebto funksione: <\/p>\n