{"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 Kubernetes. Krijimi i konteiner\u00ebve t\u00eb vegj\u00ebl<\/a><\/noindex>
\nPraktikat m\u00eb t\u00eb mira Kubernetes. Organizimi i Kubernetes me hap\u00ebsira emri<\/a><\/noindex>
\nPraktikat m\u00eb t\u00eb mira t\u00eb Kubernetes. Verifikimi i jet\u00ebs s\u00eb Kubernetes me ndihm\u00ebn e testeve Readiness dhe Liveness<\/a><\/noindex><\/p>\n

P\u00ebr \u00e7do burim Kubernetes, ka mund\u00ebsin\u00eb p\u00ebr t\u00eb vendosur dy lloje t\u00eb k\u00ebrkesave \u2014 Requests dhe Limits. E para p\u00ebrshkruan k\u00ebrkesat minimale p\u00ebr disponueshm\u00ebrin\u00eb e burimeve t\u00eb lira n\u00eb nod, t\u00eb nevojshme p\u00ebr t\u00eb nisur nj\u00eb kontejner ose pod, e dyta kufizon rrept\u00ebsisht 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 implementoni 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 e mbaron memorien ose i mungon fuqia e procesorit. N\u00eb k\u00ebt\u00eb artikull do t\u00eb shqyrtojm\u00eb se si mund t\u00eb zgjidhni problemet e munges\u00ebs s\u00eb fuqis\u00eb kompjuterike n\u00ebp\u00ebrmjet k\u00ebrkesave p\u00ebr burime dhe kufizimeve.<\/p>\n

K\u00ebrkesat Requests dhe kufizimet Limits jan\u00eb mekanizma q\u00eb Kubernetes p\u00ebrdor p\u00ebr t\u00eb menaxhuar burime t\u00eb tilla si procesori dhe memoria. K\u00ebrkesat jan\u00eb ato, p\u00ebr shkak t\u00eb t\u00eb cilave kontejneri merr garanci p\u00ebr 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 \u00ebsht\u00eb n\u00eb gjendje ta ofroj\u00eb. Kufizimet Limits kontrollojn\u00eb q\u00eb burimet e k\u00ebrkuara nga kontejneri t\u00eb mos tejkalojn\u00eb kurr\u00eb nj\u00eb vler\u00eb t\u00eb caktuar.<\/p>\n

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

Kontejneri mund t\u00eb rris\u00eb fuqit\u00eb kompjuterike vet\u00ebm deri n\u00eb nj\u00eb kufi t\u00eb caktuar, pas s\u00eb cil\u00ebs do t\u00eb kufizohet. Le t\u00eb shohim se si funksionon kjo. Pra, ka dy lloje burimesh \u2014 procesori dhe memoria. Planifikuesi i Kubernetes p\u00ebrdor t\u00eb dh\u00ebnat p\u00ebr k\u00ebto burime p\u00ebr t\u00eb zbuluar se ku t\u00eb nis\u00eb pod-et tuaja. Specifikimi tipik i burimeve p\u00ebr nj\u00eb pod duket k\u00ebshtu.<\/p>\n

\"Praktikat
\n
\n\u00c7do kontejner n\u00eb pod mund t\u00eb vendos\u00eb k\u00ebrkesat dhe kufizimet e tij t\u00eb veta, dhe t\u00eb gjitha k\u00ebto jan\u00eb aditive. Burimet e CPU-s\u00eb p\u00ebrcaktohen n\u00eb milikra. N\u00ebse kontejneri juaj ka nevoj\u00eb p\u00ebr dy b\u00ebrthama t\u00eb plota p\u00ebr ekzekutimin, vendosni vler\u00ebn 2000m. N\u00ebse kontejneri ka nevoj\u00eb vet\u00ebm p\u00ebr fuqin\u00eb e 1\/4 b\u00ebrthame, vlera do t\u00eb jet\u00eb 250m. Mbani parasysh se n\u00ebse caktoni nj\u00eb vler\u00eb p\u00ebr burimet e CPU-s\u00eb m\u00eb t\u00eb madhe se numri i b\u00ebrthamave t\u00eb nodit m\u00eb t\u00eb madh, at\u00ebher\u00eb ekzekutimi i pod-it tuaj nuk do t\u00eb planifikohet fare. Nj\u00eb situat\u00eb e ngjashme do t\u00eb ndodhi n\u00ebse keni nj\u00eb pod q\u00eb ka nevoj\u00eb p\u00ebr kat\u00ebr b\u00ebrthama, nd\u00ebrsa klasteri Kubernetes p\u00ebrb\u00ebhet vet\u00ebm nga dy makineri 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 (duke pasur parasysh aplikacione si llogaritjet shkencore komplekse dhe operacionet me databaza), praktik\u00ebn m\u00eb t\u00eb mir\u00eb \u00ebsht\u00eb t\u00eb vendosni K\u00ebrkesat e CPU-s\u00eb n\u00eb 1 ose m\u00eb pak, duke vazhduar me ekzekutimin e nj\u00eb numri m\u00eb t\u00eb madh replikash p\u00ebr ndryshueshm\u00ebri. Ky zgjidhje i ofron sistemit fleksibilitet dhe besueshm\u00ebri m\u00eb t\u00eb madhe.<\/p>\n

Kur b\u00ebhet fjal\u00eb p\u00ebr kufizimet e CPU-s\u00eb, gjith\u00e7ka b\u00ebhet m\u00eb interesante, pasi ajo konsiderohet nj\u00eb burim shtyp\u00ebs. N\u00ebse aplikacioni juaj fillon t\u00eb afroj\u00eb kufirin e fuqis\u00eb s\u00eb CPU-s\u00eb, Kubernetes do t\u00eb filloj\u00eb t\u00eb ngadal\u00ebsoj\u00eb kontejnerin tuaj duke p\u00ebrdorur CPU Throttling \u2014 uljen e frekuenc\u00ebs s\u00eb procesorit. Kjo do t\u00eb thot\u00eb se CPU do t\u00eb jet\u00eb artificialisht e kufizuar, duke i ofruar aplikacionit potencialisht nj\u00eb performanc\u00eb m\u00eb t\u00eb dob\u00ebt, megjithat\u00eb procesi nuk do t\u00eb ndalet ose t\u00eb d\u00ebshtoj\u00eb. <\/p>\n

Burimet e memorjes p\u00ebrcaktohen n\u00eb byte. N\u00eb p\u00ebrgjith\u00ebsi, vlera n\u00eb cil\u00ebsimet matet n\u00eb mebibyte (MiB), por mund t\u00eb caktoni \u00e7do vler\u00eb, nga byte deri n\u00eb petabyte. K\u00ebtu ka ndodhi e nj\u00ebjt\u00eb si me CPU-n\u00eb \u2014 n\u00ebse vendosni nj\u00eb k\u00ebrkes\u00eb p\u00ebr sasi memorjeje q\u00eb tejkalon kapacitetin e memorjes n\u00eb nodet tuaja, ekzekutimi i k\u00ebtij pod-i nuk do t\u00eb planifikohet. Por ndryshe nga burimet e CPU-s\u00eb, memoria nuk \u00ebsht\u00eb e kompresueshme, sepse nuk ka asnj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb kufizuar p\u00ebrdorimin e saj. Prandaj, ekzekutimi i kontejnerit do t\u00eb ndalet, sapo ai t\u00eb kaloj\u00eb kufirin e memorjes 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 nodet tuaja mund t\u00eb ofrojn\u00eb. Karakteristikat e burimeve t\u00eb p\u00ebrbashk\u00ebta 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 kontenier\u00ebve n\u00ebn default do t\u00eb ishin mjaft t\u00eb mjaftueshme q\u00eb pun\u00ebt t\u00eb zhvilloheshin pa probleme. Por bota reale nuk \u00ebsht\u00eb e till\u00eb, njer\u00ebzit mund t\u00eb harrojn\u00eb leht\u00ebsisht t\u00eb konfigurojn\u00eb p\u00ebrdorimin e burimeve ose haker\u00ebt do t\u00eb vendosin k\u00ebrkesa dhe kufij q\u00eb tejkalojn\u00eb kapacitetet reale t\u00eb infrastruktur\u00ebs. P\u00ebr t\u00eb parandaluar zhvillimin e skenar\u00ebve t\u00eb till\u00eb, mund t\u00eb konfigurohen kuota burimesh ResourceQuota dhe intervalet e kufijve LimitRange.<\/p>\n

Pas krijimit t\u00eb hap\u00ebsirave t\u00eb emrave, ato mund t\u00eb bllokohen p\u00ebrmes kuotave. P\u00ebr shembull, n\u00ebse keni hap\u00ebsira emrash prodhimi dhe zhvillimi, p\u00ebrdoret nj\u00eb model ku kuotat p\u00ebr prodhimin nuk ekzistojn\u00eb fare, nd\u00ebrsa kuotat p\u00ebr zhvillimin jan\u00eb shum\u00eb strikte. Kjo lejon q\u00eb prodhimi, n\u00eb rast t\u00eb nj\u00eb rritjeje t\u00eb papritur t\u00eb trafikut, t\u00eb marr\u00eb t\u00eb gjith\u00eb burimin e kaluar, duke bllokuar plot\u00ebsisht zhvillimin.<\/p>\n

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

\"Praktikat
\n
\nLe t\u00eb shqyrtojm\u00eb secilin prej tyre. Requests.cpu \u00ebsht\u00eb maksimalja e numrit t\u00eb kombinuar t\u00eb k\u00ebrkesave t\u00eb fuqis\u00eb procesorit q\u00eb mund t\u00eb vijn\u00eb nga t\u00eb gjith\u00eb kontenier\u00ebt e hap\u00ebsir\u00ebs s\u00eb emrave. N\u00eb k\u00ebt\u00eb shembull, mund t\u00eb keni 50 kontenier\u00eb me k\u00ebrkesa prej 10m, pes\u00eb kontenier\u00eb me k\u00ebrkesa prej 100m ose thjesht nj\u00eb kontenier me k\u00ebrkes\u00eb 500m. Pavar\u00ebsisht se sa shum\u00eb \u00ebsht\u00eb shuma e requests.cpu t\u00eb k\u00ebsaj hap\u00ebsire emri, do t\u00eb jet\u00eb n\u00eb rregull derisa ajo t\u00eb jet\u00eb m\u00eb pak se 500m.<\/p>\n

K\u00ebrkesa e memories requests.memory \u00ebsht\u00eb sasia maksimale e k\u00ebrkesave t\u00eb kombinuara t\u00eb memories q\u00eb mund t\u00eb ken\u00eb t\u00eb gjith\u00eb kontenier\u00ebt n\u00eb hap\u00ebsir\u00ebn e emrave. Si n\u00eb rastin e m\u00ebparsh\u00ebm, mund t\u00eb keni 50 kontenier\u00eb t\u00eb 2 mib, pes\u00eb kontenier\u00eb t\u00eb 20 Mib ose nj\u00eb t\u00eb vet\u00ebm me 100 Mib, derisa shuma totale e memories s\u00eb k\u00ebrkuar n\u00eb hap\u00ebsir\u00ebn e emrave t\u00eb mbetet n\u00ebn 100 mebibajt\u00eb.<\/p>\n

Limits.cpu \u00ebsht\u00eb vlera maksimale e kombinuar e fuqis\u00eb procesorit q\u00eb mund t\u00eb p\u00ebrdorin t\u00eb gjith\u00eb kontenier\u00ebt e hap\u00ebsir\u00ebs s\u00eb emrave. Mund t\u00eb mendohet si kufiri i k\u00ebrkesave t\u00eb fuqis\u00eb procesorit.<\/p>\n

Finalmente, limits.memory \u00ebsht\u00eb sasia maksimale e memories totale q\u00eb mund t\u00eb p\u00ebrdorin t\u00eb gjitha kontejner\u00ebt n\u00eb hap\u00ebsir\u00ebn e emrave. Ky kufizim \u00ebsht\u00eb p\u00ebr k\u00ebrkesat totale t\u00eb memories.
\nPra, me parazgjedhje, kontejner\u00ebt n\u00eb klusterin Kubernetes funksionojn\u00eb me burime kompjuterike t\u00eb pap\u00ebrcaktuar. Me an\u00eb t\u00eb kuotave t\u00eb burimeve, adminstrator\u00ebt e klusterit mund t\u00eb kufizojn\u00eb konsumimin e burimeve dhe krijimin e tyre bazuar n\u00eb hap\u00ebsirat e emrave. N\u00eb hap\u00ebsir\u00ebn e emrave, moduli pod ose kontejneri mund t\u00eb konsumojn\u00eb aq kapacitet CPU dhe memorje sa p\u00ebrcaktohet nga kuota e burimeve t\u00eb hap\u00ebsirave t\u00eb emrave. Sidoqoft\u00eb, ekziston shqet\u00ebsimi se nj\u00eb pod ose kontejner mund t\u00eb monopolizoj\u00eb t\u00eb gjitha burimet n\u00eb dispozicion. P\u00ebr t\u00eb parandaluar nj\u00eb situat\u00eb t\u00eb till\u00eb, p\u00ebrdoret kufiri i gam\u00ebs limit Range \u2013 nj\u00eb politik\u00eb kufizuese p\u00ebr shp\u00ebrndarjen e burimeve (p\u00ebr podet ose kontejner\u00ebt) n\u00eb hap\u00ebsir\u00ebn e emrave.<\/p>\n

Gama e limitit ofron kufizime q\u00eb mund t\u00eb:<\/p>\n