{"id":56259,"date":"2020-02-08T00:00:00","date_gmt":"2020-02-07T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/rabochie-uzly-kubernetes-mnogo-malenkih-ili-neskolko-bolshih"},"modified":"2020-02-18T14:04:30","modified_gmt":"2020-02-18T11:04:30","slug":"rabochie-uzly-kubernetes-mnogo-malenkih-ili-neskolko-bolshih","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/rabochie-uzly-kubernetes-mnogo-malenkih-ili-neskolko-bolshih","title":{"rendered":"Nyjet e pun\u00ebs n\u00eb Kubernetes: shum\u00eb t\u00eb vogla apo disa t\u00eb m\u00ebdha?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Nyjet
\nKur krijoni nj\u00eb klaster Kubernetes, mund t\u00eb shfaqen pyetje: sa nyje pune duhet t\u00eb konfiguroni dhe \u00e7far\u00eb lloji? \u00c7far\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb p\u00ebr nj\u00eb klaster on-premise: t\u00eb blini disa server\u00eb t\u00eb fuqish\u00ebm ose t\u00eb angazhojeni nj\u00eb duzin\u00eb makinash t\u00eb vjetra n\u00eb qendr\u00ebn tuaj t\u00eb t\u00eb dh\u00ebnave? Dhe n\u00eb cloud, a \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb merrni tet\u00eb instanca me nj\u00eb b\u00ebrtham\u00eb apo dy me kat\u00ebr b\u00ebrthama? <\/p>\n

P\u00ebrgjigjet p\u00ebr k\u00ebto pyetje jan\u00eb n\u00eb artikull t\u00eb Daniel Vaybel, inxhinier programues dhe m\u00ebsues i projektit arsimor Learnk8s<\/a><\/noindex> n\u00eb p\u00ebrkthimin e ekipit Kubernetes aaS nga Mail.ru<\/a><\/noindex>.
\n<\/a><\/noindex><\/p>\n

Kapasiteti i klasterit<\/h2>\n

\nN\u00eb p\u00ebrgjith\u00ebsi, nj\u00eb klaster Kubernetes mund t\u00eb mendohet si nj\u00eb \"super nyje\" e madhe. Fuqia e tij e p\u00ebrgjithshme llogaritet si shuma e fuqive t\u00eb t\u00eb gjitha nyjeve p\u00ebrb\u00ebr\u00ebse. <\/p>\n

Ekzistojn\u00eb disa m\u00ebnyra p\u00ebr t\u00eb arritur kapacitetin e d\u00ebshiruar t\u00eb klasterit. P\u00ebr shembull, na nevojitet nj\u00eb klaster me nj\u00eb kapacitet t\u00eb p\u00ebrgjithsh\u00ebm prej 8 b\u00ebrthamash procesori dhe 32 GB RAM, sepse grupi i aplikacioneve k\u00ebrkon nj\u00eb mund\u00ebsi t\u00eb till\u00eb. At\u00ebher\u00eb mund t\u00eb instaloni dy nyje me 16 GB memorie ose kat\u00ebr nyje me 8 GB memorie, dy procesor\u00eb kat\u00ebr b\u00ebrthamash ose kat\u00ebr me dy b\u00ebrthama.<\/p>\n

Ja dy mund\u00ebsi t\u00eb mundshme p\u00ebr t\u00eb krijuar nj\u00eb klaster:<\/p>\n

\"Nyjet
\nT\u00eb dy opsionet ofrojn\u00eb nj\u00eb kluster me kapacitet t\u00eb nj\u00ebjt\u00eb, por n\u00eb konfigurimin n\u00eb fund jan\u00eb vendosur kat\u00ebr nj\u00ebsit\u00eb m\u00eb t\u00eb vogla, nd\u00ebrsa n\u00eb konfigurimin lart jan\u00eb dy nj\u00ebsit\u00eb m\u00eb t\u00eb m\u00ebdha. <\/p>\n

Cili opsion \u00ebsht\u00eb m\u00eb i mir\u00eb?<\/h3>\n

\nP\u00ebr t\u00eb p\u00ebrgjigjur n\u00eb k\u00ebt\u00eb pyetje, le t\u00eb shqyrtojm\u00eb p\u00ebrpar\u00ebsit\u00eb e t\u00eb dy opsioneve. I kemi p\u00ebrmbledhur ato n\u00eb nj\u00eb tabel\u00eb.<\/p>\n

Disa nj\u00ebsit\u00eb t\u00eb m\u00ebdha<\/p>\n

Shum\u00eb nj\u00ebsit\u00eb t\u00eb vogla<\/p>\n

Menaxhimi i leht\u00eb i klustrit (n\u00ebse \u00ebsht\u00eb on-premise)<\/p>\n

Automatik i shkall\u00ebzimit fluid<\/p>\n

M\u00eb i lir\u00eb (n\u00ebse on-premise) <\/p>\n

\u00c7mimi \u00ebsht\u00eb paksa i nj\u00ebjt\u00eb (n\u00eb cloud) <\/p>\n

Mund t\u00eb ekzekutoni aplikacione me k\u00ebrkesa t\u00eb larta p\u00ebr burime <\/p>\n

Replikim i plot\u00eb<\/p>\n

Burimet p\u00ebrdoren m\u00eb efektivisht (m\u00eb pak overhead p\u00ebr demon\u00ebt e sistemit)
\nM\u00eb shum\u00eb q\u00ebndrueshm\u00ebri e klustrit<\/p>\n

Kujdes, ne flasim vet\u00ebm p\u00ebr nj\u00ebsit\u00eb operative. Zgjedhja e numrit dhe p\u00ebrmasave t\u00eb nj\u00ebsive kryesore \u00ebsht\u00eb nj\u00eb tem\u00eb krejt\u00ebsisht tjet\u00ebr.<\/p>\n

Tani, le t\u00eb diskutojm\u00eb m\u00eb n\u00eb detaje \u00e7do pik\u00eb nga tabela.<\/p>\n

Opsioni i par\u00eb: disa nj\u00ebsit\u00eb t\u00eb m\u00ebdha<\/h2>\n

\nOpsioni m\u00eb ekstrem \u00ebsht\u00eb nj\u00eb nj\u00ebsit\u00eb operative p\u00ebr gjith\u00eb kapacitetin e klustrit. N\u00eb shembullin m\u00eb lart do t\u00eb ishte nj\u00eb nj\u00ebsit\u00eb operative me 16 b\u00ebrthama CPU dhe 16 GB memorie.<\/p>\n

P\u00ebrfitimet <\/h3>\n

\nP\u00ebrfitimi \u2116 1. Menaxhimi m\u00eb i leht\u00eb<\/b>
\n\u00cbsht\u00eb m\u00eb e leht\u00eb t\u00eb menaxhosh disa makina sesa nj\u00eb park t\u00eb t\u00ebr\u00eb. Aktualizimet dhe korrigjimet aplikohen m\u00eb shpejt, dhe sinkronizimi \u00ebsht\u00eb m\u00eb i leht\u00eb. Numri i d\u00ebshtimeve n\u00eb numra absolut\u00eb gjithashtu \u00ebsht\u00eb m\u00eb i ul\u00ebt.<\/p>\n

Kujdes, gjith\u00e7ka e p\u00ebrmendur m\u00eb sip\u00ebr i referohet harduerit tuaj, server\u00ebve tuaj, dhe jo instancave n\u00eb re.<\/p><\/blockquote>\n

\nN\u00eb re, situata \u00ebsht\u00eb ndryshe. Menaxhimi b\u00ebhet nga ofruesi i sh\u00ebrbimit t\u00eb reve. K\u00ebshtu, menaxhimi i dhjet\u00eb node-ve n\u00eb re nuk \u00ebsht\u00eb ndryshe nga menaxhimi i nj\u00eb node.<\/p>\n

Routimi i trafikut dhe shp\u00ebrndarja e ngarkes\u00ebs midis pod-eve n\u00eb re kryhet automatikisht<\/a><\/noindex>: trafiku i ardhsh\u00ebm nga interneti d\u00ebrgohet n\u00eb balancuesin kryesor t\u00eb ngarkes\u00ebs, i cili drejton trafikun n\u00eb portin e nj\u00ebrit prej node-ve (sh\u00ebrbimi NodePort vendos nj\u00eb port n\u00eb intervalin 30000-32767 n\u00eb \u00e7do node t\u00eb klasterit). Rregullat e vendosura nga kube-proxy riorientojn\u00eb trafikun nga node-ja n\u00eb pod. Ky \u00ebsht\u00eb pamja p\u00ebr dhjet\u00eb pod-e n\u00eb dy node:<\/p>\n

\"Nyjet
\nPika nr. 2. M\u00eb pak shpenzime p\u00ebr node<\/b>
\nNj\u00eb server i fuqish\u00ebm \u00ebsht\u00eb m\u00eb i shtrenjt\u00eb, por rritja e \u00e7mimit nuk \u00ebsht\u00eb domosdoshm\u00ebrisht lineare. Me fjal\u00eb t\u00eb tjera, nj\u00eb server me 10 b\u00ebrthama dhe 10 GB RAM zakonisht \u00ebsht\u00eb m\u00eb i lir\u00eb se dhjet\u00eb server\u00eb nj\u00eb-b\u00ebrtham\u00ebsh me t\u00eb nj\u00ebjtin sasi RAM.<\/p>\n

Por kini parasysh se ky rregull zakonisht nuk funksionon n\u00eb sh\u00ebrbimet cloud. N\u00eb skemat aktuale t\u00eb \u00e7mimeve, t\u00eb gjith\u00eb ofruesit kryesor\u00eb t\u00eb sh\u00ebrbimeve cloud \u00e7mimet rriten linearisht me rritjen e kapacitetit.<\/p><\/blockquote>\n

\nPrandaj, zakonisht nuk \u00ebsht\u00eb e mundur t\u00eb kursehet n\u00eb server\u00ebt m\u00eb t\u00eb fuqish\u00ebm n\u00eb cloud.<\/p>\n

Pika e tret\u00eb. Mund t\u00eb executoni aplikacione t\u00eb k\u00ebrkueshme p\u00ebr burime.<\/b>
\nDisa aplikacione k\u00ebrkojn\u00eb servera t\u00eb fuqish\u00ebm n\u00eb klaster. P\u00ebr shembull, n\u00ebse nj\u00eb sistem m\u00ebsimi makinerik k\u00ebrkon 8 GB RAM, nuk do t\u00eb mund ta ekzekutoni at\u00eb n\u00eb node me 1 GB, vet\u00ebm n\u00ebse keni t\u00eb pakt\u00ebn nj\u00eb node t\u00eb madh pune.<\/p>\n

Kundrat <\/h3>\n

\n\u041c\u0438\u043d\u0443\u0441 \u2116 1. \u041c\u043d\u043e\u0433\u043e pod’\u043e\u0432 \u043d\u0430 \u0443\u0437\u0435\u043b<\/b>
\n\u0415\u0441\u043b\u0438 \u043e\u0434\u043d\u0430 \u0438 \u0442\u0430 \u0436\u0435 \u0437\u0430\u0434\u0430\u0447\u0430 \u0432\u044b\u043f\u043e\u043b\u043d\u044f\u0435\u0442\u0441\u044f \u043d\u0430 \u043c\u0435\u043d\u044c\u0448\u0435\u043c \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u0435 \u0443\u0437\u043b\u043e\u0432, \u0442\u043e \u043d\u0430 \u043a\u0430\u0436\u0434\u043e\u043c \u0438\u0437 \u043d\u0438\u0445, \u0435\u0441\u0442\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e, \u0431\u0443\u0434\u0435\u0442 \u0431\u043e\u043b\u044c\u0448\u0435 pod’\u043e\u0432.<\/p>\n

Kjo mund t\u00eb b\u00ebhet nj\u00eb problem.<\/p>\n

Arsyeja \u00ebsht\u00eb se \u00e7do modul sjell disa kosto shtes\u00eb n\u00eb ambientin e ekzekutimit t\u00eb kontejnerit (p.sh., Docker), si dhe n\u00eb kubelet dhe cAdvisor.<\/p>\n

P\u00ebr shembull, kubelet regulisht sondon p\u00ebr jet\u00ebsin\u00eb e t\u00eb gjitha konteiner\u00ebve n\u00eb nyj\u00eb \u2014 sa m\u00eb shum\u00eb konteiner\u00eb, aq m\u00eb shum\u00eb pun\u00eb ka p\u00ebr kubelet.<\/p>\n

CAdvisor grumbullon statistik\u00ebn e p\u00ebrdorimit t\u00eb burimeve t\u00eb t\u00eb gjitha konteiner\u00ebve n\u00eb nyj\u00eb, dhe kubelet regulisht k\u00ebrkon k\u00ebt\u00eb informacion dhe e ofron at\u00eb p\u00ebrmes API. Edhe nj\u00ebher\u00eb, sa m\u00eb shum\u00eb konteiner\u00eb, aq m\u00eb shum\u00eb pun\u00eb ka p\u00ebr cAdvisor dhe kubelet.<\/p>\n

N\u00ebse numri i moduleve rritet, kjo mund t\u00eb ngadal\u00ebsoj\u00eb sistemin dhe madje ta d\u00ebmtoj\u00eb at\u00eb.<\/p>\n

\"Nyjet
\nN\u00eb depoziten e Kubernetes disa Kane ankuar<\/a><\/noindex>, q\u00eb nyjat kalojn\u00eb mes statusit Ready\/NotReady, pasi kontrollimet e rregullta t\u00eb kubelet p\u00ebr t\u00eb gjitha konteiner\u00ebt n\u00eb nyj\u00eb marrin shum\u00eb koh\u00eb.
\nP\u00ebr k\u00ebt\u00eb arsye, Kubernetes \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442 \u0440\u0430\u0437\u043c\u0435\u0449\u0430\u0442\u044c \u043d\u0435 \u0431\u043e\u043b\u0435\u0435 110 pod’\u043e\u0432 \u043d\u0430 \u0443\u0437\u0435\u043b<\/a><\/noindex>. N\u00eb var\u00ebsi t\u00eb performanc\u00ebs s\u00eb nyj\u00ebs, mund t\u00eb ekzekutoni m\u00eb shum\u00eb pod\u00eb n\u00eb nyj\u00eb, por \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb parashikoni n\u00ebse do t\u00eb lindin probleme apo n\u00ebse gjith\u00e7ka do t\u00eb funksionoj\u00eb mir\u00eb. \u00cbsht\u00eb e k\u00ebshillueshme t\u00eb testoni paraprakisht funksionimin. <\/p>\n

Minusi Nr. 2. Kufizimi n\u00eb replikim<\/b>
\nNumri i vog\u00ebl i nyjeve kufizon shkall\u00ebn efektive t\u00eb replikimit t\u00eb aplikacioneve. P\u00ebr shembull, n\u00ebse keni nj\u00eb aplikacion me disponueshm\u00ebri t\u00eb lart\u00eb me pes\u00eb replikime, por vet\u00ebm dy nyje, at\u00ebher\u00eb shkalla efektive e replikimit zvog\u00eblohet n\u00eb dy.<\/p>\n

Pes\u00eb replikime mund t\u00eb shp\u00ebrndahen vet\u00ebm n\u00eb dy nyje, dhe n\u00ebse nj\u00ebra prej tyre d\u00ebshton, ajo menj\u00ebher\u00eb d\u00ebrgon n\u00eb prishje disa replikime.<\/p>\n

N\u00ebse keni pes\u00eb nyje ose m\u00eb shum\u00eb, secila replikim do t\u00eb ekzekutohet n\u00eb nj\u00eb nyje t\u00eb ve\u00e7ant\u00eb, dhe d\u00ebshtimi i nj\u00eb nyje do t\u00eb eliminoj\u00eb jo m\u00eb shum\u00eb se nj\u00eb replikim.<\/p>\n

K\u00ebshtu, k\u00ebrkesat p\u00ebr disponueshm\u00ebri t\u00eb lart\u00eb mund t\u00eb k\u00ebrkojn\u00eb nj\u00eb num\u00ebr minimal t\u00eb nyjeve n\u00eb klaster.<\/p>\n

Minus \u2116 3. Pasojat e nj\u00eb d\u00ebshtimi jan\u00eb m\u00eb t\u00eb k\u00ebqija<\/b>
\nMe num\u00ebr t\u00eb vog\u00ebl nyjesh, \u00e7do d\u00ebshtim sjell pasoja m\u00eb t\u00eb r\u00ebnda. P\u00ebr shembull, n\u00ebse keni vet\u00ebm dy nyje dhe nj\u00ebra prej tyre d\u00ebshton, menj\u00ebher\u00eb humbni gjysm\u00ebn e moduleve tuaj.<\/p>\n

Sigurisht, Kubernetes do t\u00eb transferoj\u00eb ngarkes\u00ebn e pun\u00ebs nga nyja q\u00eb ka d\u00ebshtuar n\u00eb nyjet e tjera. Por n\u00ebse ka pak, mund t\u00eb mos ket\u00eb kapacitet t\u00eb lir\u00eb t\u00eb mjaftuesh\u00ebm. Si rezultat, disa nga aplikacionet tuaja do t\u00eb jen\u00eb t\u00eb pap\u00ebrballueshme derisa t\u00eb rivendosni nyjen q\u00eb ka d\u00ebshtuar.<\/p>\n

Pra ndaj, sa m\u00eb shum\u00eb node t\u00eb ket\u00eb, aq m\u00eb pak ndikim kan\u00eb defektet harduerike.<\/p>\n

Disavantazhi \u2116 4. Shkall\u00ebzimi automatik m\u00eb i ngadalsh\u00ebm<\/b>
\nN\u00eb Kubernetes, ekziston nj\u00eb sistem shkall\u00ebzimi automatik p\u00ebr infrastruktur\u00ebn cloud, i cili lejon shtimin ose heqjen e nodave n\u00eb var\u00ebsi t\u00eb nevojave aktuale. Me node m\u00eb t\u00eb m\u00ebdha, shkall\u00ebzimi b\u00ebhet m\u00eb i papritur dhe i pakuptuesh\u00ebm. P\u00ebr shembull, n\u00eb nj\u00eb konfigurim me dy node, shtimi i nj\u00eb node tjet\u00ebr do ta rris\u00eb kapacitetin e klasterit menj\u00ebher\u00eb me 50%. Dhe do t'ju duhet t\u00eb paguani p\u00ebr k\u00ebto burime, edhe n\u00ebse ato nuk ju nevojiten.<\/p>\n

Pra, n\u00ebse planifikoni t\u00eb p\u00ebrdorni shkall\u00ebzim automatik p\u00ebr klasterin, sa m\u00eb t\u00eb vogla t\u00eb jen\u00eb nodet, aq m\u00eb fleksib\u00ebl dhe ekonomik do t\u00eb jet\u00eb shkall\u00ebzimi q\u00eb do t\u00eb merrni.<\/p>\n

Tani le t\u2019i shqyrtojm\u00eb avantazhet dhe disavantazhet e nj\u00eb numri t\u00eb madh nodash t\u00eb vogla.<\/p>\n

Zgjedhja e dyt\u00eb: shum\u00eb nod\u00eb t\u00eb vogla<\/h2>\n

\nAvantazhet e k\u00ebtij qasje, p\u00ebrfundimisht, rrjedhin nga disavantazhet e opsionit t\u00eb kund\u00ebrt me disa node t\u00eb m\u00ebdha.<\/p>\n

P\u00ebrfitimet<\/h3>\n

\nPlusi \u2116 1. Pasojat m\u00eb t\u00eb vogla t\u00eb defekteve<\/b>
\n\u0427\u0435\u043c \u0431\u043e\u043b\u044c\u0448\u0435 \u0443\u0437\u043b\u043e\u0432, \u0442\u0435\u043c \u043c\u0435\u043d\u044c\u0448\u0435 pod’\u043e\u0432 \u043d\u0430 \u043a\u0430\u0436\u0434\u043e\u043c \u0443\u0437\u043b\u0435. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0435\u0441\u043b\u0438 \u0443 \u0432\u0430\u0441 \u0441\u0442\u043e \u043c\u043e\u0434\u0443\u043b\u0435\u0439 \u043d\u0430 \u0434\u0435\u0441\u044f\u0442\u044c \u0443\u0437\u043b\u043e\u0432, \u0442\u043e \u043d\u0430 \u043a\u0430\u0436\u0434\u043e\u043c \u0443\u0437\u043b\u0435 \u0431\u0443\u0434\u0435\u0442 \u0432 \u0441\u0440\u0435\u0434\u043d\u0435\u043c \u043f\u043e \u0434\u0435\u0441\u044f\u0442\u044c \u043c\u043e\u0434\u0443\u043b\u0435\u0439.<\/p>\n

Pra, n\u00ebse nj\u00eb nga nyjet d\u00ebshton, do t\u00eb humbni vet\u00ebm 10% t\u00eb ngarkes\u00ebs s\u00eb pun\u00ebs. Ka mund\u00ebsi q\u00eb t\u00eb preken vet\u00ebm disa replika dhe aplikacionet n\u00eb p\u00ebrgjith\u00ebsi t\u00eb mbeten funksionale.<\/p>\n

\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u043d\u0430 \u043e\u0441\u0442\u0430\u0432\u0448\u0438\u0445\u0441\u044f \u0443\u0437\u043b\u0430\u0445, \u0441\u043a\u043e\u0440\u0435\u0435 \u0432\u0441\u0435\u0433\u043e, \u0445\u0432\u0430\u0442\u0438\u0442 \u0441\u0432\u043e\u0431\u043e\u0434\u043d\u044b\u0445 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0434\u043b\u044f \u0440\u0430\u0431\u043e\u0447\u0435\u0439 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u043e\u0442\u043a\u0430\u0437\u0430\u0432\u0448\u0435\u0433\u043e \u0443\u0437\u043b\u0430, \u0442\u0430\u043a \u0447\u0442\u043e Kubernetes \u043c\u043e\u0436\u0435\u0442 \u0441\u0432\u043e\u0431\u043e\u0434\u043d\u043e \u043f\u0435\u0440\u0435\u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u0442\u044c pod’\u044b, \u0438 \u0432\u0430\u0448\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043e\u0442\u043d\u043e\u0441\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0431\u044b\u0441\u0442\u0440\u043e \u0432\u0435\u0440\u043d\u0443\u0442\u0441\u044f \u0432 \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0435 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435.<\/p>\n

P\u00ebrfitimi num\u00ebr 2. Replikimi i mir\u00eb<\/b>
\nN\u00ebse ka mjaft nyje, planifikuesi i Kubernetes mund t\u00eb caktoj\u00eb t\u00eb gjitha replikat n\u00eb nyje t\u00eb ndryshme. K\u00ebshtu, n\u00eb rast d\u00ebshtimi t\u00eb nj\u00eb nyje do t\u00eb prek\u00ebt vet\u00ebm nj\u00eb replik\u00eb, nd\u00ebrsa aplikacioni do t\u00eb mbetet i aksesuesh\u00ebm.<\/p>\n

Kundrat <\/h3>\n

\nMinus num\u00ebr 1. M\u00eb e v\u00ebshtir\u00eb menaxhimi<\/b>
\nM\u00eb shum\u00eb nyje \u00ebsht\u00eb m\u00eb e v\u00ebshtir\u00eb t\u00eb menaxhohen. P\u00ebr shembull, \u00e7do nyje Kubernetes duhet t\u00eb nd\u00ebrveproj\u00eb me t\u00eb gjitha nyjet e tjera, q\u00eb do t\u00eb thot\u00eb se numri i lidhjeve rritet katrorisht, dhe t\u00eb gjitha k\u00ebto lidhje duhet t\u00eb q\u00ebndrojn\u00eb n\u00ebn mbik\u00ebqyrje.<\/p>\n

Menaxheri i nyjeve n\u00eb menaxherin e kontrolleve Kubernetes rregullisht kontrollon t\u00eb gjitha nyjet n\u00eb grup p\u00ebr t\u00eb verifikuar funksionimin \u2014 sa m\u00eb shum\u00eb nyje, aq m\u00eb e madhe \u00ebsht\u00eb ngarkesa mbi kontrollin.<\/p>\n

Ngarkesa rritet gjithashtu mbi baz\u00ebn e t\u00eb dh\u00ebnave etcd \u2014 \u00e7do kubelet dhe kube-proxy th\u00ebrret watcher<\/a><\/noindex> p\u00ebr etcd (p\u00ebrmes API), t\u00eb cilit etcd duhet t'i transmetoj\u00eb p\u00ebrdit\u00ebsimet e objektit.<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, \u00e7do nyj\u00eb punuese ngarkon shtes\u00eb mbi komponent\u00ebt sistemor\u00eb t\u00eb nyjave kryesore.<\/p>\n

\"Nyjet
\nZyrtarisht, Kubernetes mb\u00ebshtet grupe me numrin e nyjeve deri n\u00eb 5000<\/a><\/noindex>. Megjithat\u00eb, n\u00eb praktik\u00eb, edhe 500 nyje mund t\u00eb shkaktojn\u00eb probleme t\u00eb r\u00ebnd\u00ebsishme<\/a><\/noindex>.<\/p>\n

P\u00ebr t\u00eb menaxhuar nj\u00eb num\u00ebr t\u00eb madh nyjesh punuese, duhet zgjedhur nyje kryesore m\u00eb t\u00eb fuqishme. P\u00ebr shembull, kube-up instalon automatikisht<\/a><\/noindex> madh\u00ebsin\u00eb e duhur t\u00eb VM p\u00ebr nyjen kryesore n\u00eb var\u00ebsi t\u00eb numrit t\u00eb nyjeve punuese. Pra, sa m\u00eb shum\u00eb nyje punuese, aq m\u00eb efikas duhet t\u00eb jen\u00eb nyjet kryesore. <\/p>\n

P\u00ebr t\u00eb zgjidhur k\u00ebto probleme specifike ka zhvillime t\u00eb ve\u00e7anta, t\u00eb tilla si Virtual Kubelet<\/a><\/noindex>. Ky sistem lejon kalimin e kufizimeve dhe nd\u00ebrtimin e grupeve me nj\u00eb num\u00ebr t\u00eb madh nyjesh punuese.<\/p>\n

Minus Nr. 2. M\u00eb shum\u00eb shpenzime shtes\u00eb<\/b>
\nN\u00eb \u00e7do nod t\u00eb pun\u00ebs, Kubernetes ekzekuton nj\u00eb grup demon\u00ebsh sistemor\u00eb \u2014 p\u00ebrfshir\u00eb mjedisin e ekzekutimit t\u00eb konteiner\u00ebve (p.sh., Docker), kube-proxy dhe kubelet, duke p\u00ebrfshir\u00eb cAdvisor. T\u00eb gjitha s\u00eb bashku konsumojn\u00eb nj\u00eb sasi t\u00eb caktuar resursesh.<\/p>\n

N\u00ebse keni shum\u00eb nodet t\u00eb vogla, pesha e k\u00ebtyre shpenzimeve shtes\u00eb \u00ebsht\u00eb m\u00eb e madhe n\u00eb \u00e7do nod. P\u00ebr shembull, imagjinoni se t\u00eb gjith\u00eb demon\u00ebt sistemor\u00eb t\u00eb nj\u00eb nodi s\u00eb bashku p\u00ebrdorin 0,1 b\u00ebrthama CPU dhe 0,1 GB memorje. N\u00ebse keni nj\u00eb nod me dhjet\u00eb b\u00ebrthama dhe 10 GB memorje, at\u00ebher\u00eb demon\u00ebt konsumojn\u00eb 1% t\u00eb kapacitetit t\u00eb klasterit. Nga ana tjet\u00ebr, n\u00eb dhjet\u00eb nodet me nj\u00eb b\u00ebrtham\u00eb me 1 GB memorje, demon\u00ebt do t\u00eb marrin 10% t\u00eb kapacitetit t\u00eb klasterit.<\/p>\n

K\u00ebshtu, sa m\u00eb pak nodet t\u00eb keni, aq m\u00eb efektivisht p\u00ebrdoret infrastruktura.<\/p>\n

Minus Nr. 3. P\u00ebrdorim i paefektsh\u00ebm i burimeve<\/b>
\nN\u00eb nodet e vogla, mund t\u00eb ndodhi q\u00eb fragmentet e mbetura t\u00eb burimeve t\u00eb jen\u00eb shum\u00eb t\u00eb vogla p\u00ebr t'u caktuar nj\u00eb ngarkes\u00eb pune, k\u00ebshtu q\u00eb ato mbeten t\u00eb pa p\u00ebrdorura.<\/p>\n

\u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u0430\u0436\u0434\u044b\u0439 pod \u0442\u0440\u0435\u0431\u0443\u0435\u0442 0,75 \u0413\u0411 \u043f\u0430\u043c\u044f\u0442\u0438. \u0415\u0441\u043b\u0438 \u0443 \u0432\u0430\u0441 \u0434\u0435\u0441\u044f\u0442\u044c \u0443\u0437\u043b\u043e\u0432, \u0438 \u043d\u0430 \u043a\u0430\u0436\u0434\u043e\u043c \u043f\u043e 1 \u0413\u0411 \u043f\u0430\u043c\u044f\u0442\u0438, \u043c\u043e\u0436\u043d\u043e \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0434\u0435\u0441\u044f\u0442\u044c pod’\u043e\u0432 \u2014 \u0432 \u0438\u0442\u043e\u0433\u0435 \u043d\u0430 \u043a\u0430\u0436\u0434\u043e\u043c \u0443\u0437\u043b\u0435 \u043e\u0441\u0442\u0430\u043d\u0435\u0442\u0441\u044f 0,25 \u0413\u0411 \u043d\u0435\u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c\u043e\u0439 \u043f\u0430\u043c\u044f\u0442\u0438.<\/p>\n

Kjo do t\u00eb thot\u00eb se 25% e memories s\u00eb t\u00eb gjith\u00eb klasterit shpenzohet kot.<\/p>\n

N\u00eb nj\u00eb node t\u00eb madh me 10 GB memorie, mund t\u00eb lanconi 13 prej k\u00ebtyre moduleve \u2014 dhe do t\u00eb mbetet vet\u00ebm nj\u00eb fragment i pa p\u00ebrdorur prej 0,25 GB.<\/p>\n

N\u00eb k\u00ebt\u00eb rast, vet\u00ebm 2,5% e memories shpenzohet kot.<\/p>\n

Prandaj, n\u00eb node t\u00eb m\u00ebdhenj, resurset shpenzohen m\u00eb optimalisht.<\/p>\n

Disa node t\u00eb m\u00ebdhenj apo shum\u00eb t\u00eb vegj\u00ebl?<\/h2>\n

\nPra, \u00e7far\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb: disa node t\u00eb m\u00ebdhenj n\u00eb klaster apo shum\u00eb t\u00eb vegj\u00ebl? Si gjithmon\u00eb, nuk ka nj\u00eb p\u00ebrgjigje t\u00eb qart\u00eb. Shum\u00eb\u00e7ka varet nga lloji i aplikacionit.<\/p>\n

P\u00ebr shembull, n\u00ebse aplikacioni ka nevoj\u00eb p\u00ebr 10 GB memorie, zgjedhja p\u00ebr node t\u00eb m\u00ebdhenj \u00ebsht\u00eb e qart\u00eb. Nd\u00ebrsa n\u00ebse aplikacioni k\u00ebrkon riplikim dhjet\u00ebfish p\u00ebr akses t\u00eb lart\u00eb, nuk \u00ebsht\u00eb p\u00ebr t'u rrezikuar duke vendosur replikat vet\u00ebm n\u00eb dy node \u2014 n\u00eb klaster duhet t\u00eb jen\u00eb t\u00eb pakt\u00ebn dhjet\u00eb node.<\/p>\n

N\u00eb situata t\u00eb nd\u00ebrmjetme, b\u00ebni zgjedhjen tuaj duke u bazuar n\u00eb avantazhet dhe disavantazhet e \u00e7do opsioni. Mund t\u00eb ndodh\u00eb q\u00eb disa argumente t\u00eb jen\u00eb m\u00eb t\u00eb r\u00ebnd\u00ebsishme p\u00ebr situat\u00ebn tuaj se t\u00eb tjer\u00ebt.<\/p>\n

Nuk \u00ebsht\u00eb aspak e nevojshme t\u00eb keni node t\u00eb nj\u00ebjta n\u00eb madh\u00ebsi. Asgj\u00eb nuk ju ndalon t\u00eb eksperimentoni fillimisht me node t\u00eb s\u00eb nj\u00ebjt\u00ebs madh\u00ebsi dhe m\u00eb pas t\u00eb shtoni node me madh\u00ebsi t\u00eb ndryshme, duke i kombinuar ato n\u00eb nj\u00eb klaster. Node t\u00eb pun\u00ebs n\u00eb klasterin Kubernetes mund t\u00eb jen\u00eb plot\u00ebsisht heterogjene. Pra, mund t\u00eb provoni t\u00eb kombinoni avantazhet e t\u00eb dyja qasjeve.<\/p>\n

Nuk ka nj\u00eb recet\u00eb universale, \u00e7do situat\u00eb ka nuancat e veta, dhe vet\u00ebm prodhimi do t\u00eb tregoj\u00eb t\u00eb v\u00ebrtet\u00ebn.<\/p>\n

P\u00ebrkthimi \u00ebsht\u00eb p\u00ebrgatitur nga ekipi i platform\u00ebs cloud Zgjidhjet Cloud t\u00eb Mail.ru<\/a><\/noindex>.<\/i><\/p>\n

M\u00eb shum\u00eb rreth Kubernetes: 25 mjete t\u00eb dobishme p\u00ebr menaxhimin dhe shp\u00ebrndarjen e klaster\u00ebve<\/a><\/noindex>.<\/p>\n

Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041f\u0440\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0438 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u043c\u043e\u0433\u0443\u0442 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0442\u044c \u0432\u043e\u043f\u0440\u043e\u0441\u044b: \u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u0443\u0437\u043b\u043e\u0432 \u0438 \u043a\u0430\u043a\u043e\u0433\u043e \u0442\u0438\u043f\u0430? \u0427\u0442\u043e \u043b\u0443\u0447\u0448\u0435 \u0434\u043b\u044f \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 on-premise: \u043a\u0443\u043f\u0438\u0442\u044c \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043c\u043e\u0449\u043d\u044b\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0438\u043b\u0438 \u0437\u0430\u0434\u0435\u0439\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0434\u0435\u0441\u044f\u0442\u043e\u043a \u0441\u0442\u0430\u0440\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0432 \u0432\u0430\u0448\u0435\u043c \u0434\u0430\u0442\u0430-\u0446\u0435\u043d\u0442\u0440\u0435? \u0410 \u0432 \u043e\u0431\u043b\u0430\u043a\u0435 \u043b\u0443\u0447\u0448\u0435 \u0432\u0437\u044f\u0442\u044c \u0432\u043e\u0441\u0435\u043c\u044c \u043e\u0434\u043d\u043e\u044f\u0434\u0435\u0440\u043d\u044b\u0445 \u0438\u043b\u0438 \u0434\u0432\u0430 \u0447\u0435\u0442\u044b\u0440\u0435\u0445\u044a\u044f\u0434\u0435\u0440\u043d\u044b\u0445 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u0430? \u041e\u0442\u0432\u0435\u0442\u044b \u043d\u0430 \u044d\u0442\u0438 \u0432\u043e\u043f\u0440\u043e\u0441\u044b \u2014 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 \u0414\u0430\u043d\u0438\u044d\u043b\u044f \u0412\u0430\u0439\u0431\u0435\u043b\u044f, \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u0430-\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0441\u0442\u0430 \u0438 \u043f\u0440\u0435\u043f\u043e\u0434\u0430\u0432\u0430\u0442\u0435\u043b\u044f \u043e\u0431\u0443\u0447\u0430\u044e\u0449\u0435\u0433\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-56259","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Node t\u00eb pun\u00ebs Kubernetes: shum\u00eb t\u00eb vogla apo disa t\u00eb m\u00ebdha? | ProHoster","description":"Kur krijoni nj\u00eb klaster Kubernetes, mund t\u00eb lindin pyetje: sa node pune duhet t\u00eb konfigurohen dhe \u00e7far\u00eb lloji? \u00c7far\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb p\u00ebr nj\u00eb klaster on-premise: t\u00eb blini disa server\u00eb t\u00eb fuqish\u00ebm apo t\u00eb p\u00ebrdorni nj\u00eb duzin\u00eb makinash t\u00eb vjetra n\u00eb qendr\u00ebn tuaj t\u00eb t\u00eb dh\u00ebnave? Po n\u00eb cloud, a \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb merrni tet\u00eb instanca me nj\u00eb b\u00ebrtham\u00eb apo dy me kat\u00ebr b\u00ebrthama? P p\u00ebrgjigjet e k\u00ebtyre pyetjeve jan\u00eb n\u00eb artikullin e Daniel Weibel, inxhinier programues dhe m\u00ebsues t\u00eb trajnuar.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/rabochie-uzly-kubernetes-mnogo-malenkih-ili-neskolko-bolshih","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0430\u0431\u043e\u0447\u0438\u0435 \u0443\u0437\u043b\u044b Kubernetes: \u043c\u043d\u043e\u0433\u043e \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445 \u0438\u043b\u0438 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0431\u043e\u043b\u044c\u0448\u0438\u0445? | ProHoster","og:description":"\u041f\u0440\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0438 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u043c\u043e\u0433\u0443\u0442 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0442\u044c \u0432\u043e\u043f\u0440\u043e\u0441\u044b: \u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u0443\u0437\u043b\u043e\u0432 \u0438 \u043a\u0430\u043a\u043e\u0433\u043e \u0442\u0438\u043f\u0430? \u0427\u0442\u043e \u043b\u0443\u0447\u0448\u0435 \u0434\u043b\u044f \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 on-premise: \u043a\u0443\u043f\u0438\u0442\u044c \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043c\u043e\u0449\u043d\u044b\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0438\u043b\u0438 \u0437\u0430\u0434\u0435\u0439\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0434\u0435\u0441\u044f\u0442\u043e\u043a \u0441\u0442\u0430\u0440\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0432 \u0432\u0430\u0448\u0435\u043c \u0434\u0430\u0442\u0430-\u0446\u0435\u043d\u0442\u0440\u0435? \u0410 \u0432 \u043e\u0431\u043b\u0430\u043a\u0435 \u043b\u0443\u0447\u0448\u0435 \u0432\u0437\u044f\u0442\u044c \u0432\u043e\u0441\u0435\u043c\u044c \u043e\u0434\u043d\u043e\u044f\u0434\u0435\u0440\u043d\u044b\u0445 \u0438\u043b\u0438 \u0434\u0432\u0430 \u0447\u0435\u0442\u044b\u0440\u0435\u0445\u044a\u044f\u0434\u0435\u0440\u043d\u044b\u0445 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u0430? \u041e\u0442\u0432\u0435\u0442\u044b \u043d\u0430 \u044d\u0442\u0438 \u0432\u043e\u043f\u0440\u043e\u0441\u044b \u2014 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 \u0414\u0430\u043d\u0438\u044d\u043b\u044f \u0412\u0430\u0439\u0431\u0435\u043b\u044f, \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u0430-\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0441\u0442\u0430 \u0438 \u043f\u0440\u0435\u043f\u043e\u0434\u0430\u0432\u0430\u0442\u0435\u043b\u044f \u043e\u0431\u0443\u0447\u0430\u044e\u0449\u0435\u0433\u043e","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/rabochie-uzly-kubernetes-mnogo-malenkih-ili-neskolko-bolshih","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-02-07T21:00:00+00:00","article:modified_time":"2020-02-18T11:04:30+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"56259","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:28:23","updated":"2022-10-03 08:08:38"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/56259","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=56259"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/56259\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=56259"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=56259"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=56259"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}