{"id":82920,"date":"2020-05-26T13:42:37","date_gmt":"2020-05-26T11:42:37","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-nastrojka-zaprosov-i-limitov-resursov"},"modified":"2020-05-26T13:42:37","modified_gmt":"2020-05-26T11:42:37","slug":"luchshie-praktiki-kubernetes-nastrojka-zaprosov-i-limitov-resursov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-nastrojka-zaprosov-i-limitov-resursov","title":{"rendered":"Praktikat m\u00eb t\u00eb mira t\u00eb Kubernetes. Konfigurimi i k\u00ebrkesave dhe kufijve t\u00eb burimeve","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Praktikat m\u00eb t\u00eb mira t\u00eb Kubernetes. Krijimi i kontejner\u00ebve t\u00eb vegj\u00ebl<\/a><\/noindex>
\nPraktikat m\u00eb t\u00eb mira t\u00eb Kubernetes. Organizimi i Kubernetes me hap\u00ebsira em\u00ebrtimi<\/a><\/noindex>
\nPraktikat m\u00eb t\u00eb mira t\u00eb Kubernetes. Kontrollimi i jet\u00ebsis\u00eb s\u00eb Kubernetes me teste Readiness dhe Liveness<\/a><\/noindex><\/p>\n

P\u00ebr \u00e7do burim Kubernetes ka mund\u00ebsin\u00eb p\u00ebr t\u00eb konfiguracion dy lloje k\u00ebrkesash \u2014 Requests dhe Limits. E para p\u00ebrshkruan k\u00ebrkesat minimale p\u00ebr disponueshm\u00ebrin\u00eb e burimeve n\u00eb nodin e nevojshme p\u00ebr t\u00eb nisur kontejnerin ose podin, e dyta kufizon n\u00eb m\u00ebnyr\u00eb strikte burimet e disponueshme p\u00ebr kontejnerin. <\/p>\n

Kur Kubernetes planifikon nj\u00eb pod, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme q\u00eb kontejner\u00ebt t\u00eb ken\u00eb mjaft burime p\u00ebr t\u00eb funksionuar normalisht. N\u00ebse planifikoni t\u00eb shpalosni nj\u00eb aplikacion t\u00eb madh n\u00eb nj\u00eb nod me burime t\u00eb kufizuara, \u00ebsht\u00eb shum\u00eb e mundur q\u00eb ai t\u00eb mos funksionoj\u00eb p\u00ebr shkak se nodi p\u00ebrfundon memorjen ose nuk ka mjaft kapacitet procesori. N\u00eb k\u00ebt\u00eb artikull ne do t\u00eb shohim se si mund t\u00eb zgjidhim problemet e munges\u00ebs s\u00eb kapacitetit kompjuterik me ndihm\u00ebn e k\u00ebrkesave p\u00ebr burime dhe kufizimeve.<\/p>\n

K\u00ebrkesat dhe kufizimet jan\u00eb mekanizma q\u00eb Kubernetes p\u00ebrdor p\u00ebr t\u00eb menaxhuar burime si CPU dhe memorie. K\u00ebrkesat e b\u00ebjn\u00eb t\u00eb mundur q\u00eb kontejneri t\u00eb marr\u00eb burimin e k\u00ebrkuar. N\u00ebse nj\u00eb kontejner k\u00ebrkon nj\u00eb burim, Kubernetes do ta planifikoj\u00eb at\u00eb vet\u00ebm n\u00eb nodin q\u00eb mund ta ofroj\u00eb at\u00eb. Kufizimet kontrollojn\u00eb q\u00eb burimet e k\u00ebrkuara nga kontejneri kurr\u00eb t\u00eb mos tejkalojn\u00eb nj\u00eb vler\u00eb t\u00eb caktuar.<\/p>\n

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

Kontejneri mund t\u00eb rris\u00eb kapacitetet llogarit\u00ebse vet\u00ebm deri n\u00eb nj\u00eb limit t\u00eb caktuar, pas s\u00eb cil\u00ebs do t\u00eb kufizohet. Le t\u00eb shohim se si funksionon kjo. Pra, ekzistojn\u00eb dy lloje burimesh \u2014 CPU dhe memorie. Planifikuesi i Kubernetes p\u00ebrdor t\u00eb dh\u00ebnat rreth k\u00ebtyre burimeve p\u00ebr t\u00eb p\u00ebrcaktuar se ku t\u00eb nisim pod-\u00ebt tuaj. Nj\u00eb specifikim tipik i burimeve p\u00ebr nj\u00eb pod duket k\u00ebshtu.<\/p>\n

\"Praktikat
\n
\n\u00c7do konteiner n\u00eb pod mund t\u00eb vendos\u00eb k\u00ebrkesat dhe kufizimet e veta, e gjith\u00eb kjo \u00ebsht\u00eb additive. Burimet e procesorit caktohen n\u00eb milicore. N\u00ebse konteineri juaj ka nevoj\u00eb p\u00ebr dy b\u00ebrthama t\u00eb plota p\u00ebr t\u00eb funksionuar, vendosni nj\u00eb vler\u00eb prej 2000m. N\u00ebse konteinerit i duhet vet\u00ebm fuqia e 1\/4 t\u00eb b\u00ebrtham\u00ebs, vlera do t\u00eb jet\u00eb 250m. Kini parasysh q\u00eb n\u00ebse caktoni nj\u00eb vler\u00eb burimesh procesori m\u00eb t\u00eb madhe se numri i b\u00ebrthamave t\u00eb nodit m\u00eb t\u00eb madh, at\u00ebher\u00eb mb\u00ebshtjellja juaj nuk do t\u00eb planifikohet p\u00ebr t'u nisur fare. Nj\u00eb situat\u00eb e ngjashme do t\u00eb ndodhte n\u00ebse keni nj\u00eb mb\u00ebshtjellje q\u00eb ka nevoj\u00eb p\u00ebr kat\u00ebr b\u00ebrthama, nd\u00ebrsa klasteri Kubernetes p\u00ebrb\u00ebhet vet\u00ebm nga dy makina virtuale kryesore.<\/p>\n

N\u00ebse aplikacioni juaj nuk \u00ebsht\u00eb zhvilluar posa\u00e7\u00ebrisht p\u00ebr t\u00eb shfryt\u00ebzuar p\u00ebrfitimet e shum\u00eb b\u00ebrthamave (k\u00ebtu e kemi fjal\u00ebn p\u00ebr programe si llogaritjet komplekse shkencore dhe operacionet me databaza), praktika m\u00eb e mir\u00eb \u00ebsht\u00eb t\u00eb vendosni K\u00ebrkesat e CPU-s\u00eb n\u00eb 1 ose m\u00eb pak dhe t'i drejtoni m\u00eb shum\u00eb replika p\u00ebr shkall\u00ebzim. Ky zgjidhje do t'i jap\u00eb sistemit m\u00eb shum\u00eb fleksibilitet dhe besueshm\u00ebri.<\/p>\n

Kur b\u00ebhet fjal\u00eb p\u00ebr kufizimet e CPU-s\u00eb, gjith\u00e7ka b\u00ebhet m\u00eb interesante, pasi ai konsiderohet nj\u00eb burim i comprimuar. N\u00ebse aplikacioni juaj fillon t\u00eb afrohet me kufirin e kapacitetit t\u00eb procesorit, Kubernetes do t\u00eb filloj\u00eb t\u00eb ngadal\u00ebsoj\u00eb kontejnerin tuaj duke p\u00ebrdorur CPU Throttling \u2014 ulje t\u00eb frekuenc\u00ebs s\u00eb procesorit. Kjo do t\u00eb thot\u00eb se procesori do t\u00eb jet\u00eb artifialisht i kufizuar, duke i dh\u00ebn\u00eb aplikacionit nj\u00eb performanc\u00eb potencialisht m\u00eb t\u00eb keqe, megjithat\u00eb procesi nuk do t\u00eb nd\u00ebrpritet apo transferohet jasht\u00eb. <\/p>\n

Burimet e kujtes\u00ebs p\u00ebrcaktohen n\u00eb byte. Zakonisht, vlera n\u00eb cil\u00ebsime matet n\u00eb mebibyte (Mib), por ju mund t\u00eb vendosni \u00e7do vler\u00eb, nga byte deri n\u00eb petabyte. K\u00ebtu \u00ebsht\u00eb e nj\u00ebjta situat\u00eb si me CPU-n\u00eb \u2014 n\u00ebse vendosni nj\u00eb k\u00ebrkes\u00eb p\u00ebr sasi memorje q\u00eb tejkalon kapacitetin e memories n\u00eb nyjet tuaja, p\u00ebrfundimi i k\u00ebtij pod-i nuk do t\u00eb planifikohet. Por, ndryshe nga burimet e procesor\u00ebve, memoria nuk \u00ebsht\u00eb e comprimuar, sepse nuk ka asnj\u00eb m\u00ebnyr\u00eb p\u00ebr ta kufizuar p\u00ebrdorimin e saj. Prandaj, ekzekutimi i kontejnerit do t\u00eb ndalet sapo t\u00eb kaloj\u00eb kufirin e memories s\u00eb caktuar.<\/p>\n

\"Praktikat
\n
\n\u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb mbani mend se nuk mund t\u00eb konfiguroni k\u00ebrkesa q\u00eb tejkalojn\u00eb madh\u00ebsin\u00eb e burimeve q\u00eb nodes tuaj mund t\u00eb ofrojn\u00eb. Karakteristikat e burimeve t\u00eb zakonshme p\u00ebr makinat virtuale GKE mund t\u00eb gjenden n\u00eb lidhjet e vendosura n\u00ebn k\u00ebt\u00eb video.<\/p>\n

N\u00eb nj\u00eb bot\u00eb ideale, konfigurimet e containerit do t\u00eb ishin mjaftuesh\u00ebm p\u00ebr t\u00eb siguruar q\u00eb proceset t\u00eb kalojn\u00eb pa probleme. Por bota reale \u00ebsht\u00eb ndryshe; njer\u00ebzit mund t\u00eb harrojn\u00eb leht\u00eb t\u00eb konfigurojn\u00eb p\u00ebrdorimin e burimeve, ose haker\u00ebt mund t\u00eb vendosin k\u00ebrkesa dhe kufizime q\u00eb tejkalojn\u00eb mund\u00ebsit\u00eb reale t\u00eb infrastruktur\u00ebs. P\u00ebr t\u00eb parandaluar zhvillimin e skenar\u00ebve t\u00eb till\u00eb, mund t\u00eb konfiguroni kuota burimesh ResourceQuota dhe gamat e kufizimeve LimitRange.<\/p>\n

Pas krijimit t\u00eb hap\u00ebsirave t\u00eb emrave, ato mund t\u00eb bllokohen me an\u00eb t\u00eb kuotave. P\u00ebr shembull, n\u00ebse keni hap\u00ebsira emrash prodhimi dhe zhvillimi, nj\u00eb model p\u00ebrdoret ku kuotat p\u00ebr prodhim nuk ekzistojn\u00eb fare, nd\u00ebrsa kuotat p\u00ebr zhvillim jan\u00eb shum\u00eb t\u00eb rrepta. Kjo i lejon prodhimit, n\u00eb rast t\u00eb nj\u00eb rritjeje t\u00eb papritur t\u00eb trafik, t\u00eb marr\u00eb t\u00eb gjith\u00eb burimin e disponuesh\u00ebm, duke bllokuar krejt\u00ebsisht zhvillimin.<\/p>\n

Kuota e burimeve mund t\u00eb duket k\u00ebshtu. N\u00eb k\u00ebt\u00eb shembull, ka 4 kategori \u2013 k\u00ebto jan\u00eb 4 rreshta t\u00eb posht\u00ebm t\u00eb kodit.<\/p>\n

\"Praktikat
\n
\nLe t\u00eb shqyrtojm\u00eb secil\u00ebn prej tyre. Requests.cpu \u00ebsht\u00eb numri maksimal i k\u00ebrkesave t\u00eb kombinuara t\u00eb fuqis\u00eb procesorike q\u00eb mund t\u00eb vijn\u00eb nga t\u00eb gjitha en\u00ebt (containers) e hap\u00ebsir\u00ebs emri. N\u00eb k\u00ebt\u00eb shembull, mund t\u00eb keni 50 en\u00eb me k\u00ebrkesa prej 10m, pes\u00eb en\u00eb me k\u00ebrkesa prej 100m ose thjesht nj\u00eb en\u00eb me k\u00ebrkes\u00eb 500m. Deri sa shuma e p\u00ebrgjithshme e requests.cpu p\u00ebr k\u00ebt\u00eb hap\u00ebsir\u00eb emri t\u00eb jet\u00eb m\u00eb pak se 500m, gjith\u00e7ka do t\u00eb jet\u00eb n\u00eb rregull.<\/p>\n

K\u00ebrkesa p\u00ebr memorie requests.memory \u00ebsht\u00eb sasia maksimale e k\u00ebrkesave t\u00eb kombinuara p\u00ebr memorie q\u00eb mund t\u00eb ken\u00eb t\u00eb gjitha en\u00ebt n\u00eb hap\u00ebsir\u00ebn emri. Ashtu si n\u00eb rastin e m\u00ebparsh\u00ebm, mund t\u00eb keni 50 en\u00eb me 2 MiB, pes\u00eb en\u00eb me 20 MiB ose nj\u00eb en\u00eb t\u00eb vetme me 100 MiB, derisa shuma e p\u00ebrgjithshme e memories s\u00eb k\u00ebrkuar n\u00eb hap\u00ebsir\u00ebn emri t\u00eb jet\u00eb m\u00eb pak se 100 mebibajt.<\/p>\n

Limits.cpu \u2014 \u00ebsht\u00eb vlera maksimale e kombinuar e fuqis\u00eb procesorike q\u00eb mund t\u00eb p\u00ebrdorin t\u00eb gjitha kontejner\u00ebt n\u00eb hap\u00ebsir\u00ebn em\u00ebrtuese. Mund t\u00eb mendohet si kufiri i k\u00ebrkesave t\u00eb fuqis\u00eb s\u00eb procesorit.<\/p>\n

M\u00eb n\u00eb fund, limits.memory \u2013 \u00ebsht\u00eb sasia maksimale e p\u00ebrgjithshme e memories q\u00eb mund t\u00eb p\u00ebrdorin t\u00eb gjith\u00eb kontejner\u00ebt n\u00eb hap\u00ebsir\u00ebn em\u00ebrtuese. Ky \u00ebsht\u00eb kufiri i k\u00ebrkesave t\u00eb p\u00ebrgjithshme p\u00ebr memory.
\nPra, me nj\u00ebsin\u00eb e parazgjedhur, kontejner\u00ebt n\u00eb grumbullin Kubernetes punojn\u00eb me burime llogaritur pa kufizime. Me ndihm\u00ebn e kuotave t\u00eb burimeve, administrator\u00ebt e grumbullit mund t\u00eb kufizojn\u00eb konsumin e burimeve dhe krijimin e saj n\u00eb baz\u00eb t\u00eb hap\u00ebsirave em\u00ebrtuese. N\u00eb hap\u00ebsir\u00ebn em\u00ebrtuese, moduli pod ose kontejneri mund t\u00eb konsumoj\u00eb aq fuqi CPU dhe memorie sa \u00ebsht\u00eb e p\u00ebrcaktuar nga kuota e burimeve t\u00eb hap\u00ebsirave em\u00ebrtuese. Megjithat\u00eb, ka shqet\u00ebsime se nj\u00eb pod ose kontejner mund t\u00eb monopolizoj\u00eb t\u00eb gjitha burimet e disponueshme. P\u00ebr t\u00eb parandaluar nj\u00eb situat\u00eb t\u00eb till\u00eb, p\u00ebrdoret kufiri i gam\u00ebs limit Range \u2013 politika e kufizimit t\u00eb shp\u00ebrndarjes s\u00eb burimeve (p\u00ebr pod\u00ebt ose kontejner\u00ebt) n\u00eb hap\u00ebsir\u00ebn em\u00ebrtuese.<\/p>\n

Kufiri i gam\u00ebs ofron kufizime q\u00eb mund t\u00eb:<\/p>\n