{"id":34735,"date":"2019-10-31T22:00:06","date_gmt":"2019-10-31T19:00:06","guid":{"rendered":"https:\/\/prohoster.info\/blog\/znakomstvo-s-helm-3\/"},"modified":"2019-10-31T22:00:06","modified_gmt":"2019-10-31T19:00:06","slug":"znakomstvo-s-helm-3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/znakomstvo-s-helm-3","title":{"rendered":"Njohja me Helm 3","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Njohja me Helm 3\" src=\"\/wp-content\/uploads\/2019\/05\/6de0e2887ddcc802f1dd71c902325401.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i><b>Sh\u00ebn. p\u00ebrk.<\/b>: 16 maj 2023 \u2014 nj\u00eb ngjarje e r\u00ebnd\u00ebsishme n\u00eb zhvillimin e menaxherit t\u00eb paketave p\u00ebr Kubernetes \u2014 Helm. N\u00eb k\u00ebt\u00eb dit\u00eb u prezantua versioni i par\u00eb alpha i nj\u00eb versioni t\u00eb r\u00ebnd\u00ebsish\u00ebm t\u00eb projektit \u2014 3.0. Dalja e tij do t\u00eb sjell\u00eb ndryshime t\u00eb konsiderueshme dhe t\u00eb shum\u00ebpritura n\u00eb Helm, p\u00ebr t\u00eb cilat shum\u00eb n\u00eb komunitetin Kubernetes kan\u00eb shpres\u00eb t\u00eb madhe. Ne vet\u00eb jemi pjes\u00eb e k\u00ebsaj, pasi e p\u00ebrdorim aktivisht Helm p\u00ebr t\u00eb realizuar aplikacione: e kemi integruar at\u00eb n\u00eb mjetin ton\u00eb p\u00ebr realizimin e CI\/CD <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/flant\/werf\">werf<\/a><\/noindex> dhe nga rasti n\u00eb rast, kontribuojm\u00eb me mund\u00ebsit\u00eb tona n\u00eb zhvillimin e upstream. Ky p\u00ebrkthim bashkon 7 sh\u00ebnime nga blogu zyrtar i Helm, t\u00eb cilat jan\u00eb dedikuar p\u00ebr versionin e par\u00eb alpha t\u00eb Helm 3 dhe tregojn\u00eb historin\u00eb e projektit dhe karakteristikat kryesore t\u00eb Helm 3. Autori i tyre \u00ebsht\u00eb Matt \u00abbacongobbler\u00bb Fisher, nj\u00eb punonj\u00ebs i Microsoft dhe nj\u00eb nga mbajt\u00ebsit kryesor\u00eb t\u00eb Helm.<\/i><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>15 tetor 2015 lindi projekti, tani i njohur si Helm. Vet\u00ebm nj\u00eb vit pas themelimit, komuniteti i Helm u bashkua me Kubernetes, duke punuar aktivisht n\u00eb Helm 2. N\u00eb qershor 2018, Helm <noindex><a rel=\"nofollow\" href=\"https:\/\/www.cncf.io\/blog\/2018\/06\/01\/cncf-to-host-helm\/\">u b\u00eb pjes\u00eb e CNCF<\/a><\/noindex> si nj\u00eb projekt n\u00eb zhvillim (incubating). Tani po shkojm\u00eb n\u00eb t\u00eb tashmen \u2014 dhe ja, po afrohet versioni i par\u00eb alpha i Helm 3 <i>(ky version <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/helm\/helm\/releases\/tag\/v3.0.0-alpha.1\">ka ndodhur<\/a><\/noindex> n\u00eb mes t\u00eb majit \u2014 sh\u00ebn. i p\u00ebrk.<\/i>.<\/p>\n<p>N\u00eb k\u00ebt\u00eb material do t\u00eb flas p\u00ebr fillimet tona, si arrit\u00ebm n\u00eb k\u00ebt\u00eb faz\u00eb, do t\u00eb paraqes disa karakteristika unike q\u00eb jan\u00eb disponible n\u00eb versionin e par\u00eb alfa t\u00eb Helm 3 dhe do t\u00eb shpjegoj se si planifikojm\u00eb t\u00eb zhvillohemi m\u00eb tej.<\/p>\n<p>P\u00ebrmbledhje:<\/p>\n<ul>\n<li>historia e krijimit t\u00eb Helm;<\/li>\n<li>lajmi i but\u00eb me Tiller<\/li>\n<li>repozitor\u00ebt e chart-\u00ebve;<\/li>\n<li>menaxhimi i l\u00ebshimeve;<\/li>\n<li>ndryshimet n\u00eb var\u00ebsit\u00eb e chart-\u00ebve;<\/li>\n<li>chart-a t\u00eb bibliotek\u00ebs;<\/li>\n<li>\u00e7far\u00eb duhet t\u00eb b\u00ebni m\u00eb pas?<\/li>\n<\/ul>\n<p><\/p>\n<h2>Historia e krijimit t\u00eb Helm<\/h2>\n<p><\/p>\n<h3>Lindja<\/h3>\n<p>\nHelm 1 filloi si nj\u00eb projekt Open Source, i krijuar nga kompania Deis. Ne ishim nj\u00eb startup i vog\u00ebl, <noindex><a rel=\"nofollow\" href=\"https:\/\/blogs.microsoft.com\/blog\/2017\/04\/10\/microsoft-acquire-deis-help-companies-innovate-containers\/\">i absorbuar<\/a><\/noindex> nga Microsoft pranver\u00ebn e vitit 2017. Projekti yn\u00eb tjet\u00ebr Open Source, gjithashtu me emrin Deis, kishte nj\u00eb mjet <code>deisctl<\/code>, i cili p\u00ebrdorej (p\u00ebrve\u00e7 t\u00eb tjerave) p\u00ebr t\u00eb instaluar dhe menaxhuar platform\u00ebn Deis n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/coreos\/fleet\">klasterin Fleet<\/a><\/noindex>. N\u00eb at\u00eb koh\u00eb, Fleet ishte nj\u00eb nga platformat e para p\u00ebr orkestrimin e kontejner\u00ebve.<\/p>\n<p>N\u00eb mes t\u00eb vitit 2015, ne vendos\u00ebm t\u00eb ndryshojm\u00eb kursin dhe e kaluam Deis (n\u00eb at\u00eb koh\u00eb i riem\u00ebruar n\u00eb Deis Workflow) nga Fleet n\u00eb Kubernetes. Nj\u00eb nga t\u00eb par\u00ebt ishte riprojektimi i mjetit t\u00eb instalimit <code>deisctl<\/code>. E p\u00ebrdor\u00ebm at\u00eb p\u00ebr instalimin dhe menaxhimin e Deis Workflow n\u00eb klasterin Fleet.<\/p>\n<p>Helm 1 \u00ebsht\u00eb krijuar sipas modeleve t\u00eb menaxher\u00ebve t\u00eb njohur t\u00eb paketave, si Homebrew, apt dhe yum. Q\u00ebllimi kryesor i tij ishte t\u00eb thjeshtonte detyra t\u00eb tilla si paketimi dhe instalimi i aplikacioneve n\u00eb Kubernetes. Zyrtarisht, Helm u prezantua n\u00eb vitin 2015 n\u00eb konferenc\u00ebn KubeCon n\u00eb San Francisco.<\/p>\n<p>P\u00ebrpjekja jon\u00eb e par\u00eb me Helm kishte sukses, megjithat\u00eb nuk kaluam pa kufizime serioze. Ai merrte nj\u00eb grup manifestesh Kubernetes, t\u00eb pasuruara me gjenerues si input YAML. <i>(front-matter)<\/i>*, dhe ngarkohej rezultati n\u00eb Kubernetes.<\/p>\n<p><i>* <b>Sh\u00ebn. p\u00ebrk.<\/b>: Nga versioni i par\u00eb t\u00eb Helm, sintaksa YAML ishte zgjedhur p\u00ebr p\u00ebrshkrimin e burimeve Kubernetes, dhe n\u00eb shkruarjen e konfigurimeve ishin mb\u00ebshtetur shabllonat Jinja dhe skenar\u00ebt Python. M\u00eb shum\u00eb rreth k\u00ebsaj dhe nd\u00ebrtimit t\u00eb versionit t\u00eb par\u00eb t\u00eb Helm n\u00eb p\u00ebrgjith\u00ebsi, ne kemi shkruar n\u00eb kapitullin \"Nj\u00eb histori e shkurt\u00ebr e Helm\". <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/417079\/\">k\u00ebtij materiali<\/a><\/noindex>.<\/i><\/p>\n<p>P\u00ebr shembull, p\u00ebr t\u00eb z\u00ebvend\u00ebsuar nj\u00eb fush\u00eb n\u00eb skedarin YAML, duhet t\u00eb shtoni n\u00eb manifest k\u00ebt\u00eb konstrukcion:<\/p>\n<pre><code class=\"plaintext\">#helm:generate sed -i -e s|ubuntu-debootstrap|fluffy-bunny| my\/pod.yaml<\/code><\/pre>\n<p>\n\u00cbsht\u00eb e mrekullueshme q\u00eb sot ekzistojn\u00eb shabllonizues, apo jo?<\/p>\n<p>P\u00ebr shum\u00eb arsye, ky instalues i hersh\u00ebm t\u00eb Kubernetes k\u00ebrkoi nj\u00eb list\u00eb t\u00eb caktuar t\u00eb skedar\u00ebve t\u00eb manifestit dhe ekzekutoi vet\u00ebm nj\u00eb sekuenc\u00eb t\u00eb vog\u00ebl t\u00eb ngjarjeve t\u00eb fiksuara. P\u00ebrdorimi i tij ishte aq i v\u00ebshtir\u00eb, saq\u00eb ekipi R&amp;D i Deis Workflow kishte v\u00ebshtir\u00ebsi kur p\u00ebrpiqej t\u00eb transferonte produktin e tij n\u00eb k\u00ebt\u00eb platform\u00eb \u2014 megjithat\u00eb, farat e ideve ishin tashm\u00eb mbjellur. P\u00ebrpjekja jon\u00eb e par\u00eb u b\u00eb nj\u00eb mund\u00ebsi e shk\u00eblqyer p\u00ebr t\u00eb m\u00ebsuar: kuptuam se ishim me t\u00eb v\u00ebrtet\u00eb t\u00eb apasionuar pas krijimit t\u00eb mjeteve pragmatike q\u00eb zgjidhnin probleme t\u00eb p\u00ebrditshme p\u00ebr p\u00ebrdoruesit tan\u00eb.<\/p>\n<p>Duke u mb\u00ebshtetur n\u00eb p\u00ebrvoj\u00ebn e gabimeve t\u00eb kaluara, ne filluam zhvillimin e Helm 2.<\/p>\n<h3>Krijimi i Helm 2<\/h3>\n<p>\nN\u00eb fund t\u00eb vitit 2015, ekipi yn\u00eb u kontaktua nga ekipi i Google. Ata po punonin mbi nj\u00eb mjet t\u00eb ngjash\u00ebm p\u00ebr Kubernetes. Manageri i rreshtimit p\u00ebr Kubernetes ishte nj\u00eb port i nj\u00eb mjeti ekzistues q\u00eb p\u00ebrdorej p\u00ebr Google Cloud Platform. \"A do t\u00eb d\u00ebshironim, \u2014 pyet\u00ebn ata, \u2014 t\u00eb kalonin disa dit\u00eb duke diskutuar p\u00ebr ngjashm\u00ebrit\u00eb dhe dallimet?\"<\/p>\n<p>N\u00eb janar 2016, ekipet e Helm dhe t\u00eb Menaxherit t\u00eb Disavantazhit u takuan n\u00eb Seattle p\u00ebr t\u00eb ndar\u00eb ide. Bisedimet p\u00ebrfunduan me nj\u00eb plan ambicioz: t\u00eb bashkonin t\u00eb dy projektet p\u00ebr t\u00eb krijuar Helm 2. S\u00eb bashku me Deis dhe Google, djemt\u00eb nga ekipi i zhvilluesve u bashkuan me <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/skippbox\">SkippBox<\/a><\/noindex> <i>(tani i p\u00ebrfshir\u00eb n\u00eb Bitnami \u2014 sh\u00ebn. p\u00ebrkth.)<\/i>, dhe ne filluam pun\u00ebn mbi Helm 2.<\/p>\n<p>Donim t\u00eb ruanim leht\u00ebsin\u00eb e p\u00ebrdorimit t\u00eb Helm, por t\u00eb shtonim n\u00eb vazhdim:<\/p>\n<ul>\n<li> shabllon\u00ebt e chart-eve p\u00ebr personalizim;<\/li>\n<li> menaxhim brenda klasterit p\u00ebr ekipet;<\/li>\n<li> nj\u00eb depandenc\u00eb e klasit t\u00eb par\u00eb p\u00ebr chart-e;<\/li>\n<li> nj\u00eb format t\u00eb stabilizuar paketash me mund\u00ebsi n\u00ebnshkrimi;<\/li>\n<li> nj\u00eb p\u00ebrkushtim t\u00eb fort\u00eb ndaj versionimit semantik dhe ruajtjes s\u00eb p\u00ebrputhshm\u00ebris\u00eb mbrapsht midis versioneve.<\/li>\n<\/ul>\n<p>\nP\u00ebr t\u00eb arritur k\u00ebto q\u00ebllime, nj\u00eb komponent i dyt\u00eb u shtua n\u00eb ekosistemin e Helm. Ky komponent brenda klasterit quhej Tiller dhe merrej me instalimin dhe menaxhimin e Helm-chart-eve.<\/p>\n<p>Q\u00eb nga dalja e Helm 2 n\u00eb vitin 2016, Kubernetes ka kaluar n\u00ebp\u00ebr disa risit\u00eb e m\u00ebdha. U krijua menaxhimi i aksesit mbi baza rolesh (<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/422801\/\">RBAC<\/a><\/noindex>), e cila n\u00eb fund z\u00ebvend\u00ebsoi kontrollin e aksesit bazuar n\u00eb atribute (ABAC). U prezantuan tipe t\u00eb reja burimesh (Deployments ende ishin n\u00eb faz\u00ebn beta). U shpik\u00ebn Definicioni i Burimeve t\u00eb Personalizuara ( n\u00eb fillim u quajt\u00ebn Burime t\u00eb Pal\u00ebve t\u00eb Treta ose TPRs). \u00c7far\u00eb \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishmja \u2014 u shfaq nj\u00eb grup praktikash m\u00eb t\u00eb mira.<\/p>\n<p>N\u00eb sfondin e t\u00eb gjitha k\u00ebtyre ndryshimeve, Helm vazhdoi t\u00eb sh\u00ebrbej\u00eb me besnik\u00ebri p\u00ebr p\u00ebrdoruesit e Kubernetes. Pas tre vjet\u00ebsh dhe shum\u00eb shtesave t\u00eb reja, u b\u00eb e qart\u00eb se ishte koha p\u00ebr t\u00eb b\u00ebr\u00eb ndryshime t\u00eb r\u00ebnd\u00ebsishme n\u00eb baz\u00ebn e kodit, n\u00eb m\u00ebnyr\u00eb q\u00eb Helm t\u00eb mund t\u00eb p\u00ebrmbushte nevojat n\u00eb rritje t\u00eb ekosistemit n\u00eb zhvillim.<\/p>\n<h2>lajmi i but\u00eb me Tiller<\/h2>\n<p>\nGjat\u00eb zhvillimit t\u00eb Helm 2, ne prezantuam Tiller si pjes\u00eb t\u00eb integrimit ton\u00eb me Menaxherin e Disavantazhit nga Google. Tiller luajti nj\u00eb rol t\u00eb r\u00ebnd\u00ebsish\u00ebm p\u00ebr ekipet q\u00eb punonin n\u00eb nj\u00eb klaster t\u00eb p\u00ebrbashk\u00ebt: ai lejonte specialist\u00ebt e ndrysh\u00ebm q\u00eb t\u00eb p\u00ebrdorin infrastruktur\u00ebn t\u00eb bashk\u00ebpunonin me t\u00eb nj\u00ebjtin set l\u00ebshimesh.<\/p>\n<p>Duke qen\u00eb se kontrolli i aksesit bazuar n\u00eb role (RBAC) ishte aktivizuar si standard n\u00eb Kubernetes 1.6, p\u00ebrdorimi i Tiller n\u00eb produkcion b\u00ebhej m\u00eb i v\u00ebshtir\u00eb. P\u00ebr shkak t\u00eb numrit t\u00eb madh t\u00eb mund\u00ebsive politike t\u00eb siguris\u00eb, pozita jon\u00eb ishte q\u00eb t\u00eb ofronim nj\u00eb konfigurim leht\u00ebsues si standard. Kjo lejonte fillestar\u00ebt t\u00eb eksperimentonin me Helm dhe Kubernetes pa pasur nevoj\u00eb t\u00eb thelloheshin fillimisht n\u00eb konfigurimet e siguris\u00eb. Fatkeq\u00ebsisht, kjo konfigurim leht\u00ebsues mund t\u00eb jepte p\u00ebrdoruesve nj\u00eb gam\u00eb t\u00eb gjer\u00eb lejesh q\u00eb ata nuk i nevojiteshin. Inxhinier\u00ebt DevOps dhe SRE duhej t\u00eb m\u00ebsonin hapa shtes\u00eb operacional\u00eb duke instaluar Tiller n\u00eb nj\u00eb klaster me shum\u00eb p\u00ebrdorues.<\/p>\n<p>Pas m\u00ebsimit t\u00eb m\u00ebnyr\u00ebs si p\u00ebrfaq\u00ebsuesit e komunitetit p\u00ebrdornin Helm n\u00eb situata t\u00eb caktuara, ne kuptuam se sistemi i menaxhimit t\u00eb l\u00ebshimeve Tiller nuk kishte nevoj\u00eb t\u00eb mb\u00ebshtetej n\u00eb nj\u00eb komponent brenda klasterit p\u00ebr t\u00eb mb\u00ebshtetur shtetat ose p\u00ebr t\u00eb funksionuar si nj\u00eb qend\u00ebr qendrore me informacion p\u00ebr l\u00ebshimin. N\u00eb vend t\u00eb k\u00ebsaj, ne mund t\u00eb merrnim thjesht informacion nga API-serveri i Kubernetes, t\u00eb gjeneronim chart nga ana e klientit dhe t\u00eb ruanim nj\u00eb regjist\u00ebr t\u00eb instalimit n\u00eb Kubernetes.<\/p>\n<p>Detyra kryesore e Tiller mund t\u00eb realizohej edhe pa Tiller, prandaj nj\u00eb nga vendimet tona t\u00eb para p\u00ebr Helm 3 ishte komplet heqja e Tiller.<\/p>\n<p>Me largimin e Tiller, modeli i siguris\u00eb s\u00eb Helm u thjeshtua ndjesh\u00ebm. Helm 3 tani mb\u00ebshtet t\u00eb gjitha m\u00ebnyrat moderne t\u00eb siguris\u00eb, identifikimit dhe autorizimit t\u00eb Kubernetes aktual. Lejet e Helm p\u00ebrcaktohen me an\u00eb t\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/configuration\/organize-cluster-access-kubeconfig\/\">skedarit kubeconfig<\/a><\/noindex>. Administrator\u00ebt e klasterit mund t\u00eb kufizojn\u00eb t\u00eb drejtat e p\u00ebrdoruesve me \u00e7do nivel detaji. Rilizat akoma ruhen brenda klasterit, funksionaliteti i mbetur i Helm mbetet.<\/p>\n<h2>Repozitoret e chart-eve<\/h2>\n<p>\nN\u00eb nj\u00eb nivel t\u00eb lart\u00eb, depoja e chart-eve \u00ebsht\u00eb vendi ku mund t\u00eb ruani dhe t\u00eb ndani chart-et. Klienti Helm paketonte dhe d\u00ebrgon chart-et n\u00eb depo. Th\u00ebn\u00eb ndryshe, depoja e chart-eve \u00ebsht\u00eb nj\u00eb server HTTP temelor me nj\u00eb dosje index.yaml dhe disa chart-e t\u00eb paketuar.<\/p>\n<p>Megjith\u00ebse ka disa p\u00ebrfitime nga kjo q\u00eb API e depozit\u00ebs s\u00eb chart-eve p\u00ebrmbush k\u00ebrkesat m\u00eb themelore p\u00ebr ruajtje, ajo ka gjithashtu disa disavantazhe:<\/p>\n<ul>\n<li> Depozitat e chart-eve jan\u00eb pak kompatibile me shumic\u00ebn e zbatimeve t\u00eb siguris\u00eb q\u00eb nevojiten n\u00eb mjedisin e prodhimit. K\u00ebtu, prania e nj\u00eb API standard p\u00ebr autentifikimin dhe autorizimin \u00ebsht\u00eb jasht\u00ebzakonisht e r\u00ebnd\u00ebsishme n\u00eb skenar\u00ebt e prodhimit.<\/li>\n<li> Veglat e Helm p\u00ebr t\u00eb ndjekur origjin\u00ebn e chart-it, t\u00eb p\u00ebrdorura p\u00ebr n\u00ebnshkrimin, verifikimin e integritetit dhe origjin\u00ebn e chart-it, jan\u00eb nj\u00eb pjes\u00eb opsionale e procesit t\u00eb publikimit t\u00eb Chart-it.<\/li>\n<li> N\u00eb skenar\u00ebt shum\u00ebp\u00ebrdorues, e nj\u00ebjta chart mund t\u00eb ngarkohet nga nj\u00eb p\u00ebrdorues tjet\u00ebr, duke dyfishuar hap\u00ebsir\u00ebn e nevojshme p\u00ebr ruajtjen e p\u00ebrmbajtjes s\u00eb nj\u00ebjt\u00eb. P\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem jan\u00eb zhvilluar depo m\u00eb t\u00eb men\u00e7ura, megjithat\u00eb ato nuk jan\u00eb pjes\u00eb e specifikimit formal.<\/li>\n<li> P\u00ebrdorimi i nj\u00eb skedari indeksi t\u00eb vet\u00ebm p\u00ebr k\u00ebrkimin, ruajtjen e metadata dhe marrjen e chart-eve e ka komplikuar zhvillimin e realizimeve t\u00eb sigurta shum\u00ebp\u00ebrdorues.<\/li>\n<\/ul>\n<p>\nProjekt <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/docker\/distribution\">Docker Distribution<\/a><\/noindex> (i njohur gjithashtu si Docker Registry v2) \u00ebsht\u00eb pasardh\u00ebsi i Docker Registry dhe faktikisht p\u00ebrfaq\u00ebson nj\u00eb grup mjetesh p\u00ebr paketimin, d\u00ebrgimin, ruajtjen dhe shp\u00ebrndarjen e imazheve Docker. Shum\u00eb sh\u00ebrbime t\u00eb m\u00ebdha cloud ofrojn\u00eb produkte mbi baz\u00ebn e Distribution. Fal\u00eb k\u00ebsaj v\u00ebmendjeje t\u00eb rritur, projekti Distribution ka p\u00ebrfituar nga p\u00ebrmir\u00ebsime t\u00eb vazhdueshme, praktikat m\u00eb t\u00eb mira n\u00eb fush\u00ebn e siguris\u00eb dhe testimin n\u00eb kushte 'beteje', duke u transformuar n\u00eb nj\u00eb nga heronjt\u00eb m\u00eb t\u00eb suksessh\u00ebm t\u00eb paq\u00ebruar n\u00eb bot\u00ebn Open Source.<\/p>\n<p>Por a e dini se projekti Distribution \u00ebsht\u00eb zhvilluar p\u00ebr t\u00eb shp\u00ebrndar\u00eb \u00e7do lloj p\u00ebrmbajtjeje, jo vet\u00ebm imazhe kontejner\u00ebsh?<\/p>\n<p>Fal\u00ebnderit p\u00ebr p\u00ebrpjekjet <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opencontainers.org\/\">Open Container Initiative<\/a><\/noindex> (ose OCI), Helm-chartet mund t\u00eb vendosen n\u00eb \u00e7do instanc\u00eb Distribution. Deri tani, ky proces ka nj\u00eb karakter eksperimental. Puna p\u00ebr mb\u00ebshtetje t\u00eb fjal\u00ebkalimeve dhe funksioneve t\u00eb tjera t\u00eb nevojshme p\u00ebr Helm 3 nuk ka p\u00ebrfunduar ende, por jemi shum\u00eb t\u00eb k\u00ebnaqur me mund\u00ebsin\u00eb p\u00ebr t\u00eb m\u00ebsuar nga zbulimet e b\u00ebra nga ekipet OCI dhe Distribution gjat\u00eb k\u00ebtyre viteve. Dhe fal\u00eb mentorimit dhe udh\u00ebheqjes s\u00eb tyre, po m\u00ebsojm\u00eb se \u00e7far\u00eb \u00ebsht\u00eb operimi i nj\u00eb sh\u00ebrbimi me disponueshm\u00ebri t\u00eb lart\u00eb n\u00eb nj\u00eb shkall\u00eb t\u00eb madhe.<\/p>\n<p>Nj\u00eb p\u00ebrshkrim m\u00eb i detajuar i disa ndryshimeve t\u00eb ardhshme n\u00eb depozit\u00eb t\u00eb Helm-chart-it \u00ebsht\u00eb n\u00eb dispozicion <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.bacongobbler.com\/post\/2019-01-25-distributing-with-distribution\/\">n\u00eb lidhje<\/a><\/noindex>.<\/p>\n<h2>Menaxhimi i l\u00ebshimeve<\/h2>\n<p>\nN\u00eb Helm 3, gjendja e aplikacionit ndjeket brenda klasterit nga nj\u00eb \u00e7ift objektesh:<\/p>\n<ul>\n<li> objekti release \u2014 p\u00ebrfaq\u00ebson nj\u00eb instanc\u00eb t\u00eb aplikacionit;<\/li>\n<li> sekreti i versionit release \u2014 p\u00ebrfaq\u00ebson gjendjen e d\u00ebshiruar t\u00eb aplikacionit n\u00eb nj\u00eb moment t\u00eb caktuar (p.sh., l\u00ebshimi i nj\u00eb versioni t\u00eb ri).<\/li>\n<\/ul>\n<p>\nThirrja <code>helm install<\/code> krijon objektin release dhe sekretin e versionit release. Thirrja <code>helm upgrade<\/code> k\u00ebrkon nj\u00eb objekt release (t\u00eb cilin mund ta ndryshoj\u00eb) dhe krijon nj\u00eb sekret t\u00eb ri t\u00eb versionit release, duke p\u00ebrfshir\u00eb vlerat e reja dhe manifestin e p\u00ebrgatitur.<\/p>\n<p>Objekti Release p\u00ebrmban informacion n\u00eb lidhje me l\u00ebshimin, ku l\u00ebshimi \u00ebsht\u00eb nj\u00eb instalim specifik i nj\u00eb chart t\u00eb em\u00ebruar dhe vlerave. Ky objekt p\u00ebrshkruan metadata-n e nivelit t\u00eb lart\u00eb p\u00ebr l\u00ebshimin. Objekti Release ruhet gjat\u00eb gjith\u00eb ciklit t\u00eb jet\u00ebs s\u00eb aplikacionit dhe vepron si pronar i t\u00eb gjitha secretioneve t\u00eb versioneve t\u00eb l\u00ebshimeve, si dhe t\u00eb gjith\u00eb objekteve q\u00eb krijohen drejtp\u00ebrdrejt nga chart-i i Helm.<\/p>\n<p>Sekreti i versionit t\u00eb lansimit lidh lansimin me nj\u00eb seri revizioni (instalimi, p\u00ebrdit\u00ebsimet, rikthimet, fshirja).<\/p>\n<p>N\u00eb Helm 2, revizionet ishin ekskluzivisht t\u00eb radhitur. Thirrja <code>helm install<\/code> krijonte v1, p\u00ebrdit\u00ebsimi n\u00eb vijim (upgrade) - v2, dhe k\u00ebshtu me radh\u00eb. Objekti Release dhe secretionet e versioneve t\u00eb l\u00ebshimeve u bashkuan n\u00eb nj\u00eb objekt t\u00eb njohur si revision. Revision-t ruheshin n\u00eb t\u00eb nj\u00ebjt\u00ebn hap\u00ebsir\u00eb emri si Tiller, q\u00eb do t\u00eb thoshte se \u00e7do l\u00ebshim ishte 'global' n\u00eb aspektin e hap\u00ebsir\u00ebs s\u00eb emrit; si rezultat, mund t\u00eb p\u00ebrdorej vet\u00ebm nj\u00eb instanc\u00eb emri.<\/p>\n<p>N\u00eb Helm 3, \u00e7do l\u00ebshim \u00ebsht\u00eb i lidhur me nj\u00eb ose m\u00eb shum\u00eb secretionet e versioneve t\u00eb l\u00ebshimeve. Objekti Release gjithmon\u00eb p\u00ebrshkruan l\u00ebshimin aktual t\u00eb zbatuar n\u00eb Kubernetes. \u00c7do secretion version l\u00ebshimi p\u00ebrshkruan vet\u00ebm nj\u00eb version t\u00eb k\u00ebtij l\u00ebshimi. Nj\u00eb p\u00ebrdit\u00ebsim (upgrade), p\u00ebr shembull, do t\u00eb krijonte nj\u00eb sekret t\u00eb ri t\u00eb versionit t\u00eb l\u00ebshimit dhe pastaj do t\u00eb nd\u00ebrronte objektin Release p\u00ebr t\u00eb treguar k\u00ebt\u00eb version t\u00eb ri. N\u00eb rastin e rikthimit (rollback), mund t\u00eb p\u00ebrdoren secretionet e m\u00ebparshme t\u00eb versioneve t\u00eb l\u00ebshimeve p\u00ebr t\u00eb kthyer l\u00ebshimin n\u00eb gjendjen e m\u00ebparshme.<\/p>\n<p>Pas heqjes s\u00eb Tiller, Helm 3 ruan t\u00eb dh\u00ebnat p\u00ebr l\u00ebshimin n\u00eb t\u00eb nj\u00ebjt\u00ebn hap\u00ebsir\u00eb emri me l\u00ebshimin. Ky ndryshim lejon instalimin e nj\u00eb chart-i me t\u00eb nj\u00ebjtin em\u00ebr l\u00ebshimi n\u00eb nj\u00eb hap\u00ebsir\u00eb emri tjet\u00ebr, dhe t\u00eb dh\u00ebnat ruhen midis p\u00ebrdit\u00ebsimeve\/riparimeve t\u00eb klasterit n\u00eb etcd. P\u00ebr shembull, mund t\u00eb instaloni WordPress n\u00eb hap\u00ebsir\u00ebn e emrit 'foo', dhe pastaj n\u00eb hap\u00ebsir\u00ebn e emrit 'bar', dhe t\u00eb dy l\u00ebshimet mund t\u00eb quhen 'wordpress'.<\/p>\n<h2>Ndryshimet n\u00eb var\u00ebsit\u00eb e kartave<\/h2>\n<p>\nKartat, t\u00eb paketuar (me <code>helm package<\/code>) p\u00ebr p\u00ebrdorim me Helm 2, mund t\u00eb instalohet me Helm 3; megjithat\u00eb, procesi i zhvillimit t\u00eb grafik\u00ebve \u00ebsht\u00eb rishikuar plot\u00ebsisht, k\u00ebshtu q\u00eb disa ndryshime duhet t\u00eb b\u00ebhen p\u00ebr t\u00eb vazhduar zhvillimin e grafik\u00ebve me Helm 3. N\u00eb ve\u00e7anti, sistemi i menaxhimit t\u00eb var\u00ebsive t\u00eb grafik\u00ebve ka ndryshuar.<\/p>\n<p>Sistemi i menaxhimit t\u00eb var\u00ebsive t\u00eb grafik\u00ebve kaloi nga <code>requirements.yaml<\/code> dhe <code>requirements.lock<\/code> n\u00eb <code>Chart.yaml<\/code> dhe <code>Chart.lock<\/code>. Kjo do t\u00eb thot\u00eb se grafik\u00ebt q\u00eb p\u00ebrdor\u00ebn komand\u00ebn <code>helm dependency<\/code>, k\u00ebrkojn\u00eb disa konfigurime p\u00ebr t\u00eb funksionuar n\u00eb Helm 3.<\/p>\n<p>Le t\u00eb shohim nj\u00eb shembull. Shtojm\u00eb nj\u00eb var\u00ebsi n\u00eb grafik\u00ebt n\u00eb Helm 2 dhe shohim se \u00e7far\u00eb do t\u00eb ndryshoj\u00eb kur kalojm\u00eb n\u00eb Helm 3.<\/p>\n<p>N\u00eb Helm 2 <code>requirements.yaml<\/code> dukej si m\u00eb posht\u00eb:<\/p>\n<pre><code class=\"plaintext\">dependencies:\n- name: mariadb\n  version: 5.x.x\n  repository: https:\/\/kubernetes-charts.storage.googleapis.com\/\n  condition: mariadb.enabled\n  tags:\n    - database<\/code><\/pre>\n<p>\nN\u00eb Helm 3, e nj\u00ebjta var\u00ebsi do t\u00eb reflektohet n\u00eb <code>Chart.yaml<\/code>:<\/p>\n<pre><code class=\"plaintext\">dependencies:\n- name: mariadb\n  version: 5.x.x\n  repository: https:\/\/kubernetes-charts.storage.googleapis.com\/\n  condition: mariadb.enabled\n  tags:\n    - database<\/code><\/pre>\n<p>\nGrafik\u00ebt ende ngarkohen dhe vendosen n\u00eb drejtorin\u00eb <code>charts\/<\/code>, prandaj subgrafik\u00ebt <i>(subcharts)<\/i>, q\u00eb ndodhen n\u00eb katalogun <code>charts\/<\/code>, do t\u00eb vazhdojn\u00eb t\u00eb funksionojn\u00eb pa ndryshime.<\/p>\n<h2>Prezantimi i Grafik\u00ebve t\u00eb Bibliotekave<\/h2>\n<p>\nHelm 3 mb\u00ebshtet nj\u00eb klas\u00eb grafik\u00ebsh q\u00eb quhet grafik\u00eb-bibliotek\u00eb <i>(library chart)<\/i>. Ky chart p\u00ebrdoret nga charts t\u00eb tjera, por vet\u00eb nuk krijon asnj\u00eb artefakt t\u00eb l\u00ebshimit. Shabllonat e chart-eve t\u00eb bibliotek\u00ebs mund t\u00eb shpallin vet\u00ebm elemente <code>p\u00ebrcakto<\/code>. P\u00ebrmbajtje tjet\u00ebr thjesht injorohet. Kjo lejon p\u00ebrdoruesit t\u00eb rip\u00ebrdorin dhe ndajn\u00eb fragmente kodi q\u00eb mund t\u00eb p\u00ebrdoren n\u00eb shum\u00eb chart-e, duke shmangur k\u00ebshtu p\u00ebrs\u00ebritjen dhe duke ndjekur parimin <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Don%27t_repeat_yourself\">DRY<\/a><\/noindex>.<\/p>\n<p>Chart-et library shpallen n\u00eb seksionin <code>var\u00ebsi<\/code> n\u00eb skedarin <code>Chart.yaml<\/code>. Instalimi dhe menaxhimi i tyre nuk ndryshon nga chart-et e tjera.<\/p>\n<pre><code class=\"plaintext\">var\u00ebsi:\n  - emri: mylib\n    version: 1.x.x\n    repo: quay.io<\/code><\/pre>\n<p>\nNe me padurim presim rastet e p\u00ebrdorimit q\u00eb ky komponent do t\u00eb hap\u00eb para zhvilluesve t\u00eb chart-eve, si dhe praktikat m\u00eb t\u00eb mira q\u00eb mund t\u00eb lindin fal\u00eb chart-eve library.<\/p>\n<h2>\u00c7far\u00eb ndodh m\u00eb tej?<\/h2>\n<p>\nHelm 3.0.0-alpha.1 \u2014 baza mbi t\u00eb cil\u00ebn fillojm\u00eb t\u00eb krijojm\u00eb nj\u00eb version t\u00eb ri t\u00eb Helm. N\u00eb k\u00ebt\u00eb artikull kam p\u00ebrshkruar disa mund\u00ebsi interesante t\u00eb Helm 3. Shum\u00eb prej tyre jan\u00eb ende n\u00eb fazat fillestare t\u00eb zhvillimit dhe kjo \u00ebsht\u00eb n\u00eb rregull; thelbi i l\u00ebshimit alfa \u00ebsht\u00eb t\u00eb provosh iden\u00eb, t\u00eb mbledh\u00ebsh mendime nga p\u00ebrdoruesit e par\u00eb dhe t\u00eb konfirmosh supozimet tona.<\/p>\n<p>Sapo t\u00eb l\u00ebshohet versione alfa <i>(kujtoj, se kjo <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/helm\/helm\/releases\/tag\/v3.0.0-alpha.1\">ka ndodhur tashm\u00eb<\/a><\/noindex> \u2014 sh\u00ebnim i p\u00ebrkthyesit.)<\/i>, ne do t\u00eb fillojm\u00eb t\u00eb pranojm\u00eb patches p\u00ebr Helm 3 nga komuniteti. \u00cbsht\u00eb thelb\u00ebsore t\u00eb krijojm\u00eb nj\u00eb baz\u00eb solide q\u00eb do t\u00eb lejoj\u00eb zhvillimin dhe pranimet e karakteristikave t\u00eb reja, nd\u00ebrsa p\u00ebrdoruesit do t\u00eb ndihen t\u00eb angazhuar n\u00eb proces, duke hapur tiketa dhe duke kontribuar me rregullime.<\/p>\n<p>N\u00eb k\u00ebt\u00eb artikull p\u00ebrpiqem t\u00eb p\u00ebrmbledh disa p\u00ebrmir\u00ebsime t\u00eb r\u00ebnd\u00ebsishme q\u00eb do t\u00eb vin\u00eb n\u00eb Helm 3, megjithat\u00eb kjo list\u00eb nuk mund t\u00eb quhet e plot\u00eb n\u00eb asnj\u00eb rast. Plani i plot\u00eb p\u00ebr Helm 3 p\u00ebrfshin inovacione t\u00eb tilla si strategji t\u00eb p\u00ebrmir\u00ebsuara t\u00eb p\u00ebrdit\u00ebsimit, integrim m\u00eb t\u00eb thell\u00eb me regjistrat OCI dhe p\u00ebrdorimin e skemave JSON p\u00ebr t\u00eb verifikuar vlerat e grafik\u00ebve. Gjithashtu, ne planifikojm\u00eb t\u00eb pastrojm\u00eb baz\u00ebn e kodit dhe t\u00eb azhurnojm\u00eb ato pjes\u00eb q\u00eb kan\u00eb mbetur pa v\u00ebmendje gjat\u00eb tre viteve t\u00eb fundit.<\/p>\n<p>N\u00ebse ndiheni se kemi humbur di\u00e7ka, do t\u00eb ishim t\u00eb lumtur t\u00eb d\u00ebgjonim mendimet tuaja!<\/p>\n<p>Bashkohuni n\u00eb diskutimin ton\u00eb n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.slack.com\/\">kanalet tona t\u00eb Slack<\/a><\/noindex>:<\/p>\n<ul>\n<li> <code>#helm-users<\/code> p\u00ebr pyetje dhe komunikim t\u00eb thjesht\u00eb me komunitetin;<\/li>\n<li> <code>#helm-dev<\/code> p\u00ebr diskutimin e pull requests, kodit dhe gabimeve.<\/li>\n<\/ul>\n<p>\nMund t\u00eb bisedoni n\u00eb Thirrjet Publike p\u00ebr Zhvilluesit q\u00eb mbahen \u00e7do jav\u00eb t\u00eb enjten n\u00eb or\u00ebn 19:30 MSK. Takimet jan\u00eb t\u00eb dedikuara p\u00ebr diskutimin e detyrave q\u00eb po punojn\u00eb zhvilluesit kryesor\u00eb dhe komuniteti, si dhe temave q\u00eb do t\u00eb diskutohen gjat\u00eb jav\u00ebs. \u00c7dokush \u00ebsht\u00eb e mir\u00ebpritur t\u00eb bashkohet dhe t\u00eb marr\u00eb pjes\u00eb n\u00eb takim. Linku \u00ebsht\u00eb i disponuesh\u00ebm n\u00eb kanalin Slack. <code>#helm-dev<\/code>.<\/p>\n<h2>P.S. nga p\u00ebrkthyesi<\/h2>\n<p>\nLexoni gjithashtu n\u00eb blogun ton\u00eb:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/417079\/\">Menaxheri i paketave p\u00ebr Kubernetes - Helm: e kaluara, e tanishmja, e ardhmja.<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/438814\/\">Nj\u00eb pamje e qet\u00eb mbi Helm 2: 'K\u00ebshtu si\u00e7 \u00ebsht\u00eb...'<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/420437\/\">Njohje praktike me menaxherin e paketave p\u00ebr Kubernetes - Helm.<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/441964\/\">K\u00ebshilla dhe truke p\u00ebr Kubernetes: transferimi i burimeve funksionale n\u00eb menaxhimin e Helm 2.<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/336170\/\">Praktik\u00eb me dapp. Pjesa 2. D\u00ebrgimi i imazheve Docker n\u00eb Kubernetes duke p\u00ebrdorur Helm.<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/453734\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: 16 \u043c\u0430\u044f \u044d\u0442\u043e\u0433\u043e \u0433\u043e\u0434\u0430 \u2014 \u0437\u043d\u0430\u0447\u0438\u043c\u0430\u044f \u0432\u0435\u0445\u0430 \u0432 \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0438 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440\u0430 \u043f\u0430\u043a\u0435\u0442\u043e\u0432 \u0434\u043b\u044f Kubernetes \u2014 Helm. \u0412 \u044d\u0442\u043e\u0442 \u0434\u0435\u043d\u044c \u0431\u044b\u043b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d \u043f\u0435\u0440\u0432\u044b\u0439 \u0430\u043b\u044c\u0444\u0430-\u0440\u0435\u043b\u0438\u0437 \u0431\u0443\u0434\u0443\u0449\u0435\u0439 \u043a\u0440\u0443\u043f\u043d\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u2014 3.0. \u0415\u0451 \u0432\u044b\u0445\u043e\u0434 \u043f\u0440\u0438\u043d\u0435\u0441\u0451\u0442 \u0432 Helm \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0435 \u0438 \u0434\u043e\u043b\u0433\u043e\u0436\u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043d\u043e\u0433\u0438\u0435 \u0432 Kubernetes-\u0441\u043e\u043e\u0431\u0449\u0435\u0441\u0442\u0432\u0435 \u0432\u043e\u0437\u043b\u0430\u0433\u0430\u044e\u0442 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u043d\u0430\u0434\u0435\u0436\u0434\u044b. \u041a \u0442\u0430\u043a\u043e\u0432\u044b\u043c \u043e\u0442\u043d\u043e\u0441\u0438\u043c\u0441\u044f \u0438 \u043c\u044b \u0441\u0430\u043c\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0430\u043a\u0442\u0438\u0432\u043d\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26173,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34735","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.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: 16 \u043c\u0430\u044f \u044d\u0442\u043e\u0433\u043e \u0433\u043e\u0434\u0430 \u2014 \u0437\u043d\u0430\u0447\u0438\u043c\u0430\u044f \u0432\u0435\u0445\u0430 \u0432 \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0438 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440\u0430 \u043f\u0430\u043a\u0435\u0442\u043e\u0432 \u0434\u043b\u044f Kubernetes \u2014 Helm. \u0412 \u044d\u0442\u043e\u0442 \u0434\u0435\u043d\u044c \u0431\u044b\u043b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d \u043f\u0435\u0440\u0432\u044b\u0439 \u0430\u043b\u044c\u0444\u0430-\u0440\u0435\u043b\u0438\u0437 \u0431\u0443\u0434\u0443\u0449\u0435\u0439 \u043a\u0440\u0443\u043f\u043d\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u2014 3.0. \u0415\u0451 \u0432\u044b\u0445\u043e\u0434 \u043f\u0440\u0438\u043d\u0435\u0441\u0451\u0442 \u0432 Helm \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0435 \u0438 \u0434\u043e\u043b\u0433\u043e\u0436\u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043d\u043e\u0433\u0438\u0435 \u0432 Kubernetes-\u0441\u043e\u043e\u0431\u0449\u0435\u0441\u0442\u0432\u0435 \u0432\u043e\u0437\u043b\u0430\u0433\u0430\u044e\u0442 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u043d\u0430\u0434\u0435\u0436\u0434\u044b. \u041a \u0442\u0430\u043a\u043e\u0432\u044b\u043c \u043e\u0442\u043d\u043e\u0441\u0438\u043c\u0441\u044f \u0438 \u043c\u044b \u0441\u0430\u043c\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\" \/>\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\/znakomstvo-s-helm-3\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\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\udd47\u0417\u043d\u0430\u043a\u043e\u043c\u0441\u0442\u0432\u043e \u0441 Helm 3 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: 16 \u043c\u0430\u044f \u044d\u0442\u043e\u0433\u043e \u0433\u043e\u0434\u0430 \u2014 \u0437\u043d\u0430\u0447\u0438\u043c\u0430\u044f \u0432\u0435\u0445\u0430 \u0432 \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0438 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440\u0430 \u043f\u0430\u043a\u0435\u0442\u043e\u0432 \u0434\u043b\u044f Kubernetes \u2014 Helm. \u0412 \u044d\u0442\u043e\u0442 \u0434\u0435\u043d\u044c \u0431\u044b\u043b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d \u043f\u0435\u0440\u0432\u044b\u0439 \u0430\u043b\u044c\u0444\u0430-\u0440\u0435\u043b\u0438\u0437 \u0431\u0443\u0434\u0443\u0449\u0435\u0439 \u043a\u0440\u0443\u043f\u043d\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u2014 3.0. \u0415\u0451 \u0432\u044b\u0445\u043e\u0434 \u043f\u0440\u0438\u043d\u0435\u0441\u0451\u0442 \u0432 Helm \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0435 \u0438 \u0434\u043e\u043b\u0433\u043e\u0436\u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043d\u043e\u0433\u0438\u0435 \u0432 Kubernetes-\u0441\u043e\u043e\u0431\u0449\u0435\u0441\u0442\u0432\u0435 \u0432\u043e\u0437\u043b\u0430\u0433\u0430\u044e\u0442 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u043d\u0430\u0434\u0435\u0436\u0434\u044b. \u041a \u0442\u0430\u043a\u043e\u0432\u044b\u043c \u043e\u0442\u043d\u043e\u0441\u0438\u043c\u0441\u044f \u0438 \u043c\u044b \u0441\u0430\u043c\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/znakomstvo-s-helm-3\" \/>\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=\"2019-10-31T19:00:06+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:00:06+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\udd47Kintroduktimi n\u00eb Helm 3 | ProHoster","description":"Sh\u00ebnim: 16 maji i k\u00ebtij viti \u00ebsht\u00eb nj\u00eb kthes\u00eb e r\u00ebnd\u00ebsishme n\u00eb zhvillimin e menaxherit t\u00eb paketave p\u00ebr Kubernetes \u2014 Helm. N\u00eb k\u00ebt\u00eb dit\u00eb u prezantua versioni i par\u00eb alfa i versionit t\u00eb ardhsh\u00ebm t\u00eb madh t\u00eb projektit \u2014 3.0. Dalja e tij do t\u00eb sjell\u00eb ndryshime t\u00eb r\u00ebnd\u00ebsishme dhe t\u00eb pritura n\u00eb Helm, p\u00ebr t\u00eb cilat shum\u00eb n\u00eb komunitetin Kubernetes kan\u00eb shpresa t\u00eb m\u00ebdha. Ndryshime t\u00eb tilla jemi edhe ne vet\u00eb, pasi jemi aktiv\u00eb.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/znakomstvo-s-helm-3","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\u0417\u043d\u0430\u043a\u043e\u043c\u0441\u0442\u0432\u043e \u0441 Helm 3 | ProHoster","og:description":"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: 16 \u043c\u0430\u044f \u044d\u0442\u043e\u0433\u043e \u0433\u043e\u0434\u0430 \u2014 \u0437\u043d\u0430\u0447\u0438\u043c\u0430\u044f \u0432\u0435\u0445\u0430 \u0432 \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0438 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440\u0430 \u043f\u0430\u043a\u0435\u0442\u043e\u0432 \u0434\u043b\u044f Kubernetes \u2014 Helm. \u0412 \u044d\u0442\u043e\u0442 \u0434\u0435\u043d\u044c \u0431\u044b\u043b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d \u043f\u0435\u0440\u0432\u044b\u0439 \u0430\u043b\u044c\u0444\u0430-\u0440\u0435\u043b\u0438\u0437 \u0431\u0443\u0434\u0443\u0449\u0435\u0439 \u043a\u0440\u0443\u043f\u043d\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u2014 3.0. \u0415\u0451 \u0432\u044b\u0445\u043e\u0434 \u043f\u0440\u0438\u043d\u0435\u0441\u0451\u0442 \u0432 Helm \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0435 \u0438 \u0434\u043e\u043b\u0433\u043e\u0436\u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043d\u043e\u0433\u0438\u0435 \u0432 Kubernetes-\u0441\u043e\u043e\u0431\u0449\u0435\u0441\u0442\u0432\u0435 \u0432\u043e\u0437\u043b\u0430\u0433\u0430\u044e\u0442 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u043d\u0430\u0434\u0435\u0436\u0434\u044b. \u041a \u0442\u0430\u043a\u043e\u0432\u044b\u043c \u043e\u0442\u043d\u043e\u0441\u0438\u043c\u0441\u044f \u0438 \u043c\u044b \u0441\u0430\u043c\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0430\u043a\u0442\u0438\u0432\u043d\u043e","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/znakomstvo-s-helm-3","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":"2019-10-31T19:00:06+00:00","article:modified_time":"2019-10-31T19:00:06+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34735","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":"2026-01-21 20:26:53","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 23:08:04","updated":"2026-01-21 20:26:53","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\/34735","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=34735"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34735\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/26173"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=34735"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=34735"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=34735"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}