{"id":81130,"date":"2020-05-11T01:42:39","date_gmt":"2020-05-10T23:42:39","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo"},"modified":"2020-05-11T01:42:39","modified_gmt":"2020-05-10T23:42:39","slug":"kubernetes-open-source-protiv-vendorskogo","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo","title":{"rendered":"Kubernetes: open source kund\u00ebr atij me mark\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><b>P\u00ebrsh\u00ebndetje, un\u00eb quhem Dmitry Krasnov. Tani e m\u00eb shum\u00eb se pes\u00eb vjet merrem me administrimin e klastereve Kubernetes dhe nd\u00ebrtimin e arkitekturave t\u00eb komplikuara mikrosh\u00ebrbimesh. N\u00eb fillim t\u00eb k\u00ebtij viti lan\u00e7uam nj\u00eb sh\u00ebrbim p\u00ebr menaxhimin e klastereve Kubernetes mbi Containerum. Duke e shfryt\u00ebzuar rastin, do t\u00eb tregoj se \u00e7far\u00eb \u00ebsht\u00eb ky Kubernetes dhe si ndryshon integrimi me nj\u00eb ofrues n\u00eb krahasim me open source.<\/b><\/p>\n<p>P\u00ebr t\u00eb filluar, \u00e7far\u00eb \u00ebsht\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/overview\/what-is-kubernetes\/\">Kubernetes<\/a><\/noindex>. Kjo \u00ebsht\u00eb nj\u00eb sistem p\u00ebr menaxhimin e konteiner\u00ebve n\u00eb nj\u00eb num\u00ebr t\u00eb madh hostesh. Nga greqishtja, p\u00ebrndryshe, p\u00ebrkthehet si \"pilot\" ose \"p\u00ebrgjegj\u00ebs\". Fillimisht \u00ebsht\u00eb zhvilluar nga Google, dhe m\u00eb pas \u00ebsht\u00eb dh\u00ebn\u00eb si nj\u00eb kontribut teknologjik n\u00eb Cloud Native Computing Foundation, nj\u00eb organizat\u00eb nd\u00ebrkomb\u00ebtare jo fitimprur\u00ebse q\u00eb bashkon zhvilluesit kryesor\u00eb t\u00eb bot\u00ebs, p\u00ebrdoruesit p\u00ebrfundimtar\u00eb dhe ofruesit e teknologjive t\u00eb konteiner\u00ebve. <\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source kund\u00ebr atij me mark\u00eb\" src=\"\/wp-content\/uploads\/2020\/05\/7cbe773adf691ad29c4aaa7a2c8f0461.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>P\u00ebr t\u00eb menaxhuar nj\u00eb num\u00ebr t\u00eb madh konteiner\u00ebsh <\/h3>\n<p>\nTani t\u00eb marrim vesh se \u00e7far\u00eb jan\u00eb k\u00ebta konteiner\u00eb. K\u00ebta jan\u00eb aplikacione me t\u00eb gjith\u00eb mjedisin e tyre \u2013 kryesisht, bibliotekat nga t\u00eb cilat varet funksionimi i programit. T\u00eb gjitha k\u00ebto jan\u00eb paketuar n\u00eb arkiva dhe paraqiten si imazhe, q\u00eb mund t\u00eb ekzekutohen pavar\u00ebsisht nga sistemi operativ, t\u00eb testohen dhe jo vet\u00ebm. Por ka nj\u00eb problem \u2013 t\u00eb menaxhosh konteiner\u00ebt n\u00eb nj\u00eb num\u00ebr t\u00eb madh hostesh \u00ebsht\u00eb shum\u00eb e komplikuar. Prandaj, Kubernetes u krijua. <\/p>\n<p>Imazhi i konteinerit p\u00ebrb\u00ebn aplikacionin plus var\u00ebsit\u00eb e tij. Aplikacioni, var\u00ebsit\u00eb e tij dhe imazhi i sistemit t\u00eb skedar\u00ebve t\u00eb OS jan\u00eb t\u00eb vendosura n\u00eb pjes\u00eb t\u00eb ndryshme t\u00eb imazhit, t\u00eb ashtuquajturat shtresa. Shtresat mund t\u00eb riciklohen p\u00ebr konteiner\u00eb t\u00eb ndrysh\u00ebm. P\u00ebr shembull, nj\u00eb shtres\u00eb baz\u00eb Ubuntu mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb gjitha aplikacionet n\u00eb kompani. Gjat\u00eb ekzekutimit t\u00eb konteiner\u00ebve nuk ka nevoj\u00eb p\u00ebr t\u00eb ruajtur n\u00eb host shum\u00eb kopje t\u00eb nj\u00eb shtrese baz\u00eb. Kjo lejon optimizimin e ruajtjes dhe shp\u00ebrndarjes s\u00eb imazheve.<\/p>\n<p>Kur ne duam t\u00eb shkarkojm\u00eb nj\u00eb aplikacion nga nj\u00eb kontejner, shtresat e nevojshme vendosen nj\u00ebra mbi tjetr\u00ebn dhe formojn\u00eb nj\u00eb sistem t\u00eb skedar\u00ebve t\u00eb mbivendosur. Nj\u00eb shtres\u00eb p\u00ebr shkrim vendoset mbi t\u00eb, e cila, kur kontejneri ndalet, fshihet. Kjo garanton q\u00eb kur kontejneri hapet, aplikacioni gjithmon\u00eb ka nj\u00eb mjedis t\u00eb nj\u00ebjt\u00eb, i cili nuk mund t\u00eb ndryshohet. Kjo siguron riprodhueshm\u00ebrin\u00eb e mjedisit n\u00eb sisteme t\u00eb ndryshme operative t\u00eb hostit. Pa marr\u00eb parasysh n\u00ebse \u00ebsht\u00eb Ubuntu apo CentOS, mjedisi gjithmon\u00eb do t\u00eb jet\u00eb i nj\u00ebjt\u00eb. P\u00ebr m\u00eb tep\u00ebr, kontejneri \u00ebsht\u00eb i izoluar nga hosti p\u00ebrmes mekanizmave t\u00eb inkorporuar n\u00eb kernelin Linux. Aplikacionet n\u00eb kontejner nuk shohin skedar\u00ebt, proceset e hostit dhe kontejner\u00ebt e tjer\u00eb. Kjo izolim i aplikacioneve nga sistemi operativ i hostit ofron nj\u00eb shtes\u00eb t\u00eb siguris\u00eb. <\/p>\n<p>P\u00ebr menaxhimin e konteiner\u00ebve n\u00eb host, ka shum\u00eb mjete. Mjeti m\u00eb i njohur \u00ebsht\u00eb Docker. Ai ofron nj\u00eb cik\u00ebl t\u00eb plot\u00eb jet\u00ebsor p\u00ebr konteiner\u00ebt. Megjithat\u00eb, ai funksionon vet\u00ebm n\u00eb nj\u00eb host. Kur \u00ebsht\u00eb e nevojshme t\u00eb menaxhohen konteiner\u00ebt n\u00eb shum\u00eb hoste, Docker mund ta kthej\u00eb jet\u00ebn e inxhinier\u00ebve n\u00eb nj\u00eb ferr. Prandaj, Kubernetes u krijua.<\/p>\n<p>K\u00ebrkesa p\u00ebr Kubernetes \u00ebsht\u00eb pik\u00ebrisht p\u00ebr shkak t\u00eb mund\u00ebsis\u00eb p\u00ebr t\u00eb menaxhuar grupe kontejner\u00ebsh n\u00eb shum\u00eb hoste si entitete t\u00eb vetme. Popullariteti i sistemit siguron mund\u00ebsin\u00eb e nd\u00ebrtimit t\u00eb DevOps ose Operacioneve t\u00eb Zhvillimit, ku Kubernetes p\u00ebrdoret p\u00ebr t\u00eb nisur proceset e k\u00ebtij DevOps.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source kund\u00ebr atij me mark\u00eb\" src=\"\/wp-content\/uploads\/2020\/05\/40f253f4445595376231bb384253763d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Figura 1. Nj\u00eb diagram\u00eb e thjesht\u00eb e funksionimit t\u00eb Kubernetes<\/i><\/p>\n<h3>Automatizimi i plot\u00eb<\/h3>\n<p>\nDevOps, n\u00eb parim, \u00ebsht\u00eb automatizimi i procesit t\u00eb zhvillimit. Thjesht, zhvilluesit shkruajn\u00eb kodin, i cili ngarkohet n\u00eb nj\u00eb depo. M\u00eb pas, ky kod mund t\u00eb nd\u00ebrtohet automatikisht menj\u00ebher\u00eb n\u00eb nj\u00eb kontejner me t\u00eb gjitha bibliotekat, t\u00eb testohet dhe \"t\u00eb p\u00ebrfundoj\u00eb\" n\u00eb faz\u00ebn tjet\u00ebr \u2013 Staging, dhe m\u00eb pas menj\u00ebher\u00eb n\u00eb Production.<\/p>\n<p>S\u00eb bashku me Kubernetes, DevOps lejon automatizimin e k\u00ebtij procesi, n\u00eb m\u00ebnyr\u00eb q\u00eb ai t\u00eb zhvillohet praktikisht pa pjes\u00ebmarrjen e vet\u00eb zhvilluesve. Si rezultat, ndodhin p\u00ebrshpejtimet e ndjeshme n\u00eb nd\u00ebrtim, p\u00ebr shkak se zhvilluesit nuk e kan\u00eb k\u00ebt\u00eb detyr\u00eb n\u00eb kompjuterin e tyre \u2014 ata thjesht shkruajn\u00eb nj\u00eb pjes\u00eb t\u00eb kodit, e shtyjn\u00eb kodin n\u00eb depo, pas s\u00eb cil\u00ebs fillon pipeline-i, i cili mund t\u00eb p\u00ebrfshij\u00eb procesin e nd\u00ebrtimit, testimit dhe implementimit. K\u00ebshtu ndodh me \u00e7do komit, prandaj testimi \u00ebsht\u00eb i vazhduesh\u00ebm.<\/p>\n<p>N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, p\u00ebrdorimi i kontejner\u00ebve siguron q\u00eb e gjith\u00eb ambienti i k\u00ebsaj programi t\u00eb dal\u00eb n\u00eb prodhim n\u00eb t\u00eb nj\u00ebjt\u00ebn form\u00eb si\u00e7 \u00ebsht\u00eb testuar. Pra, nuk do t\u00eb ndodhin probleme si \u00abn\u00eb test ishin versionet nj\u00eb, n\u00eb prodhim \u2013 t\u00eb tjera, dhe kur u vendos \u2013 gjith\u00e7ka ra\u00bb. Dhe pasi sot kemi nj\u00eb tendenc\u00eb drejt arkitektur\u00ebs mikrosh\u00ebrbimeve, kur n\u00eb vend t\u00eb nj\u00eb aplikacioni t\u00eb madh ka qindra t\u00eb vogla, at\u00ebher\u00eb p\u00ebr ta administruar ato manualisht, do t\u00eb k\u00ebrkohet nj\u00eb staf i madh punonj\u00ebsish. Prandaj ne p\u00ebrdorim Kubernetes.<\/p>\n<p><b><\/p>\n<h3>P\u00ebrfitimet, p\u00ebrfitimet, p\u00ebrfitimet<\/h3>\n<p><\/b><br \/>\nN\u00ebse flasim p\u00ebr avantazhet e Kubernetes si platform\u00eb, ajo ka p\u00ebrfitime t\u00eb konsiderueshme n\u00eb aspektin e menaxhimit t\u00eb arkitektur\u00ebs mikrosh\u00ebrbimeve. <\/p>\n<ul>\n<li> <b>Menaxhimi i shum\u00eb replikave.<\/b> E r\u00ebnd\u00ebsishmja \u2014 \u00ebsht\u00eb menaxhimi i kontejner\u00ebve n\u00eb shum\u00eb hoste. Dhe \u00e7far\u00eb \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishmja, \u2014 menaxhimi i shum\u00eb replikave t\u00eb aplikacioneve n\u00eb kontejner\u00eb si nj\u00eb nj\u00ebsi t\u00eb vetme. Fal\u00eb k\u00ebtij fakti, inxhinier\u00ebt nuk duhet t\u00eb kujdesen p\u00ebr \u00e7do kontejner individual. N\u00ebse nj\u00eb nga kontejner\u00ebt d\u00ebshton, at\u00ebher\u00eb Kubernetes e sheh k\u00ebt\u00eb dhe e rinis at\u00eb p\u00ebrs\u00ebri. <\/li>\n<li> <b>Rrjeti klasterik.<\/b> Gjithashtu, Kubernetes ka nj\u00eb rrjet klasterik t\u00eb quajtur me hap\u00ebsir\u00ebn e vet adresore. Fal\u00eb k\u00ebtij fakti, \u00e7do pod ka adres\u00ebn e vet. Pod-i n\u00ebnkupton nj\u00ebsin\u00eb minimale strukturale t\u00eb klasterit, n\u00eb t\u00eb cil\u00ebn drejtohen p\u00ebrve\u00e7 kontejner\u00ebve. P\u00ebr m\u00eb tep\u00ebr, Kubernetes ka funksionalitet q\u00eb kombinon n\u00eb vetvete balancuesin e ngarkes\u00ebs dhe Zbulimin e Sh\u00ebrbimit. Kjo lejon eliminimin e menaxhimit manual t\u00eb IP-adresave dhe delegimin e k\u00ebsaj detyre te Kubernetes. Dhe kontrolli automatik mbi sh\u00ebndetin do t\u00eb ndihmoj\u00eb n\u00eb zbulimin e problemeve dhe n\u00eb ridrejtimin e trafikut n\u00eb podet funksionale.<\/li>\n<li> <b>Menaxhimi i konfigurimeve. <\/b>Kur menaxhimi i nj\u00eb s\u00ebr\u00eb t\u00eb madhe aplikacionesh b\u00ebhet e v\u00ebshtir\u00eb t\u00eb menaxhosh konfigurimin e aplikacioneve. P\u00ebr k\u00ebt\u00eb, Kubernetes ka burime speciale ConfigMap. Ato lejojn\u00eb ruajtjen n\u00eb m\u00ebnyr\u00eb qendrore t\u00eb konfigurimeve dhe t'i vendosin ato n\u00eb pods gjat\u00eb nisjes s\u00eb aplikacioneve. Ky mekaniz\u00ebm garanton konsistenc\u00ebn e konfigurimit, pavar\u00ebsisht n\u00ebse ka dhjet\u00eb ose nj\u00ebqind replika aplikacionesh. <\/li>\n<li> <b>V\u00ebllime t\u00eb P\u00ebrshtatshme. <\/b>Kontejner\u00ebt n\u00eb thelb jan\u00eb imutab\u00ebl dhe n\u00eb momentin e ndalimit t\u00eb nj\u00eb konteineri, t\u00eb dh\u00ebnat e shkruara n\u00eb sistemin e skedar\u00ebve do t\u00eb shkat\u00ebrrohen. Por disa aplikacione ruajn\u00eb t\u00eb dh\u00ebna direkt n\u00eb disk. P\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem, Kubernetes ka funksionalitet p\u00ebr menaxhimin e ruajtjes s\u00eb disqeve \u2014 V\u00ebllime t\u00eb P\u00ebrshtatshme. Ky mekaniz\u00ebm p\u00ebrdor nj\u00eb ruajtje t\u00eb jashtme p\u00ebr t\u00eb dh\u00ebnat, mund t\u00eb ofroj\u00eb ruajtje t\u00eb p\u00ebrhershme, t\u00eb bllokuar ose t\u00eb skedarit n\u00eb konteiner\u00ebt. Ky zgjidhje lejon ruajtjen e t\u00eb dh\u00ebnave ndaras nga pun\u00ebtor\u00ebt, duke i shp\u00ebtuar ata n\u00eb rastin e d\u00ebshtimit t\u00eb k\u00ebtyre pun\u00ebtor\u00ebve.<\/li>\n<li> <b>Balancues Ngarkese.<\/b> Pavar\u00ebsisht se n\u00eb Kubernetes ne menaxhojm\u00eb entitete abstrakte si Deployment, StatefulSet etj., n\u00eb fund t\u00eb fundit konteiner\u00ebt fillojn\u00eb n\u00eb servera t\u00eb zakonsh\u00ebm <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sq\/vps\/abuzoustojchivye-vps\/\"   title=\"makina virtuale\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"4246\">makina virtuale<\/a> apo harduer\u00eb. Ato nuk jan\u00eb perfekte dhe mund t\u00eb bien n\u00eb \u00e7do moment. Kubernetes do ta v\u00ebrej\u00eb k\u00ebt\u00eb dhe do t\u00eb drejtoj\u00eb trafikun e brendsh\u00ebm n\u00eb replika t\u00eb tjera. Por \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb me trafikun q\u00eb vjen nga jasht\u00eb? N\u00ebse thjesht drejtojm\u00eb trafikun n\u00eb nj\u00eb nga pun\u00ebtor\u00ebt, \u00e7far\u00eb ndodh n\u00eb rastin e d\u00ebshtimit t\u00eb tij, sh\u00ebrbimi do t\u00eb b\u00ebhet i paq\u00ebndruesh\u00ebm. P\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem, Kubernetes ka sh\u00ebrbime si Balancues Ngarkese. Ato jan\u00eb t\u00eb destinuara p\u00ebr konfigurimin automatik t\u00eb nj\u00eb balancuesi t\u00eb jasht\u00ebm t\u00eb trafikut n\u00eb t\u00eb gjith\u00eb pun\u00ebtor\u00ebt n\u00eb grumbull. Ky balancues i jasht\u00ebm drejton trafikun e jasht\u00ebm n\u00eb pun\u00ebtor\u00eb dhe vet\u00eb monitoron statusin e tyre. N\u00ebse nj\u00eb ose m\u00eb shum\u00eb pun\u00ebtor\u00eb b\u00ebhen t\u00eb paarritsh\u00ebm, at\u00ebher\u00eb trafiku drejtohet n\u00eb t\u00eb tjer\u00ebt. Kjo lejon krijimin e sh\u00ebrbimeve me disponueshm\u00ebri t\u00eb lart\u00eb p\u00ebrmes Kubernetes.<\/li>\n<\/ul>\n<p>\nKubernetes tregon m\u00eb s\u00eb miri potencialin e tij kur fillon arkitekturat mikrosh\u00ebrbimore. T\u00eb implementosh sistemin n\u00eb nj\u00eb arkitektur\u00eb klasike \u00ebsht\u00eb e mundur, por pa kuptim. N\u00ebse nj\u00eb aplikacion nuk mund t\u00eb funksionoj\u00eb n\u00eb disa replika, \u00e7far\u00eb r\u00ebnd\u00ebsie ka, n\u00ebse \u00ebsht\u00eb n\u00eb Kubernetes apo jo?<\/p>\n<p><b><\/p>\n<h3>Kubernetes me burim t\u00eb hapur<\/h3>\n<p><\/b><br \/>\nKubernetes me burim t\u00eb hapur \u2013 gj\u00eb e shk\u00eblqyer: e vendos dhe funksionon. Mund t\u00eb instalohet n\u00eb serverat e tu, n\u00eb infrastruktur\u00ebn tuaj, t\u00eb vendosni master dhe workere, mbi t\u00eb cilat do t\u00eb ekzekutohen t\u00eb gjitha aplikacionet. Dhe m\u00eb e r\u00ebnd\u00ebsishmja \u2013 e gjith\u00eb kjo \u00ebsht\u00eb falas. Megjithat\u00eb, ka nuanca.<\/p>\n<ul>\n<li> E para \u2013 k\u00ebrkesat p\u00ebr njohurit\u00eb dhe p\u00ebrvoj\u00ebn e administrator\u00ebve dhe inxhinier\u00ebve q\u00eb do t\u00eb instalojn\u00eb dhe mb\u00ebshtesin gjith\u00e7ka. Duke qen\u00eb se klienti merr lirin\u00eb e plot\u00eb t\u00eb veprimit n\u00eb klaster, ai mban p\u00ebrgjegj\u00ebsin\u00eb p\u00ebr funksionimin e klasterit vet\u00eb. Dhe \u00ebsht\u00eb shum\u00eb e leht\u00eb t\u00eb d\u00ebshtosh k\u00ebtu.<\/li>\n<li> E dyta \u2013 mungesa e integrimeve. N\u00ebse e filloni Kubernetes pa pasur ndonj\u00eb platform\u00eb virtualizimi t\u00eb njohur, at\u00ebher\u00eb nuk do t\u00eb merrni t\u00eb gjith\u00eb p\u00ebrfitimet e programit. Si\u00e7 jan\u00eb p\u00ebrdorimi i Volume-ve t\u00eb q\u00ebndrueshme dhe sh\u00ebrbimeve Load balancer.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Kubernetes: open source kund\u00ebr atij me mark\u00eb\" src=\"\/wp-content\/uploads\/2020\/05\/8445e46889ca4c4d53bd91abeaa49256.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Figura 2. Arkitektura k8s<\/i><\/p>\n<p><b><\/p>\n<h3>Kubernetes nga nje ofrues<\/h3>\n<p><\/b><br \/>\nIntegrimi me ofruesin e cloud-it ofron dy mund\u00ebsi: <\/p>\n<ul>\n<li> S\u00eb pari, nj\u00eb person mund thjesht t\u00eb klikoj\u00eb butonin \u00abkrijo klaster\u00bb dhe t\u00eb marr\u00eb nj\u00eb klaster t\u00eb konfiguruar dhe gati p\u00ebr pun\u00eb.<\/li>\n<li> S\u00eb dyti, ofruesi e vendos vet klasterin dhe konfigurimin e integrimit me cloud-in.<\/li>\n<\/ul>\n<p>\nSi ndodh kjo me ne. Inxhinieri q\u00eb nis klasterin tregon se sa workera i duhen dhe me cilat parametra (p.sh., 5 workera, \u00e7do nj\u00eb me 10 CPU, 16 GB RAM dhe, le t\u00eb themi, 100 GB disk). Pas k\u00ebsaj, ai merr qasje n\u00eb klasterin e formuar tashm\u00eb. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, worker-at mbi t\u00eb cil\u00ebt ngarkohet puna, i dor\u00ebzohen plot\u00ebsisht klientit, por e gjith\u00eb plani i menaxhimit mbetet p\u00ebrgjegj\u00ebsi e ofruesit (n\u00eb rast se sh\u00ebrbimi ofrohet sipas modelit t\u00eb sh\u00ebrbimeve t\u00eb menaxhuara).<\/p>\n<p>Megjithat\u00eb, kjo skem\u00eb ka mang\u00ebsi. P\u00ebr shkak se plani i menaxhimit mbetet te ofruesi, ai nuk i jep klientit qasje t\u00eb plot\u00eb, dhe kjo redukton fleksibilitetin n\u00eb pun\u00ebn me Kubernetes. Nsometimes ndodh q\u00eb klienti d\u00ebshiron t\u00eb shtoj\u00eb nj\u00eb funksionalitet specifik te Kubernetes, p\u00ebr shembull, autentifikim p\u00ebrmes LDAP, por konfigurimi i planit t\u00eb menaxhimit nuk e lejon k\u00ebt\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source kund\u00ebr atij me mark\u00eb\" src=\"\/wp-content\/uploads\/2020\/05\/e5cff16e4280cf041917c886c146a2d0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Figura 3. Shembulli i klasterit Kubernetes nga ofruesi i cloud-it<\/i><\/p>\n<p><b><\/p>\n<h3>\u00c7far\u00eb t\u00eb zgjidhni: burim t\u00eb hapur apo nga ofruesi<\/h3>\n<p><\/b><br \/>\nPra, Kubernetes me burim t\u00eb hapur apo nga nj\u00eb furnizues? Po t\u00eb marrim Kubernetes me burim t\u00eb hapur, p\u00ebrdoruesi mund t\u00eb b\u00ebj\u00eb \u00e7far\u00ebdo q\u00eb d\u00ebshiron me t\u00eb. Por ka nj\u00eb shans t\u00eb madh t\u00eb q\u00eblloj\u00eb vet\u00eb n\u00eb k\u00ebmb\u00eb. Me furnizuesin, kjo \u00ebsht\u00eb m\u00eb e komplikuar, sepse p\u00ebr kompanin\u00eb gjith\u00e7ka \u00ebsht\u00eb menduar dhe e konfiguruar. Mang\u00ebsia m\u00eb e madhe e Kubernetes me burim t\u00eb hapur \u00ebsht\u00eb k\u00ebrkesa p\u00ebr specialist\u00eb. Me furnizuesin, kompanit\u00eb jan\u00eb t\u00eb shp\u00ebtuara nga kjo dhimbje koke, por do t'u duhet t\u00eb vendosin: t\u00eb paguajn\u00eb specialist\u00ebt e tyre ose furnizuesin.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source kund\u00ebr atij me mark\u00eb\" src=\"\/wp-content\/uploads\/2020\/05\/f14130c42049e20b2f33121e4d789cca.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<img decoding=\"async\" alt=\"Kubernetes: open source kund\u00ebr atij me mark\u00eb\" src=\"\/wp-content\/uploads\/2020\/05\/4fb1feaacd42a67a444ae1600e37d0f0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMir\u00eb, p\u00ebrfitimet jan\u00eb t\u00eb dukshme, t\u00eb disavantazhet gjithashtu jan\u00eb t\u00eb njohura. Nj\u00eb gj\u00eb \u00ebsht\u00eb e pashqyrtueshme: Kubernetes zgjidh shum\u00eb probleme, duke automatizuar menaxhimin e shum\u00eb konteiner\u00ebve. Dhe cila t\u00eb zgjidhet, me burim t\u00eb hapur apo nga nj\u00eb furnizues, - secili e merr vendimin vet.<\/p>\n<p><i>Artikullin e p\u00ebrgatiti Dmitri Krasnov, arkitekt kryesor i sh\u00ebrbimit Containerum t\u00eb ofruesit #CloudMTS <\/i><br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ru_mts\/blog\/500728\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440. \u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u044d\u0442\u043e\u0433\u043e \u0433\u043e\u0434\u0430 \u043c\u044b \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0441\u0435\u0440\u0432\u0438\u0441 \u043f\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044e \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430\u043c\u0438 Kubernetes \u043d\u0430 \u0431\u0430\u0437\u0435 Containerum. \u041f\u043e\u043b\u044c\u0437\u0443\u044f\u0441\u044c \u043f\u043e\u0432\u043e\u0434\u043e\u043c \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u043e\u0431\u043e\u0439 \u044d\u0442\u043e\u0442 \u0441\u0430\u043c\u044b\u0439 Kubernetes \u0438 \u0447\u0435\u043c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u044f \u0441 \u0432\u0435\u043d\u0434\u043e\u0440\u043e\u043c \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u043e\u0442 open source. \u0414\u043b\u044f \u043d\u0430\u0447\u0430\u043b\u0430, \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":81131,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-81130","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Kubernetes: open source \u043f\u0440\u043e\u0442\u0438\u0432 \u0432\u0435\u043d\u0434\u043e\u0440\u0441\u043a\u043e\u0433\u043e | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-05-10T23:42:39+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-10T23:42:39+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kubernetes: open source kund\u00ebr nj\u00eb ofruesi | ProHoster","description":"P\u00ebrsh\u00ebndetje, un\u00eb quhem Dmitri Krasnov. Prej m\u00eb shum\u00eb se pes\u00eb vitesh merrem me administrimin e klastereve Kubernetes dhe krijimin e arkitekturave mikros_services komplekse.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo","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\udd47Kubernetes: open source \u043f\u0440\u043e\u0442\u0438\u0432 \u0432\u0435\u043d\u0434\u043e\u0440\u0441\u043a\u043e\u0433\u043e | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo","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-05-10T23:42:39+00:00","article:modified_time":"2020-05-10T23:42:39+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"81130","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 16:04:23","updated":"2022-09-27 22:17:56","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/81130","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=81130"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/81130\/revisions"}],"predecessor-version":[{"id":164121,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/81130\/revisions\/164121"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/81131"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=81130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=81130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=81130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}