{"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 e shkall\u00ebzimit dhe automatizimi i shp\u00ebrndarjes. Pjesa 2.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Kubernetes \u00ebsht\u00eb nj\u00eb mjet i shk\u00eblqyer p\u00ebr t\u00eb drejtuar konteiner\u00ebt Docker n\u00eb nj\u00eb mjedis t\u00eb klasterizuar t\u00eb prodhimit. Megjithat\u00eb, ka detyra q\u00eb Kubernetes nuk mund t'i zgjidh\u00eb. Kur shp\u00ebrndajm\u00eb shpesh n\u00eb mjedisin e pun\u00ebs, na nevojitet nj\u00eb implementim Blue\/Green plot\u00ebsisht i automatizuar p\u00ebr t\u00eb shmangur ndalimet n\u00eb k\u00ebt\u00eb proces, gjat\u00eb t\u00eb cilit gjithashtu duhet t\u00eb trajtojm\u00eb k\u00ebrkesat ekstern HTTP dhe t\u00eb kryejm\u00eb shkarkimin SSL. Kjo k\u00ebrkon integrim 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 kur punon n\u00eb nj\u00eb mjedis cloud, p\u00ebr shembull, zvog\u00eblimi i pjessh\u00ebm i klasterit gjat\u00eb nat\u00ebs.<\/p>\n

Nd\u00ebrsa Kubernetes nuk i ka k\u00ebto funksione direkt \"nga kutia\", ai ofron nj\u00eb API q\u00eb mund t\u00eb shfryt\u00ebzohet p\u00ebr zgjidhjen e k\u00ebtyre detyrave. Veglat p\u00ebr implementimin e automatizuar Blue\/Green 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 baz\u00ebn e open-source.<\/p>\n

N\u00eb k\u00ebt\u00eb artikull, n\u00eb transkriptin e videos, shpjegohet se si t\u00eb konfiguroni Kubernetes bashk\u00eb me komponente t\u00eb tjera me burim t\u00eb hapur p\u00ebr krijimin e nj\u00eb mjedisi t\u00eb gatsh\u00ebm p\u00ebr prodhim, i cili pranon kod nga angazhimi git commit pa nd\u00ebrprerje n\u00eb prodhim.<\/p>\n

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

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

Pra, pasi t\u00eb keni aksesuar aplikacionet tuaja nga bota e jashtme, mund t\u00eb filloni konfigurimin e plot\u00eb t\u00eb automatizimit, duke e \u00e7uar at\u00eb n\u00eb nj\u00eb faz\u00eb n\u00eb t\u00eb cil\u00ebn mund t\u00eb realizoni git commit dhe t\u00eb siguroni q\u00eb ky git commit p\u00ebrfundon n\u00eb prodhim. Natyrisht, gjat\u00eb realizimit t\u00eb k\u00ebtyre hapave, gjat\u00eb desplojimit, ne nuk duam t\u00eb hasim ndonj\u00eb nd\u00ebrprerje. Pra, \u00e7do automatizim n\u00eb Kubernetes fillon me API. <\/p>\n

\"DEVOXX
\n
\nKubernetes nuk \u00ebsht\u00eb nj\u00eb mjet q\u00eb mund t\u00eb p\u00ebrdoret produktivisht \"n\u00eb m\u00ebnyr\u00eb t\u00eb drejtp\u00ebrdrejt\u00eb nga kutia\". Sigurisht, mund ta b\u00ebni k\u00ebt\u00eb, duke p\u00ebrdorur kubectl etj., por API \u00ebsht\u00eb gj\u00ebja m\u00eb interesante dhe e dobishme e k\u00ebsaj platforme. Duke p\u00ebrdorur API-n\u00eb si nj\u00eb grup funksionesh, mund t\u00eb keni akses n\u00eb pothuajse \u00e7do gj\u00eb q\u00eb d\u00ebshironi t\u00eb b\u00ebni n\u00eb Kubernetes. Vet\u00eb kubectl gjithashtu p\u00ebrdor REST API. <\/p>\n

Kjo \u00ebsht\u00eb REST, k\u00ebshtu q\u00eb mund t\u00eb p\u00ebrdorni \u00e7do gjuh\u00eb dhe mjet p\u00ebr t\u00eb punuar me k\u00ebt\u00eb API, por librarit\u00eb p\u00ebrdoruese do t'ju leht\u00ebsojn\u00eb jet\u00ebn n\u00eb m\u00ebnyr\u00eb t\u00eb konsiderueshme. Ekipi im ka shkruar 2 libra t\u00eb till\u00eb: nj\u00eb p\u00ebr Java \/ OSGi dhe nj\u00eb p\u00ebr Go. I dyti nuk p\u00ebrdoret shpesh, por gjithsesi, keni n\u00eb dispozicion k\u00ebto mjete t\u00eb dobishme. Ato jan\u00eb nj\u00eb projekt pjes\u00ebrisht i licencuar me burim t\u00eb hapur. Ekzistojn\u00eb shum\u00eb libra t\u00eb till\u00eb p\u00ebr gjuh\u00eb t\u00eb ndryshme, k\u00ebshtu q\u00eb mund t\u00eb zgjidhni ato q\u00eb i p\u00ebrshtaten m\u00eb mir\u00eb. <\/p>\n

\"DEVOXX
\n
\nPra ndaj, para se t\u00eb filloni me automatizimin e shp\u00ebrndarjes, duhet t\u00eb siguroheni q\u00eb ky proces t\u00eb mos p\u00ebsoj\u00eb asnj\u00eb ndales\u00eb. P\u00ebr shembull, ekipi yn\u00eb kryen shp\u00ebrndarje n\u00eb prodhim n\u00eb mes t\u00eb dit\u00ebs, kur njer\u00ebzit po e p\u00ebrdorin maksimalisht aplikacionin, prandaj \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme t\u00eb evitoni vonesat n\u00eb k\u00ebt\u00eb proces. P\u00ebr t\u00eb shmangur ndalesat, p\u00ebrdoren dy m\u00ebnyra: shp\u00ebrndarje blue\/green ose p\u00ebrdit\u00ebsim i vazhduesh\u00ebm rolling update. N\u00eb rastin e fundit, n\u00ebse keni 5 replika t\u00eb aplikacionit, ato p\u00ebrdit\u00ebsohen nj\u00eb nga nj\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb rregullt. Kjo metod\u00eb funksionon shum\u00eb mir\u00eb, por nuk \u00ebsht\u00eb e p\u00ebrshtatshme n\u00ebse gjat\u00eb shp\u00ebrndarjes keni versione t\u00eb ndryshme t\u00eb aplikacionit q\u00eb funksionojn\u00eb nj\u00ebkoh\u00ebsisht. N\u00eb k\u00ebt\u00eb rast, mund t\u00eb p\u00ebrdit\u00ebsoni nd\u00ebrfaqen e p\u00ebrdoruesit nd\u00ebrkoh\u00eb q\u00eb backend-i punon me versionin e vjet\u00ebr, dhe puna e aplikacionit do t\u00eb nd\u00ebrpritet. Prandaj, nga pik\u00ebpamja e programimit, punimi n\u00eb kushte t\u00eb tilla \u00ebsht\u00eb mjaft i v\u00ebshtir\u00eb. <\/p>\n

Kjo \u00ebsht\u00eb nj\u00eb nga arsyet pse ne preferojm\u00eb t\u00eb p\u00ebrdorim blue\/green deployment p\u00ebr automatizimin e implementimit t\u00eb aplikacioneve tona. Me k\u00ebt\u00eb metod\u00eb, ju duhet t\u00eb siguroheni se n\u00eb \u00e7do moment aktiv \u00ebsht\u00eb vet\u00ebm nj\u00eb version i aplikacionit. <\/p>\n

Mekanizmi i blue\/green deployment duket si vijon. Ne marrim trafik p\u00ebr aplikacionet tona p\u00ebrmes ha-proxy, i cili e drejton at\u00eb te instancat e aktivizuara t\u00eb aplikacionit t\u00eb t\u00eb nj\u00ebjtit version. <\/p>\n

Kur b\u00ebhet nj\u00eb implementim i ri, ne p\u00ebrdorim Deployer, i cili merr komponent\u00ebt e rinj dhe b\u00ebn implementimin e versionit t\u00eb ri. Implementimi i versionit t\u00eb ri t\u00eb aplikacionit do t\u00eb thot\u00eb se nj\u00eb grup i ri instancash \"ngrihet\", pas s\u00eb cil\u00ebs k\u00ebto instanca t\u00eb versionit t\u00eb ri aktivizohen n\u00eb nj\u00eb konteiner t\u00eb ri dhe t\u00eb ndar\u00eb. Megjithat\u00eb, ha-proxy nuk di asgj\u00eb p\u00ebr ta dhe p\u00ebr momentin nuk drejton asnj\u00eb ngarkes\u00eb pune te ato.<\/p>\n

Prandaj, e para q\u00eb duhet b\u00ebr\u00eb \u00ebsht\u00eb t\u00eb kryhen kontrollet e sh\u00ebndetshm\u00ebris\u00eb s\u00eb versioneve t\u00eb reja p\u00ebr t'u siguruar se instancat jan\u00eb t\u00eb gatshme p\u00ebr t\u00eb trajtuar ngarkes\u00ebn.<\/p>\n

\"DEVOXX
\n
\nT\u00eb gjith\u00eb komponent\u00ebt e shp\u00ebrndarjes duhet t\u00eb mb\u00ebshtesin ndonj\u00eb form\u00eb t\u00eb kontrollit t\u00eb sh\u00ebndetit. Kjo mund t\u00eb jet\u00eb nj\u00eb kontroll i thjesht\u00eb HTTP, kur merrni nj\u00eb status kod 200, ose nj\u00eb kontroll m\u00eb i thell\u00eb, ku verifikoni lidhjen e kopjeve me databaz\u00ebn dhe sh\u00ebrbimet e tjera, q\u00ebndrueshm\u00ebrin\u00eb e lidhjeve n\u00eb ambientin dinamik, si dhe n\u00ebse gjith\u00e7ka po nis dhe funksionon si\u00e7 duhet. Ky proces mund t\u00eb jet\u00eb mjaft kompleks. <\/p>\n

\"DEVOXX
\n
\nPasi sistemi t\u00eb jet\u00eb siguruar p\u00ebr funksionimin e t\u00eb gjitha kopjeve t\u00eb azhurnuara, Deployer do t\u00eb p\u00ebrdit\u00ebsoj\u00eb konfigurimin dhe do t\u00eb d\u00ebrgoj\u00eb confd-n\u00eb e sakta, e cila do t\u00eb rikonfiguronte ha-proxy-n. <\/p>\n

\"DEVOXX
\n
\nVet\u00ebm pas k\u00ebsaj, trafiku do t\u00eb drejtohet n\u00eb n\u00ebnshtrimin me kopjet e versions s\u00eb re, nd\u00ebrsa n\u00ebnshtrimi i vjet\u00ebr do t\u00eb zhduket. <\/p>\n

\"DEVOXX
\n
\nKy mekaniz\u00ebm nuk \u00ebsht\u00eb nj\u00eb ve\u00e7ori e Kubernetes. Koncepti i shp\u00ebrndarjes Blue\/green 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 drejt versionit t\u00eb vjet\u00ebr t\u00eb aplikacionit dhe pas p\u00ebrdit\u00ebsimit, plot\u00ebsisht e shnd\u00ebrroni at\u00eb n\u00eb versionin e ri. Ky princip p\u00ebrdoret jo vet\u00ebm n\u00eb Kubernetes.<\/p>\n

Tani un\u00eb do t'ju prezantoj nj\u00eb komponent t\u00eb ri t\u00eb shp\u00ebrndarjes \u2013 Deployer, i cili kryen verifikimin e funksionimit, rind\u00ebrton proxy dhe m\u00eb shum\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 Deployer duke p\u00ebrdorur mjetet open-source. <\/p>\n

Pra, e para q\u00eb b\u00ebn Deployer \u00ebsht\u00eb krijimi i nj\u00eb kontrolluesi t\u00eb replikimit RC, duke p\u00ebrdorur API-n\u00eb e Kubernetes. Ky API krijon pod-e dhe sh\u00ebrbime p\u00ebr shp\u00ebrndarjen e m\u00ebtejshme, dometh\u00ebn\u00eb krijon nj\u00eb klas\u00eb krejt t\u00eb re p\u00ebr aplikacionet tona. Sapo RC t\u00eb sigurohet q\u00eb replikat kan\u00eb nisur, ai do t\u00eb kryej\u00eb nj\u00eb kontroll t\u00eb funksionimit 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 verifikon t\u00eb gjitha elementet q\u00eb sigurojn\u00eb funksionimin e klas\u00ebs. <\/p>\n

\"DEVOXX
\n
\nPasi q\u00eb t\u00eb gjitha pods raportojn\u00eb p\u00ebr \"sh\u00ebndetin\" e tyre, Deployer krijon nj\u00eb element t\u00eb ri konfigurimi \u2013 nj\u00eb ruajtje t\u00eb shp\u00ebrndar\u00eb etcd, e cila p\u00ebrdoret brenda Kubernetes, duke p\u00ebrfshir\u00eb p\u00ebr ruajtjen e konfiguracionit t\u00eb balancuesit t\u00eb ngarkes\u00ebs. Ne regjistrojm\u00eb t\u00eb dh\u00ebnat n\u00eb etcd, dhe nj\u00eb mjet i vog\u00ebl confd monitoron etcd p\u00ebr t\u00eb zbuluar t\u00eb dh\u00ebna t\u00eb reja. <\/p>\n

N\u00ebse ai zb\u53d1\u73b0 ndonj\u00eb ndryshim n\u00eb konfigurimin e par\u00eb, ai gjeneron nj\u00eb skedar t\u00eb ri konfigurimi dhe ia d\u00ebrgon ha-proxy. N\u00eb k\u00ebt\u00eb rast, ha-proxy rindez pa humbur asnj\u00eb lidhje dhe adreson ngarkes\u00ebn te sh\u00ebrbimet e reja, t\u00eb cilat sigurojn\u00eb funksionimin e versioneve t\u00eb reja t\u00eb aplikacioneve tona. <\/p>\n

\"DEVOXX
\n
\nSi\u00e7 e shihni, pavar\u00ebsisht nga numri i madh i komponent\u00ebve, nuk ka asgj\u00eb t\u00eb komplikuar k\u00ebtu. Ju thjesht duhet t\u00eb kushtoni m\u00eb shum\u00eb v\u00ebmendje API dhe etcd. Dua t'ju flas p\u00ebr nj\u00eb depozitor open-source, q\u00eb ne e p\u00ebrdorim vet\u00eb \u2013 Amdatu Kubernetes Deployer.<\/p>\n

\"DEVOXX
\n
\nKy \u00ebsht\u00eb nj\u00eb mjet p\u00ebr orkestrimin e implementimeve Kubernetes, q\u00eb ka funksione t\u00eb tilla si: <\/p>\n