{"id":34450,"date":"2019-10-31T21:58:24","date_gmt":"2019-10-31T18:58:24","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kubernetes-zahvatit-mir-kogda-i-kak\/"},"modified":"2019-10-31T21:58:24","modified_gmt":"2019-10-31T18:58:24","slug":"kubernetes-zahvatit-mir-kogda-i-kak","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kubernetes-zahvatit-mir-kogda-i-kak","title":{"rendered":"Kubernetes do t\u00eb pushtoj\u00eb bot\u00ebn. Kur dhe si?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00eb prag t\u00eb DevOpsConf<\/a><\/noindex> Vitali Habrov<\/b> ka intervistuar\u00a0Dmitrin Stolyarov<\/b> (distol<\/a><\/noindex>), drejtorin teknik dhe bashk\u00ebthemeluesin e kompanis\u00eb \"Flant\". Vitali e pyeti Dmitrin mbi at\u00eb q\u00eb b\u00ebn \"Flant\", mbi Kubernetes, zhvillimin e ekosistemit, dhe mb\u00ebshtetje. Diskutuan pse \u00ebsht\u00eb e nevojshme Kubernetes dhe n\u00ebse v\u00ebrtet \u00ebsht\u00eb e nevojshme. Gjithashtu fol\u00ebn p\u00ebr mikrosh\u00ebrbimet, Amazon AWS, qasjen \"M\u00eb p\u00eblqen t\u00eb kem fat\" n\u00eb DevOps, t\u00eb ardhmen e Kubernetes, pse, kur dhe si do t\u00eb pushtoj\u00eb bot\u00ebn, perspektivat e DevOps dhe p\u00ebr \u00e7far\u00eb duhet t\u00eb p\u00ebrgatiten inxhinier\u00ebt n\u00eb t\u00eb ardhmen e af\u00ebrt me thjesht\u00ebsimin dhe rrjetet nervore.<\/p>\n

Origjinali i intervist\u00ebs<\/a><\/noindex> n\u00eb form\u00eb podkasti mund ta d\u00ebgjoni n\u00eb DevOps D\u00ebflop \u2014 podkast n\u00eb gjuh\u00ebn ruse mbi DevOps, nd\u00ebrsa m\u00eb posht\u00eb gjeni versionin tekstual. <\/p>\n

\"Kubernetes
\n
\nK\u00ebtu dhe m\u00eb posht\u00eb pyetjet i b\u00ebn Vitali Habrov<\/a><\/noindex> inxhinieri nga Express42.
\n<\/a><\/noindex><\/p>\n

Rreth \"Flant\"<\/h2>\n

\n\u2014 Dima, p\u00ebrsh\u00ebndetje. Ti je drejtor teknik i \"Flant<\/a><\/noindex>\" dhe gjithashtu themeluesi i tij. T\u00eb lutem, trego pak p\u00ebr at\u00eb \u00e7far\u00eb b\u00ebn kompania dhe rolin t\u00ebnd aty.<\/b><\/p>\n

\"KubernetesDmitri<\/b>: N\u00eb pamje t\u00eb par\u00eb duket se ne jemi ata q\u00eb vendosin Kubernetes dhe b\u00ebjn\u00eb di\u00e7ka me t\u00eb. Por nuk \u00ebsht\u00eb e v\u00ebrtet\u00eb. Ne filluam si nj\u00eb kompani q\u00eb merret me Linux, por prej nj\u00eb kohe t\u00eb gjat\u00eb aktiviteti yn\u00eb kryesor \u00ebsht\u00eb ofrimi i sh\u00ebrbimeve p\u00ebr projekte prodhimi dhe highload. Zakonisht nd\u00ebrtuam \u00e7do infrastruktur\u00eb nga fillimi dhe pastaj p\u00ebr shum\u00eb koh\u00eb e mbajm\u00eb n\u00ebn p\u00ebrgjegj\u00ebsi. Prandaj, puna kryesore q\u00eb b\u00ebn \u00abFlant\u00bb dhe p\u00ebr t\u00eb cil\u00ebn paguhet \u00ebsht\u00eb marrja e p\u00ebrgjegj\u00ebsis\u00eb dhe realizimi i projekteve prodhimi<\/b>.
\n

\n

\nUn\u00eb, si drejtor teknik dhe nj\u00eb nga themeluesit e kompanis\u00eb, merrem me at\u00eb q\u00eb t\u00eb mendoj vazhdimisht se si t\u00eb rris aksesin e prodhimit, t\u00eb leht\u00ebsoj operimin e tij, t\u00eb leht\u00ebsoj jet\u00ebn e administrator\u00ebve dhe t\u00eb b\u00ebj jet\u00ebn e zhvilluesve m\u00eb t\u00eb k\u00ebndshme.<\/p>\n

P\u00ebr Kubernetes<\/h2>\n

\n\u2014 Koh\u00ebt e fundit nga \u00abFlant\u00bb kam par\u00eb shum\u00eb prezantime dhe\u00a0artikujsh<\/a><\/noindex> p\u00ebr Kubernetes. Si e arrit\u00ebt k\u00ebt\u00eb?<\/b><\/p>\n

Dmitri<\/b>: Un\u00eb kam folur p\u00ebr k\u00ebt\u00eb shum\u00eb her\u00eb, por nuk e kam aspak problem t\u00eb p\u00ebrs\u00ebris. Mendoj se \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb p\u00ebrs\u00ebris k\u00ebt\u00eb tem\u00eb, sepse ka konfuzion midis arsyeve dhe pasojave.<\/p>\n

Na na duhej nevojshim nj\u00eb mjet. Kemi p\u00ebrjetuar shum\u00eb probleme, kemi luftuar, i kemi tejkaluar ato me m\u00ebnyra t\u00eb ndryshme dhe kemi ndjer\u00eb nevoj\u00ebn p\u00ebr nj\u00eb mjet. Kemi shqyrtuar shum\u00eb mund\u00ebsi t\u00eb ndryshme, kemi nd\u00ebrtuar bi\u00e7ikletat tona dhe kemi grumbulluar p\u00ebrvoj\u00eb. Gradualisht arrit\u00ebm deri n\u00eb at\u00eb pik\u00eb sa filluam t\u00eb p\u00ebrdorim Docker pothuajse menj\u00ebher\u00eb pas shfaqjes s\u00eb tij \u2014 rreth vitit 2013. N\u00eb momentin e shfaqjes s\u00eb tij, ne kishim tashm\u00eb shum\u00eb p\u00ebrvoj\u00eb me kontejner\u00ebt, ne kishim shkruar nj\u00eb analog t\u00eb \"Docker\" \u2014 disa nga mjetet tona n\u00eb Python. Me shfaqjen e Docker-it, u shfaq mund\u00ebsia p\u00ebr t\u00eb hequr ato t\u00eb \u00e7uditshme dhe p\u00ebr t\u00eb p\u00ebrdorur nj\u00eb zgjidhje t\u00eb besueshme dhe t\u00eb mb\u00ebshtetur nga komuniteti.<\/p>\n

Historia me Kubernetes \u00ebsht\u00eb e ngjashme. N\u00eb momentin kur filloi t\u00eb fitoj\u00eb terren \u2014 p\u00ebr ne kjo ishte versioni 1.2 \u2014 ne kishim tashm\u00eb nj\u00eb num\u00ebr t\u00eb madh mjetesh dhe n\u00eb Shell, dhe n\u00eb Chef, t\u00eb cilat ndonj\u00ebher\u00eb p\u00ebrpiqeshim t'i orkestronim Docker. Ne shikuam seriozisht n\u00eb drejtim t\u00eb Rancher dhe zgjidhjeve t\u00eb tjera t\u00eb ndryshme, por k\u00ebtu doli Kubernetes, ku gjith\u00e7ka ishte realizuar pik\u00ebrisht ashtu si\u00e7 do ta kishim b\u00ebr\u00eb ne ose madje m\u00eb mir\u00eb. Nuk kishte asnj\u00eb gj\u00eb p\u00ebr t\u00eb kritikuar.<\/p>\n

\u0414\u0430, \u0442\u0443\u0442 \u0435\u0441\u0442\u044c \u043a\u0430\u043a\u0430\u044f-\u0442\u043e \u043d\u0435\u0434\u043e\u0434\u0435\u043b\u043a\u0430, \u0442\u0430\u043c \u043a\u0430\u043a\u0430\u044f-\u0442\u043e \u043d\u0435\u0434\u043e\u0434\u0435\u043b\u043a\u0430\u00a0\u2014 \u043c\u043d\u043e\u0433\u043e \u043d\u0435\u0434\u043e\u0434\u0435\u043b\u043e\u043a, \u0430\u00a01.2 \u0432\u043e\u043e\u0431\u0449\u0435 \u0436\u0443\u0442\u044c, \u043d\u043e….Kubernetes \u043a\u0430\u043a \u0441\u0442\u0440\u043e\u044f\u0449\u0435\u0435\u0441\u044f \u0437\u0434\u0430\u043d\u0438\u0435\u00a0\u2014 \u0441\u043c\u043e\u0442\u0440\u0438\u0448\u044c \u043d\u0430\u00a0\u043f\u0440\u043e\u0435\u043a\u0442 \u0438\u00a0\u043f\u043e\u043d\u0438\u043c\u0430\u0435\u0448\u044c, \u0447\u0442\u043e \u044d\u0442\u043e \u0431\u0443\u0434\u0435\u0442 \u043a\u0440\u0443\u0442\u043e. \u0415\u0441\u043b\u0438 \u0443\u00a0\u0437\u0434\u0430\u043d\u0438\u044f \u0441\u0435\u0439\u0447\u0430\u0441 \u0435\u0441\u0442\u044c \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442 \u0438\u00a0\u0434\u0432\u0430 \u044d\u0442\u0430\u0436\u0430, \u0442\u043e\u00a0\u043f\u043e\u043d\u0438\u043c\u0430\u0435\u0448\u044c, \u0447\u0442\u043e \u043b\u0443\u0447\u0448\u0435 \u043f\u043e\u043a\u0430 \u043d\u0435\u00a0\u0437\u0430\u0441\u0435\u043b\u044f\u0442\u044c\u0441\u044f, \u0430\u00a0\u0441\u00a0\u0441\u043e\u0444\u0442\u043e\u043c \u0442\u0430\u043a\u0438\u0445 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u043d\u0435\u0442\u00a0\u2014 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c\u0441\u044f \u0443\u0436\u0435 \u043c\u043e\u0436\u043d\u043e.<\/p>\n

Nuk kemi pasur asnj\u00eb moment q\u00eb t\u00eb mendojm\u00eb n\u00ebse do ta p\u00ebrdorim Kubernetes apo jo. Ne e prisnim at\u00eb shum\u00eb p\u00ebrpara se t\u00eb vinte, dhe p\u00ebrpiqeshim t\u00eb krijonim alternativa vet\u00eb.<\/p><\/blockquote>\n

<\/p>\n

Rreth Kubernetes<\/h2>\n

\n\u2014 A merrni pjes\u00eb drejtp\u00ebrdrejt n\u00eb zhvillimin e vet\u00eb Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: N\u00eb m\u00ebnyr\u00eb t\u00eb t\u00ebrthort\u00eb. P\u00ebr m\u00eb tep\u00ebr, ne marrim pjes\u00eb n\u00eb zhvillimin e ekosistemit. Ne d\u00ebrgojm\u00eb disa k\u00ebrkesa pull: n\u00eb Prometheus, n\u00eb operator\u00eb t\u00eb ndrysh\u00ebm, n\u00eb Helm - n\u00eb ekosistem. Fatkeq\u00ebsisht, nuk jam n\u00eb gjendje t\u00eb ndjek gjith\u00e7ka q\u00eb b\u00ebjm\u00eb dhe mund t\u00eb gaboj, por nga ne nuk ka asnj\u00eb pull n\u00eb thelb.<\/p>\n

\u2014 Nd\u00ebrkoh\u00eb, a zhvilloni shum\u00eb prej mjeteve tuaja rreth Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: Strategjia \u00ebsht\u00eb e till\u00eb: ne shkojm\u00eb dhe b\u00ebjm\u00eb pull request p\u00ebr gjith\u00e7ka q\u00eb tashm\u00eb ekziston. N\u00ebse nuk pranohet pull requests atje, ne thjesht e forkojm\u00eb p\u00ebr vete dhe jetojm\u00eb derisa ato t\u00eb pranohet me nd\u00ebrtimet tona. Pastaj, kur kjo arrin n\u00eb upstream, kthehemi n\u00eb versionin upstream.<\/p>\n

P\u00ebr shembull, kemi nj\u00eb operatore Prometheus, me t\u00eb cilin kemi kaluar n\u00eb upstream t\u00eb nd\u00ebrtimit ton\u00eb rreth 5 her\u00eb, ndoshta. Na nevojitet nj\u00eb ve\u00e7ori, d\u00ebrgojm\u00eb nj\u00eb pull request, na duhet ta l\u00ebshojm\u00eb nes\u00ebr, dhe nuk duam t\u00eb presim derisa t\u00eb l\u00ebshohet n\u00eb upstream. Prandaj, ne e grumbullojm\u00eb p\u00ebr vete, l\u00ebshojm\u00eb nd\u00ebrtimin ton\u00eb me ve\u00e7orin\u00eb ton\u00eb, e cila na nevojitet p\u00ebr di\u00e7ka. M\u00eb pas, kjo, p\u00ebr shembull, na kthehet n\u00eb upstream me fjal\u00ebt: \u201cDjem, le t\u00eb b\u00ebjm\u00eb p\u00ebr nj\u00eb rast m\u00eb t\u00eb p\u00ebrgjithsh\u00ebm\u201d, ne, ose dikush tjet\u00ebr, p\u00ebrfundojm\u00eb k\u00ebt\u00eb, dhe me kalimin e koh\u00ebs p\u00ebrs\u00ebri bllokohet.<\/p>\n

\u00c7far\u00ebdo q\u00eb ekziston, ne p\u00ebrpiqemi ta zhvillojm\u00eb.<\/b>. Shum\u00eb elemente, q\u00eb ende nuk ekzistojn\u00eb, nuk jan\u00eb menduar ende ose jan\u00eb menduar, por nuk jan\u00eb realizuar \u2014 ne i krijojm\u00eb ato. Dhe, jo sepse na p\u00eblqen vet\u00eb procesi ose nd\u00ebrtimi i bi\u00e7ikletave si industri, por thjesht sepse na nevojitet ky mjet. Shpesh shtrohet pyetja, p\u00ebrse e b\u00ebm\u00eb k\u00ebt\u00eb ose at\u00eb gj\u00eb? P\u00ebrgjigjja \u00ebsht\u00eb e thjesht\u00eb \u2014 po, sepse na duhej t\u00eb shkonim p\u00ebrpara, t\u00eb zgjidhnim nj\u00eb problem praktik, dhe ne e zgjidh\u00ebm at\u00eb me k\u00ebt\u00eb mjet.<\/p>\n

Rruga gjithmon\u00eb \u00ebsht\u00eb k\u00ebshtu: ne k\u00ebrkojm\u00eb shum\u00eb me kujdes dhe, n\u00ebse nuk gjejm\u00eb asnj\u00eb zgjidhje, si t\u00eb b\u00ebjm\u00eb nj\u00eb trolebuz nga nj\u00eb buk\u00eb, at\u00ebher\u00eb ne e b\u00ebjm\u00eb buk\u00ebn ton\u00eb dhe trolebuzin ton\u00eb.<\/p><\/blockquote>\n

<\/p>\n

Veglat 'Flanta'<\/h2>\n

\n\u2014 M\u00eb \u00ebsht\u00eb b\u00ebr\u00eb e njohur se tani \u2018Flanta\u2019 ka operator\u00eb addon, operator\u00eb shell, vegla dapp\/werf. Si\u00e7 e kuptoj, ky \u00ebsht\u00eb e nj\u00ebjta veg\u00ebl n\u00eb inkarnacione t\u00eb ndryshme. Po ashtu, e kuptoj q\u00eb brenda \u2018Flanta\u2019 ka edhe shum\u00eb vegla t\u00eb tjera t\u00eb ndryshme. K\u00ebshtu \u00ebsht\u00eb?<\/b><\/p>\n

Dmitri<\/b>: N\u00eb GitHub-in ton\u00eb kemi shum\u00eb gj\u00ebra t\u00eb tjera. Nga ato q\u00eb m\u00eb vijn\u00eb n\u00eb mendje tani, kemi statusmap - nj\u00eb panel p\u00ebr Grafana, q\u00eb e donin t\u00eb gjith\u00eb. P\u00ebrmendet pothuajse n\u00eb \u00e7do artikull t\u00eb dyt\u00eb q\u00eb flet p\u00ebr monitorimin e Kubernetes n\u00eb Medium. \u00cbsht\u00eb e pamundur t\u00eb flas\u00ebsh shkurt p\u00ebr statusmap - k\u00ebrkohet nj\u00eb artikull i ve\u00e7ant\u00eb, por \u00ebsht\u00eb nj\u00eb gj\u00eb shum\u00eb e dobishme p\u00ebr monitorimin e statusit n\u00eb koh\u00eb, pasi n\u00eb Kubernetes shpesh duhet t\u00eb tregojm\u00eb statusin n\u00eb nj\u00eb periudh\u00eb t\u00eb caktuar. Po ashtu kemi LogHouse - nj\u00eb instrument mbi baz\u00ebn e ClickHouse dhe magjis\u00eb s\u00eb zez\u00eb p\u00ebr grumbullimin e logeve n\u00eb Kubernetes.<\/p>\n

Shum\u00eb mjete! Dhe do t\u00eb ket\u00eb edhe m\u00eb shum\u00eb, sepse nj\u00eb sasi e caktuar zgjidhjesh t\u00eb brendshme do t\u00eb l\u00ebshohet k\u00ebt\u00eb vit. Nga gj\u00ebrat shum\u00eb t\u00eb m\u00ebdha mbi operatorin addon, ka nj\u00eb mori addons p\u00ebr Kubernetes si p\u00ebr shembull si t\u00eb instalosh sakt\u00ebsisht menaxherin e sertifikatave - nj\u00eb mjet p\u00ebr menaxhimin e sertifikatave, si t\u00eb vendos\u00ebsh Prometheus me shum\u00eb p\u00ebrb\u00ebr\u00ebs - jan\u00eb rreth nj\u00ebzet binar\u00eb t\u00eb ndrysh\u00ebm q\u00eb eksportojn\u00eb t\u00eb dh\u00ebna dhe mbledhin di\u00e7ka, p\u00ebr k\u00ebt\u00eb Prometheus ka grafik\u00eb t\u00eb shk\u00eblqyeshme dhe alarme. T\u00eb gjitha k\u00ebto jan\u00eb thjesht nj\u00eb mori addons p\u00ebr Kubernetes q\u00eb vendosen n\u00eb klaster dhe ai kthehet nga nj\u00eb i thjesht\u00eb n\u00eb nj\u00eb t\u00eb avancuar, automatizuar, n\u00eb t\u00eb cilin shum\u00eb \u00e7\u00ebshtje jan\u00eb zgjidhur tashm\u00eb. Po, b\u00ebjm\u00eb shum\u00eb gj\u00ebra.<\/p>\n

Zhvillimi i ekosistemit<\/h2>\n

\n\u2014 M\u00eb duket se \u00ebsht\u00eb nj\u00eb kontribut shum\u00eb i madh n\u00eb zhvillimin e k\u00ebtij instrumenti dhe metodave t\u00eb tij t\u00eb p\u00ebrdorimit. A mund t\u00eb b\u00ebsh nj\u00eb p\u00ebrllogaritje se kush tjet\u00ebr mund t\u00eb jap\u00eb nj\u00eb kontribut t\u00eb till\u00eb n\u00eb zhvillimin e ekosistemit?<\/b><\/p>\n

Dmitri<\/b>: N\u00eb Rusi, nga kompanit\u00eb q\u00eb veprojn\u00eb n\u00eb tregun ton\u00eb - askush as af\u00ebrsisht<\/b>. Sigurisht, kjo \u00ebsht\u00eb nj\u00eb deklarat\u00eb e fort\u00eb, sepse ka lojtar\u00eb t\u00eb m\u00ebdhenj si Mail me Yandex-in \u2014 ata po b\u00ebjn\u00eb di\u00e7ka me Kubernetes, por madje edhe ata nuk i afrohen kontributit t\u00eb kompanive n\u00eb t\u00ebr\u00ebsi n\u00eb bot\u00eb, t\u00eb cilat b\u00ebjn\u00eb shum\u00eb m\u00eb tep\u00ebr se ne. \u00cbsht\u00eb e v\u00ebshtir\u00eb t\u00eb krahasosh \"Flant\" me nj\u00eb ekip prej 80 njer\u00ebzish dhe Red Hat, n\u00eb t\u00eb cilin ka vet\u00ebm p\u00ebr Kubernetes 300 inxhinier\u00eb, n\u00ebse nuk gaboj. \u00cbsht\u00eb e v\u00ebshtir\u00eb t\u00eb krahasosh. Ne kemi n\u00eb departamentin RnD 6 njer\u00ebz, p\u00ebrfshir\u00eb edhe mua, q\u00eb zhvillojn\u00eb t\u00eb gjith\u00eb mjete tona. 6 njer\u00ebz kundrejt 300 inxhinier\u00ebve t\u00eb Red Hat \u2014 \u00ebsht\u00eb disi e v\u00ebshtir\u00eb t\u00eb krahasosh.<\/p>\n

\u2014 Megjithat\u00eb, kur edhe k\u00ebta 6 njer\u00ebz mund t\u00eb b\u00ebjn\u00eb di\u00e7ka v\u00ebrtet t\u00eb dobishme dhe t\u00eb transferueshme, kur ata p\u00ebrballen me nj\u00eb detyr\u00eb praktike dhe i japin zgjidhje komunitetit \u2014 \u00ebsht\u00eb nj\u00eb rast interesant. E kuptoj q\u00eb n\u00eb kompanit\u00eb e m\u00ebdha teknologjike, ku ka zhvillim t\u00eb brendsh\u00ebm dhe nj\u00eb ekip mb\u00ebshtetjeje p\u00ebr Kubernetes, n\u00eb parim mund t\u00eb zhvillohen mjete t\u00eb ngjashme. Ky \u00ebsht\u00eb nj\u00eb shembull p\u00ebr ata se \u00e7far\u00eb mund t\u00eb zhvillohet dhe t\u2019i jepet komunitetit, p\u00ebr t\u00eb dh\u00ebn\u00eb nj\u00eb impuls t\u00eb gjith\u00eb komunitetit q\u00eb p\u00ebrdor Kubernetes.<\/b><\/p>\n

Dmitri<\/b>: Ndoshta kjo \u00ebsht\u00eb nj\u00eb ve\u00e7ori e integrator\u00ebve, nj\u00eb karakteristik\u00eb e tyre. Ne kemi shum\u00eb projekte dhe shohim shum\u00eb situata t\u00eb ndryshme. P\u00ebr ne, m\u00ebnyra kryesore e krijimit t\u00eb vler\u00ebs s\u00eb shtuar \u00ebsht\u00eb t\u00eb analizojm\u00eb k\u00ebto raste, t\u00eb gjejm\u00eb p\u00ebrbashk\u00ebsit\u00eb dhe t'i reduktojm\u00eb ato sa m\u00eb shum\u00eb q\u00eb t\u00eb jet\u00eb e mundur p\u00ebr ne. Ne merremi aktivisht me k\u00ebt\u00eb. M\u00eb \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb flas p\u00ebr Rusin\u00eb dhe bot\u00ebn, por ne kemi rreth 40 inxhinier\u00eb DevOps n\u00eb kompanin\u00eb ton\u00eb q\u00eb merrem me Kubernetes. Nuk mendoj se ka shum\u00eb kompani n\u00eb Rusi me nj\u00eb num\u00ebr t\u00eb krahasuesh\u00ebm specialist\u00ebsh q\u00eb kuptojn\u00eb Kubernetes, n\u00ebse ato n\u00eb t\u00eb v\u00ebrtet\u00eb ekzistojn\u00eb.<\/p>\n

Un\u00eb e kuptoj gjith\u00e7ka n\u00eb lidhje me titullin DevOps Engineer; t\u00eb gjith\u00eb e kuptojn\u00eb dhe jan\u00eb m\u00ebsuar ta quajn\u00eb DevOps inxhinier\u00eb. Nuk do ta diskutojm\u00eb k\u00ebt\u00eb. T\u00eb gjith\u00eb k\u00ebta 40 DevOps inxhinier\u00eb t\u00eb mrekulluesh\u00ebm p\u00ebrballen \u00e7do dit\u00eb me probleme dhe i zgjidhin ato. Ne thjesht analizojm\u00eb k\u00ebt\u00eb p\u00ebrvoj\u00eb dhe p\u00ebrpiqemi ta p\u00ebrmbledhim. E dim\u00eb se n\u00ebse kjo p\u00ebrvoj\u00eb mbetet brenda nesh, pas nj\u00eb viti ose dy, ky mjet do t\u00eb jet\u00eb i padobish\u00ebm, sepse diku n\u00eb komunitet do t\u00eb shfaqet nj\u00eb mjet i gatsh\u00ebm. Nuk ka kuptim t\u00eb grumbullojm\u00eb k\u00ebt\u00eb p\u00ebrvoj\u00eb brenda \u2014 \u00ebsht\u00eb vet\u00ebm nj\u00eb humbje forca dhe kohe n\u00eb dev\/null. Ne nuk jemi aspak t\u00eb shqet\u00ebsuar. Me shum\u00eb k\u00ebnaq\u00ebsi, gjith\u00e7ka e publikojm\u00eb dhe e kuptojm\u00eb se duhet ta publikojm\u00eb, ta zhvillojm\u00eb, ta promovojm\u00eb, ta shp\u00ebrndajm\u00eb, n\u00eb m\u00ebnyr\u00eb q\u00eb njer\u00ebzit ta p\u00ebrdorin dhe t\u00eb shtojn\u00eb p\u00ebrvoj\u00ebn e tyre \u2014 at\u00ebher\u00eb gjith\u00e7ka rritet dhe \u00ebsht\u00eb e gjall\u00eb. K\u00ebshtu, pas dy vitesh, mjeti nuk shkon n\u00eb plehra. Nuk \u00ebsht\u00eb problem t\u00eb vazhdojm\u00eb t\u00eb investojm\u00eb forca, sepse \u00ebsht\u00eb e qart\u00eb se dikush po e p\u00ebrdor mjetin tuaj dhe pas dy vitesh, t\u00eb gjith\u00eb e p\u00ebrdorin at\u00eb.<\/p>\n

Kjo \u00ebsht\u00eb pjes\u00eb e strategjis\u00eb son\u00eb t\u00eb madhe me dapp\/werf.<\/b>. Nuk e mbaj mend se kur e filluam, duket si para tre vjet\u00ebsh. N\u00eb fillim ishte krejt\u00ebsisht n\u00eb shell. Ishte nj\u00eb prov\u00eb fantastike, zgjidh\u00ebm disa nga problemet tona private \u2013 doli! Por me shell ka probleme, nuk \u00ebsht\u00eb e mundur t\u00eb vazhdojm\u00eb me t\u00eb, programimi n\u00eb shell \u00ebsht\u00eb nj\u00eb gj\u00eb e komplikuar. Kishim zakon t\u00eb shkruanim n\u00eb Ruby, k\u00ebshtu q\u00eb, p\u00ebrkat\u00ebsisht, e p\u00ebrpunuam, e zhvilluam, e zhvilluam, dhe u p\u00ebrball\u00ebm me faktin se komuniteti, turma, q\u00eb nuk thot\u00eb 'ne duam ose nuk duam', e kthen fytyr\u00ebn nga Ruby, sa p\u00ebr t\u00eb qeshur. Kuptuam se duhej ta shkruanim k\u00ebt\u00eb n\u00eb Go, p\u00ebr t\u00eb p\u00ebrmbushur pik\u00ebn e par\u00eb n\u00eb list\u00ebn kontrolluese: Mjeti DevOps duhet t\u00eb jet\u00eb nj\u00eb binar statik<\/b>. N\u00eb Go ose jo n\u00eb Go nuk ka r\u00ebnd\u00ebsi aq shum\u00eb, por \u00ebsht\u00eb m\u00eb mir\u00eb nj\u00eb binar statik i shkruar n\u00eb Go.<\/p>\n

Harxhuam forc\u00eb, e rip\u00ebrpunuam dapp n\u00eb Go dhe e quajt\u00ebm werf. Dapp nuk mb\u00ebshtetet m\u00eb, nuk zhvillohet, funksionon n\u00eb ndonj\u00eb version t\u00eb fundit, por ekziston nj\u00eb rrug\u00eb absolute p\u00ebr p\u00ebrmir\u00ebsim, dhe mund t\u00eb ndiqet.<\/p>\n

Pse u krijua dapp<\/h2>\n

\n\u2014 A mund t\u00eb tregosh shkurtimisht p\u00ebrse u krijua dapp, \u00e7far\u00eb probleme zgjidh?<\/b><\/p>\n

Dmitri<\/b>: Arsyeja e par\u00eb \u00ebsht\u00eb n\u00eb nd\u00ebrtim. Fillimisht, kishim probleme t\u00eb m\u00ebdha me nd\u00ebrtimin, kur Docker nuk dinte t\u00eb b\u00ebj\u00eb multi-stage, dhe ne e b\u00ebm\u00eb multi-stage me fuqit\u00eb tona. M\u00eb pas pat\u00ebm nj\u00eb mori pyetjesh lidhur me pastrimin e images. T\u00eb gjith\u00eb ata q\u00eb b\u00ebjn\u00eb CI\/CD, m\u00eb shpejt se von\u00eb, p\u00ebrballen me problemin se ka shum\u00eb images t\u00eb nd\u00ebrtuara, dhe duhet t\u00eb pastrojn\u00eb ato q\u00eb nuk duhen dhe t\u00eb l\u00ebn\u00eb ato q\u00eb duhen.<\/p>\n

Arsyeja e dyt\u00eb \u00ebsht\u00eb n\u00eb depol. Po, ka Helm, por ai zgjidh vet\u00ebm nj\u00eb pjes\u00eb t\u00eb detyrave. Si\u00e7 \u00ebsht\u00eb e \u00e7uditshme, \u00ebsht\u00eb shkruar se 'Helm \u00ebsht\u00eb Menaxheri i Paketave p\u00ebr Kubernetes'. N\u00eb t\u00eb v\u00ebrtet\u00eb, 'Menaxheri i Paketave' \u2014 \u00e7far\u00eb pritet zakonisht nga Menaxheri i Paketave? Ne themi: 'Menaxheri i Paketave, vendos paket\u00ebn!' dhe presim q\u00eb ai t\u00eb na thot\u00eb: 'Paketa u vendos'. <\/p>\n

\u00cbsht\u00eb interesante se ne themi: 'Helm, vendos paket\u00ebn', dhe kur ai p\u00ebrgjigjet se e ka vendosur, zbulojm\u00eb se ai vet\u00ebm ka filluar instalimin \u2014 i tha Kubernetes: 'Starto k\u00ebt\u00eb gj\u00eb!', por n\u00ebse ajo u startua apo jo, n\u00ebse punon apo jo, Helm nuk e zgjidh k\u00ebt\u00eb pyetje fare.<\/p>\n

Prandaj, Helm \u00ebsht\u00eb thjesht nj\u00eb preprocessori tekstual q\u00eb ngarkon t\u00eb dh\u00ebna n\u00eb Kubernetes.<\/p><\/blockquote>\n

\nPor, ne do t\u00eb duam ta dim\u00eb \u2014 a e realizuam aplikacionin n\u00eb prodhim apo jo? T\u00eb ket\u00eb kaluar n\u00eb prodhim do t\u00eb thot\u00eb q\u00eb aplikacioni u publikua, nj\u00eb version i ri u aktivizua, dhe ai t\u00eb pakt\u00ebn nuk bie dhe p\u00ebrgjigjet sakt\u00eb. Helm nuk e zgjidh k\u00ebt\u00eb problem. P\u00ebr ta zgjidhur at\u00eb, duhen investuar shum\u00eb p\u00ebrpjekje, sepse \u00ebsht\u00eb e nevojshme t\u00eb jepni komand\u00ebn Kubernetes p\u00ebr t\u00eb publikuar dhe t\u00eb monitoroni se \u00e7far\u00eb po ndodh atje \u2014 a \u00ebsht\u00eb aktivizuar, a \u00ebsht\u00eb rregulluar. Dhe ka gjithashtu shum\u00eb detyra t\u00eb lidhura me publikimin, pastrimin, dhe nd\u00ebrtimin.<\/p>\n

Planet<\/h2>\n

\nEdhe k\u00ebt\u00eb vit ne do t\u00eb fillojm\u00eb zhvillimin lokal. Ne duam t\u00eb arrijm\u00eb at\u00eb q\u00eb dikur kishte n\u00eb Vagrant \u2014 t\u00eb shkruajm\u00eb 'vagrant up' dhe t\u00eb na aktivizoheshin makinash virtuale. Ne duam t\u00eb arrijm\u00eb n\u00eb nj\u00eb gjendje ku ka nj\u00eb projekt n\u00eb Git, ne aty shkruajm\u00eb 'werf up', dhe ai ngre nj\u00eb kopje lokale t\u00eb k\u00ebtij projekti, e cila \u00ebsht\u00eb e instaluar n\u00eb nj\u00eb mini-Kub lokal, me t\u00eb gjitha dosjet e lidhura, t\u00eb p\u00ebrshtatshme p\u00ebr zhvillim. N\u00eb var\u00ebsi t\u00eb gjuh\u00ebs s\u00eb zhvillimit, kjo kryhet ndryshe, megjithat\u00eb, q\u00eb t\u00eb mund t\u00eb zhvillohet leht\u00ebsisht me skedar\u00eb t\u00eb montuar.<\/p>\n

Hapi yn\u00eb i ardhsh\u00ebm \u00ebsht\u00eb t\u00eb forcojm\u00eb investimi n\u00eb komoditet p\u00ebr zhvilluesit<\/b>. P\u00ebr t\u00eb vendosur shpejt nj\u00eb projekt lokalisht me nj\u00eb mjet, p\u00ebr ta zhvilluar, p\u00ebr ta d\u00ebrguar n\u00eb Git, dhe ai t\u00eb del po ashtu n\u00eb sken\u00eb ose n\u00eb teste, n\u00eb var\u00ebsi t\u00eb pipeline-ve, dhe pastaj me t\u00eb nj\u00ebjtin mjet t\u00eb shkojm\u00eb n\u00eb prodhim. Ky unitet, unifikimi, riprodhueshm\u00ebria e infrastruktur\u00ebs nga mjedisi lokal deri n\u00eb prodhim \u00ebsht\u00eb nj\u00eb moment shum\u00eb i r\u00ebnd\u00ebsish\u00ebm p\u00ebr ne. Por kjo ende nuk \u00ebsht\u00eb n\u00eb werf - vet\u00ebm po e planifikojm\u00eb.<\/p>\n

Por rruga drejt dapp\/werf gjithmon\u00eb ka qen\u00eb e nj\u00ebjt\u00eb si me Kubernetes n\u00eb fillim. Ne kemi p\u00ebrballur me probleme, i zgjidhim ato n\u00eb m\u00ebnyra alternative - shpikim disa zgjidhje me shell, me \u00e7far\u00ebdo p\u00ebrmbajtjeje. Pastaj, k\u00ebto rrug\u00eb alternative p\u00ebrpiqemi t'i shesim, t'i p\u00ebrgjithsojm\u00eb dhe t'i konsolidojm\u00eb n\u00eb binar\u00eb, me t\u00eb cilat vet\u00ebm ndajm\u00eb.<\/p>\n

Ka nj\u00eb tjet\u00ebr k\u00ebndv\u00ebshtrim p\u00ebr gjith\u00eb k\u00ebt\u00eb histori, me analogji. <\/p>\n

Kubernetes \u00ebsht\u00eb nj\u00eb struktur\u00eb automobili me motor. Nuk ka dyer, xhama, radio, aromatizues - p\u00ebr at\u00eb, nuk ka asgj\u00eb. Vet\u00ebm korniz\u00eb dhe motor. Dhe ka Helm - ky \u00ebsht\u00eb timoni. \u00cbsht\u00eb super - kemi timonin, por na nevojiten gjithashtu stafet\u00eb e timonit, sistemi i drejtimit, kutia e ngjitjes dhe rrotat, sepse pa to nuk shkon.<\/p><\/blockquote>\n

\nN\u00eb rastin me werf, ky \u00ebsht\u00eb nj\u00eb komponent tjet\u00ebr p\u00ebr Kubernetes. Tani, ne kemi nj\u00eb version alfa t\u00eb werf, p\u00ebr shembull, Helm \u00ebsht\u00eb inkorporuar ngusht\u00eb brenda werf, sepse na u lodh t\u00eb b\u00ebjm\u00eb k\u00ebt\u00eb vet\u00eb. Ka shum\u00eb arsye p\u00ebr k\u00ebt\u00eb, dhe do t\u00eb flas p\u00ebr arsyet pse ne inkorporuam plot\u00ebsisht Helm bashk\u00eb me Tiller brenda werf. n\u00eb prezantimin n\u00eb RIT++<\/a><\/noindex>.<\/p>\n

Tani, werf \u00ebsht\u00eb nj\u00eb komponent m\u00eb i integruar. Ne kemi nj\u00eb timon t\u00eb gatsh\u00ebm, nj\u00eb pin timoni - nuk e kuptoj shum\u00eb n\u00eb makina, por ky \u00ebsht\u00eb nj\u00eb bllok i madh q\u00eb zgjidh nj\u00eb gam\u00eb t\u00eb gjer\u00eb problemesh. Nuk \u00ebsht\u00eb e nevojshme t\u00eb k\u00ebrkojm\u00eb p\u00ebr pjes\u00eb t\u00eb ndryshme dhe t\u00eb mendojm\u00eb se si t'i bashkojm\u00eb ato. Ne marrim nj\u00eb kombajn t\u00eb gatsh\u00ebm, i cili zgjidh nj\u00eb grup t\u00eb madh problemesh menj\u00ebher\u00eb. Por brenda, ajo \u00ebsht\u00eb nd\u00ebrtuar nga t\u00eb nj\u00ebjtat komponent\u00eb open source, gjithashtu p\u00ebrdor Docker p\u00ebr nd\u00ebrtim, Helm p\u00ebr nj\u00eb pjes\u00eb t\u00eb funksionalitetit, dhe ka disa biblioteka tjera. Ky \u00ebsht\u00eb nj\u00eb mjet i integruar p\u00ebr t\u00eb marr\u00eb nj\u00eb CI\/CD t\u00eb shk\u00eblqyer me shpejt\u00ebsi dhe leht\u00ebsi nga kutia.<\/p>\n

A \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb mbash Kubernetes?<\/h2>\n

\n\u2014\u00a0Ti\u00a0flas p\u00ebr p\u00ebrvoj\u00ebn t\u00ebnde, se si e fillove t\u00eb p\u00ebrdor\u00ebsh Kubernetes, q\u00eb p\u00ebr ju \u00ebsht\u00eb nj\u00eb korniz\u00eb, motor, dhe se mbi t\u00eb mund t\u00eb vendos\u00ebsh shum\u00eb gj\u00ebra t\u00eb ndryshme: karoseri, timon, t\u00eb ngjitesh pedalet, sedilet. Ngrihet pyetja \u2014 sa e v\u00ebshtir\u00eb \u00ebsht\u00eb p\u00ebr ju t\u00eb mbani Kubernetes? Keni nj\u00eb p\u00ebrvoj\u00eb t\u00eb pasur, sa koh\u00eb dhe burime ju nevojiten specifikisht p\u00ebr t\u00eb mbajtur Kubernetes, n\u00eb ve\u00e7anti nga e gjith\u00eb e tjera?<\/b><\/p>\n

Dmitri<\/b>: Kjo \u00ebsht\u00eb nj\u00eb pyetje shum\u00eb e komplikuar dhe p\u00ebr t\u00eb p\u00ebrgjigjur, duhet t\u00eb kuptom\u00eb se \u00e7far\u00eb do t\u00eb thot\u00eb mb\u00ebshtetje dhe \u00e7far\u00eb d\u00ebshirojm\u00eb nga Kubernetes. Ndoshta do t\u00eb ndash disa m\u00eb shum\u00eb?<\/p>\n

\u2014\u00a0Sa kam informacion dhe si e shoh, tani shum\u00eb ekipe duan t\u00eb provojn\u00eb Kubernetes. T\u00eb gjith\u00eb po e qasin, e vendosin n\u00eb gjunj\u00eb. Kam ndjesin\u00eb se njer\u00ebzit nuk e kuptojn\u00eb gjithmon\u00eb kompleksitetin e k\u00ebtij sistemi.<\/b><\/p>\n

Dmitri<\/b>: Ashtu \u00ebsht\u00eb.<\/p>\n

\u2014\u00a0Sa e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb marr\u00ebsh dhe t\u00eb vendos\u00ebsh Kubernetes nga e para, q\u00eb t\u00eb jet\u00eb gati p\u00ebr prodhim?<\/b><\/p>\n

Dmitri<\/b>: Si mendon, sa e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb transplantosh nj\u00eb zem\u00ebr? E kuptoj, kjo \u00ebsht\u00eb nj\u00eb pyetje e ngjashme. T\u00eb p\u00ebrdor\u00ebsh nj\u00eb skalpel dhe t\u00eb mos gabosh \u2014 nuk \u00ebsht\u00eb aq e v\u00ebshtir\u00eb. N\u00ebse t\u00eb thon\u00eb se ku t\u00eb prenosh, dhe ku t\u00eb mbyll\u00ebsh, at\u00ebher\u00eb procedura vet\u00eb nuk \u00ebsht\u00eb e komplikuar. E v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb garantosh \u00e7do her\u00eb se gjith\u00e7ka do t\u00eb dal\u00eb si\u00e7 duhet.<\/p>\n

Instalimi i Kubernetes dhe b\u00ebrja q\u00eb t\u00eb funksionoj\u00eb \u00ebsht\u00eb e thjesht\u00eb: hop! \u2014 u instalua, ka shum\u00eb m\u00ebnyra p\u00ebr ta b\u00ebr\u00eb k\u00ebt\u00eb. Por \u00e7far\u00eb do t\u00eb ndodh\u00eb kur t\u00eb shfaqen problemet?<\/p><\/blockquote>\n

\nGjithmon\u00eb lindin pyetje \u2014 \u00e7far\u00eb nuk kemi marr\u00eb parasysh? \u00c7far\u00eb nuk kemi b\u00ebr\u00eb? Cil\u00ebt parametra t\u00eb b\u00ebrtham\u00ebs Linux i kemi th\u00ebn\u00eb gabim? O Zot, a i kemi th\u00ebn\u00eb t\u00eb gjith\u00eb?! Cil\u00ebt komponent\u00eb t\u00eb Kubernetes e kemi instaluar, dhe cil\u00ebt jo? Shfaqen mij\u00ebra pyetje dhe p\u00ebr t\u00eb p\u00ebrgjigjur n\u00eb to, duhet t\u00eb kesh 15-20 vjet p\u00ebrvoj\u00eb n\u00eb k\u00ebt\u00eb industri.<\/p>\n

Kam nj\u00eb shembull t\u00eb fresk\u00ebt n\u00eb k\u00ebt\u00eb drejtim q\u00eb mund t\u00eb zbuloj\u00eb kuptimin e problemit \"A \u00ebsht\u00eb e v\u00ebshtir\u00eb mbajtja e Kubernetes?\" Nj\u00eb koh\u00eb m\u00eb par\u00eb ne po e shqyrtonim seriozisht n\u00ebse duhet t\u00eb provonim t\u00eb implementonim Cilium si rrjet n\u00eb Kubernetes.<\/p>\n

Le t\u00eb sqaroj se \u00e7far\u00eb \u00ebsht\u00eb Cilium. N\u00eb Kubernetes ka shum\u00eb realizime t\u00eb ndryshme t\u00eb sistemit t\u00eb rrjetit, dhe nj\u00ebra prej tyre \u00ebsht\u00eb shum\u00eb e bukur \u2014 kjo \u00ebsht\u00eb Cilium. \u00c7far\u00eb e b\u00ebn at\u00eb interesante? N\u00eb b\u00ebrtham\u00ebn Linux, nj\u00eb koh\u00eb m\u00eb par\u00eb u shfaq mund\u00ebsia p\u00ebr t\u00eb shkruar hooks p\u00ebr b\u00ebrtham\u00ebn, t\u00eb cilat ndonj\u00ebher\u00eb nd\u00ebrhyjn\u00eb n\u00eb sistemin e rrjetit dhe n\u00eb shum\u00eb sisteme t\u00eb tjera, duke lejuar t\u00eb kalohen pjes\u00eb t\u00eb m\u00ebdha t\u00eb b\u00ebrtham\u00ebs.<\/p>\n

N\u00eb b\u00ebrtham\u00ebn Linux historikisht ka ip rout, netfilter, bridge dhe shum\u00eb komponente t\u00eb tjera t\u00eb vjetra, q\u00eb jan\u00eb 15, 20, 30 vje\u00e7are. N\u00eb p\u00ebrgjith\u00ebsi ato funksionojn\u00eb, gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull, por tani kemi mbushur me kontejner\u00eb, dhe duket si nj\u00eb kumbare prej 15 tullash nj\u00eb mbi tjetr\u00ebn, dhe ti je duke q\u00ebndruar mbi t\u00eb me nj\u00eb k\u00ebmb\u00eb \u2013 nj\u00eb ndjenj\u00eb e \u00e7uditshme. Ky sistem \u00ebsht\u00eb zhvilluar historikisht me shum\u00eb nuanca, si nj\u00eb apendiks n\u00eb trup. N\u00eb disa situata ka probleme me performanc\u00ebn, p\u00ebr shembull.<\/p>\n

Ka nj\u00eb BPF t\u00eb shk\u00eblqyer dhe mund\u00ebsin\u00eb p\u00ebr t\u00eb shkruar hook p\u00ebr b\u00ebrtham\u00ebn \u2013 djemt\u00eb shkruan hook e tyre p\u00ebr b\u00ebrtham\u00ebn. Paketa vjen n\u00eb b\u00ebrtham\u00ebn Linux, ata e nxjerrin at\u00eb direkt n\u00eb hyrje, e p\u00ebrpunojn\u00eb si\u00e7 duhet pa bridge, pa TCP, pa IP stack \u2013 me fjal\u00eb t\u00eb tjera, duke anashkaluar gjith\u00e7ka q\u00eb \u00ebsht\u00eb shkruar n\u00eb b\u00ebrtham\u00ebn Linux, dhe menj\u00ebher\u00eb e p\u00ebrplas\u00ebn n\u00eb kontejner.<\/p>\n

\u00c7far\u00eb ndodhi? Nj\u00eb performanc\u00eb shum\u00eb e shk\u00eblqyer, ve\u00e7ori t\u00eb shk\u00eblqyera \u2013 thjesht fantastike! Por ne e shohim k\u00ebt\u00eb dhe shohim se n\u00eb \u00e7do makin\u00eb \u00ebsht\u00eb instaluar nj\u00eb program q\u00eb lidhet me API-n\u00eb e Kubernetes dhe, n\u00eb baz\u00eb t\u00eb t\u00eb dh\u00ebnave q\u00eb merr nga ky API, gjeneron kodin C dhe kompilon binar\u00ebt, t\u00eb cil\u00ebt ngarkohen n\u00eb b\u00ebrtham\u00eb, q\u00eb n\u00eb hap\u00ebsir\u00ebn e b\u00ebrtham\u00ebs k\u00ebto hook t\u00eb funksionojn\u00eb.<\/p>\n

\u00c7far\u00eb do t\u00eb ndodh\u00eb n\u00ebse di\u00e7ka shkon keq? Ne nuk e dim\u00eb. P\u00ebr ta kuptuar k\u00ebt\u00eb, duhet t\u00eb lexoni t\u00eb gjith\u00eb k\u00ebt\u00eb kod, t\u00eb kuptoni gjith\u00eb logjik\u00ebn, dhe kjo \u00ebsht\u00eb e komplikuar. Por, nga ana tjet\u00ebr, ka k\u00ebto bidge, filtre net-i, IP rout - nuk kam lexuar kodet e tyre, dhe as 40 inxhinier\u00ebt q\u00eb punojn\u00eb n\u00eb kompanin\u00eb ton\u00eb. Ndoshta disa pjes\u00eb kuptohen nga disa individ\u00eb.<\/p>\n

Dhe \u00e7far\u00eb r\u00ebnd\u00ebsie ka? Duket se ka IP rout, b\u00ebrtham\u00ebn Linux, dhe ka nj\u00eb mjet t\u00eb ri - \u00e7far\u00eb r\u00ebnd\u00ebsie ka, asnj\u00ebra nga ato nuk e kuptojm\u00eb. Por kemi frik\u00eb t\u00eb p\u00ebrdorim t\u00eb reja - pse? Sepse n\u00ebse nj\u00eb mjet \u00ebsht\u00eb 30 vje\u00e7are, at\u00ebher\u00eb gjat\u00eb 30 viteve t\u00eb kaluara t\u00eb gjitha gabimet jan\u00eb gjetur, jan\u00eb hasur n\u00eb t\u00eb gjitha rreziqet dhe p\u00ebr t\u00eb ditur p\u00ebr t\u00eb gjitha nuk \u00ebsht\u00eb e nevojshme - punon si nj\u00eb kuti e zez\u00eb, dhe gjithmon\u00eb punon. T\u00eb gjith\u00eb e din\u00eb se ku t\u00eb fusin nj\u00eb screwdriver diagnostikues dhe cili tcpdump t\u00eb nisin n\u00eb \u00e7astin e duhur. T\u00eb gjith\u00eb e din\u00eb mir\u00eb mjetet diagnostikuese dhe kuptojn\u00eb si funksionon ky set komponentesh n\u00eb b\u00ebrtham\u00ebn Linux - jo si \u00ebsht\u00eb nd\u00ebrtuar, por si ta p\u00ebrdorin at\u00eb.<\/p>\n

Por Cilium, i cili nuk ka 30 vjet, akoma nuk \u00ebsht\u00eb i pjekur. Poashtu ka t\u00eb nj\u00ebjtin problem me Kubernetes; \u00ebsht\u00eb nj\u00eb kopje. T\u00eb dyja instalohen shk\u00eblqyesh\u00ebm, por, kur di\u00e7ka shkon keq n\u00eb prodhim, a jeni t\u00eb aft\u00eb t\u00eb kuptoni shpejt, se \u00e7far\u00eb ka shkuar keq n\u00eb nj\u00eb situat\u00eb kritike? <\/p>\n

Kur flasim n\u00ebse \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb mbash Kubernetes \u2014 jo, \u00ebsht\u00eb shum\u00eb e leht\u00eb, dhe po, \u00ebsht\u00eb jasht\u00ebzakonisht e v\u00ebshtir\u00eb. Kubernetes funksionon shk\u00eblqyer vet\u00ebm, por me nj\u00eb miliard nuancash.<\/p><\/blockquote>\n

<\/p>\n

P\u00ebr qasjen \"M\u00eb ndihmoj fatit\"<\/h2>\n

\n\u2014 A ka kompani ku k\u00ebto nuanca do t\u00eb shfaqen pothuajse me siguri? Supozoni se Yandex do t\u00eb kaloj\u00eb t\u00eb gjitha sh\u00ebrbimet n\u00eb Kubernetes, do t\u00eb ket\u00eb nj\u00eb ngarkes\u00eb t\u00eb madhe.<\/b><\/p>\n

Dmitri<\/b>: Jo, nuk \u00ebsht\u00eb bised\u00eb p\u00ebr ngarkes\u00ebn, por p\u00ebr gj\u00ebrat m\u00eb t\u00eb thjeshta. P\u00ebr shembull, kemi Kubernetes, e kemi vendosur nj\u00eb aplikacion atje. Si ta kuptojm\u00eb se ai funksionon? Nuk ka mjete t\u00eb gatshme p\u00ebr t\u00eb kuptuar se a po shembet aplikacioni, thjesht nuk egziston. Nuk ka nj\u00eb sistem t\u00eb gatsh\u00ebm q\u00eb d\u00ebrgon alarme \u2014 duhet ta konfiguroni k\u00ebt\u00eb alarm dhe \u00e7do grafik. E ne po e p\u00ebrdit\u00ebsojm\u00eb Kubernetes.<\/p>\n

Ka Ubuntu 16.04. Mund\u00ebsia \u00ebsht\u00eb se kjo \u00ebsht\u00eb nj\u00eb version i vjet\u00ebr, por ne akoma e p\u00ebrdorim sepse aty kemi LTS. Aty ka systemd, me nuanc\u00ebn se ai nuk pastron grupet C. Kubernetes ekzekuton pods, krijon grupe C, pastaj i fshin pods, dhe ndodhin disa gj\u00ebra k\u00ebshtu - nuk e mbaj mend detajet, m\u00eb vjen keq - q\u00eb mbeten sslice nga systemd. Kjo \u00e7on n\u00eb at\u00eb q\u00eb me kalimin e koh\u00ebs \u00e7do makin\u00eb fillon t\u00eb ngadal\u00ebsohet ndjesh\u00ebm. Kjo nuk \u00ebsht\u00eb vet\u00ebm p\u00ebr highload. N\u00ebse fillojn\u00eb t\u00eb ekzekutohen pods t\u00eb p\u00ebrhersh\u00ebm, p\u00ebr shembull, n\u00ebse ka nj\u00eb Cron Job q\u00eb vazhdimisht gjeneron pods, at\u00ebher\u00eb makina me Ubuntu 16.04 pas nj\u00eb jave do t\u00eb filloj\u00eb t\u00eb ngadal\u00ebsohet. Aty do t\u00eb ket\u00eb nj\u00eb load average t\u00eb lart\u00eb p\u00ebr shkak se jan\u00eb krijuar shum\u00eb grupe C. Kjo \u00ebsht\u00eb nj\u00eb problem me t\u00eb cilin p\u00ebrballet \u00e7do person q\u00eb thjesht instalon Ubuntu 16 dhe e instalon Kubernetes mbi t\u00eb.<\/p>\n

Supozoni se se ndonj\u00eb m\u00ebnyr\u00eb e p\u00ebrdit\u00ebson systemd ose di\u00e7ka tjet\u00ebr, por n\u00eb b\u00ebrtham\u00ebn Linux deri n\u00eb 4.16 \u00ebsht\u00eb akoma m\u00eb e \u00e7uditshme \u2013 kur flitet p\u00ebr heqjen e C-grupeve, ato n\u00eb b\u00ebrtham\u00eb vazhdojn\u00eb t\u00eb dep\u00ebrtojn\u00eb dhe faktikisht nuk eliminohen. Prandaj, pas nj\u00eb muaji pun\u00eb n\u00eb k\u00ebt\u00eb makin\u00eb, do t\u00eb jet\u00eb e pamundur t\u00eb shikosh statistik\u00ebn e kujtes\u00ebs p\u00ebr podet. Ne nxjerrim nj\u00eb sked\u00eb, e rrotullojm\u00eb n\u00eb program, dhe nj\u00eb sked\u00eb e till\u00eb rrotullohet p\u00ebr 15 sekonda, sepse b\u00ebrthama llogarit brenda vetes miliona C-grupeve, q\u00eb si\u00e7 duket jan\u00eb hequr, por jo \u2013 ato vazhdojn\u00eb t\u00eb dep\u00ebrtojn\u00eb.<\/p>\n

Ka shum\u00eb detaje t\u00eb tilla ende shum\u00eb n\u00eb k\u00ebtu e atje. Kjo nuk \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje me t\u00eb cil\u00ebn kompanit\u00eb gjigante ndonj\u00ebher\u00eb mund t\u00eb p\u00ebrballen n\u00ebn ngarkesa shum\u00eb t\u00eb m\u00ebdha - jo, kjo \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje e p\u00ebrditshme. Njer\u00ebzit mund t\u00eb jetojn\u00eb k\u00ebshtu p\u00ebr muaj t\u00eb t\u00ebr\u00eb - vendos\u00ebn Kubernetes, e vendos\u00ebn aplikimin - duket se punon. P\u00ebr shum\u00eb \u00ebsht\u00eb n\u00eb rregull. Rreth asaj se kur nj\u00ebher\u00eb ky aplikim ndonj\u00ebher\u00eb do t\u00eb bjer\u00eb, ata as nuk do t\u00eb kuptojn\u00eb, alarmin nuk do t\u00eb vij\u00eb, por p\u00ebr ta kjo \u00ebsht\u00eb norma. M\u00eb par\u00eb jetonin n\u00eb virtualizime pa mbik\u00ebqyrje, tani jan\u00eb shp\u00ebrngulur n\u00eb Kubernetes gjithashtu pa mbik\u00ebqyrje - \u00e7far\u00eb ndryshimi ka?<\/p>\n

Problemi \u00ebsht\u00eb se kur ecim mbi akull, kurr\u00eb nuk e dim\u00eb trash\u00ebsin\u00eb e tij n\u00ebse nuk e kemi matur paraprakisht. Shum\u00eb ecn\u00eb dhe nuk shqet\u00ebsohen, sepse kan\u00eb ecur edhe m\u00eb par\u00eb.<\/p>\n

Nga k\u00ebndv\u00ebshtrimi im, nuanca dhe kompleksiteti i funksionimit t\u00eb \u00e7do sistemi \u00ebsht\u00eb q\u00eb t\u00eb garantohet se trash\u00ebsia e akullit \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb e mjaftueshme p\u00ebr t\u00eb p\u00ebrmbushur detyrat tona. \u00cbsht\u00eb fjala p\u00ebr k\u00ebt\u00eb.<\/p><\/blockquote>\n

\nN\u00eb IT, m\u00eb duket se ka shum\u00eb qasje \u2018M\u00eb ka ndodhur\u2019. Shum\u00eb instalojn\u00eb software, p\u00ebrdorin biblioteka programimi me shpres\u00ebn se do t\u2019u ndodh\u00eb. N\u00eb p\u00ebrgjith\u00ebsi, shum\u00eb kan\u00eb fat. Ndoshta p\u00ebr k\u00ebt\u00eb funksionon.<\/p>\n

\u2014 Nga vler\u00ebsimi im pesimist, kjo duket k\u00ebshtu: kur rreziqet jan\u00eb t\u00eb m\u00ebdha, dhe aplikacioni duhet t\u00eb funksionoj\u00eb, at\u00ebher\u00eb \u00ebsht\u00eb e nevojshme mb\u00ebshtetje nga \u2018Flant\u2019 ose, ndoshta, nga Red Hat, ose k\u00ebrkohet nj\u00eb ekip i brendsh\u00ebm i dedikuar drejtp\u00ebrdrejt p\u00ebr Kubernetes, i cili \u00ebsht\u00eb i gatsh\u00ebm ta mbaj\u00eb at\u00eb.<\/b><\/p>\n

Dmitri<\/b>: Objekti \u00ebsht\u00eb k\u00ebshtu. T\u00eb hysh vet\u00eb n\u00eb historin\u00eb me Kubernetes me nj\u00eb ekip t\u00eb vog\u00ebl p\u00ebrb\u00ebn disa rreziqe.<\/p>\n

Na nevojiten konteiner\u00ebt?<\/h2>\n

\n\u2014 Mund t\u00eb flas\u00ebsh p\u00ebr sa t\u00eb p\u00ebrhapur \u00ebsht\u00eb Kubernetes n\u00eb Rusi?<\/b><\/p>\n

Dmitri<\/b>: Nuk kam k\u00ebto t\u00eb dh\u00ebna, dhe nuk jam i sigurt se a i kan\u00eb v\u00ebrtet askush. Ne po flasim: \u201cKubernetes, Kubernetes\u201d, por ka nj\u00eb k\u00ebndv\u00ebshtrim tjet\u00ebr mbi k\u00ebt\u00eb \u00e7\u00ebshtje. Sa t\u00eb zakonsh\u00ebm jan\u00eb kontejner\u00ebt, gjithashtu nuk e di, por e di nj\u00eb num\u00ebr nga raporte n\u00eb internet, q\u00eb 70% e kontejner\u00ebve orkestrohen nga Kubernetes. Ky ishte nj\u00eb burim i besuesh\u00ebm p\u00ebr nj\u00eb most\u00ebr mjaft t\u00eb madhe n\u00eb t\u00eb gjith\u00eb bot\u00ebn.<\/p>\n

M\u00eb pas, pyetja tjet\u00ebr \u00ebsht\u00eb - a na nevojiten kontejner\u00ebt?<\/b> Kam nj\u00eb ndjenj\u00eb personale dhe n\u00eb p\u00ebrgjith\u00ebsi pozita e kompanis\u00eb 'Flant' \u00ebsht\u00eb se Kubernetes \u00ebsht\u00eb standardi de facto.<\/p>\n

Nuk do t\u00eb ket\u00eb asgj\u00eb tjet\u00ebr p\u00ebrve\u00e7 Kubernetes.<\/p><\/blockquote>\n

\nKy \u00ebsht\u00eb nj\u00eb game-changer absolut n\u00eb menaxhimin e infrastruktur\u00ebs. Thjesht absolut - gjith\u00eb, asnj\u00eb Ansible, Chef, makinat virtuale, Terraform. Nuk po flas p\u00ebr metodat e vjetra kombinate. Kubernetes \u00ebsht\u00eb nj\u00eb changer absolut<\/b>, dhe tani do t\u00eb jet\u00eb vet\u00ebm k\u00ebshtu.<\/p>\n

E qart\u00eb \u00ebsht\u00eb se disa kan\u00eb nevoj\u00eb p\u00ebr disa vite, ndonj\u00ebher\u00eb disa dhjet\u00ebra, p\u00ebr ta kuptuar k\u00ebt\u00eb. Nuk kam dyshim se nuk do t\u00eb ket\u00eb asgj\u00eb tjet\u00ebr p\u00ebrve\u00e7 Kubernetes dhe k\u00ebtij k\u00ebndv\u00ebshtrimi t\u00eb ri: m\u00eb nuk e d\u00ebmtojm\u00eb operacionin, por p\u00ebrdorim infrastructure as code<\/b>, vet\u00ebm q\u00eb jo me kod, por me yml - infrastruktur\u00eb t\u00eb p\u00ebrshkruar n\u00eb m\u00ebnyr\u00eb deklarative. Kam ndjesin\u00eb se k\u00ebshtu do t\u00eb jet\u00eb gjithmon\u00eb.<\/p>\n

\u2014 Kjo do t\u00eb thot\u00eb, se kompanit\u00eb q\u00eb ende nuk jan\u00eb kaluar n\u00eb Kubernetes, patjet\u00ebr do t\u00eb kalojn\u00eb ose do t\u00eb mbeten n\u00eb harres\u00eb. A e kuptova mir\u00eb?<\/b><\/p>\n

Dmitri<\/b>: Kjo nuk \u00ebsht\u00eb gjithashtu krejt\u00ebsisht e sakt\u00eb. P\u00ebr shembull, n\u00ebse kemi p\u00ebr q\u00ebllim t\u00eb nisim nj\u00eb server dns, mund ta nisim n\u00eb FreeBSD 4.10 dhe ai mund t\u00eb funksionoj\u00eb shk\u00eblqyer p\u00ebr 20 vjet. Thjesht t\u00eb funksionoj\u00eb dhe kaq. Ndoshta p\u00ebr 20 vjet do t\u00eb nevojitet t\u00eb azhurnohet di\u00e7ka nj\u00eb her\u00eb. N\u00ebse flasim p\u00ebr softin n\u00eb formatin q\u00eb e kemi nisur dhe ai realisht funksionon shum\u00eb vite pa azhurnime ose ndryshime, at\u00ebher\u00eb sigurisht atje nuk do t\u00eb ket\u00eb Kubernetes. Ai nuk \u00ebsht\u00eb i nevojsh\u00ebm atje.<\/p>\n

Kushdo q\u00eb lidhet me CI\/CD \u2014 kudo ku nevojitet Continuous Delivery, ku k\u00ebrkohet p\u00ebr t\u00eb azhurnuar versione, p\u00ebr t\u00eb b\u00ebr\u00eb ndryshime aktive, kudo ku \u00ebsht\u00eb e domosdoshme t\u00eb krijohet q\u00ebndrueshm\u00ebria ndaj d\u00ebshtimit \u2014 vet\u00ebm Kubernetes.<\/p><\/blockquote>\n

<\/p>\n

P\u00ebr mikrosh\u00ebrbimet<\/h2>\n

\n\u2014 K\u00ebtu kam nj\u00eb disonanc\u00eb t\u00eb vog\u00ebl. P\u00ebr t\u00eb punuar me Kubernetes, nevojitet mb\u00ebshtetje e jashtme ose e brendshme \u2014 ky \u00ebsht\u00eb momenti i par\u00eb. E dyta \u2014 kur sapo fillojm\u00eb zhvillimin, jemi nj\u00eb startup i vog\u00ebl, nuk kemi asgj\u00eb, zhvillimi n\u00ebn Kubernetes ose p\u00ebr arkitektur\u00ebn mikroserviz mund t\u00eb jet\u00eb i nd\u00ebrlikuar dhe jo gjithmon\u00eb i justifikuar ekonomikisht. M\u00eb intereson mendimi yt \u2014 a duhet q\u00eb startup-et nga zero t\u00eb fillojn\u00eb menj\u00ebher\u00eb t\u00eb kodojn\u00eb p\u00ebr Kubernetes apo mund t\u00eb shkruajn\u00eb nj\u00eb monolit dhe m\u00eb pas t\u00eb kalojn\u00eb te Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: Pyetje e shk\u00eblqyer. Kam nj\u00eb prezantim n\u00eb lidhje me mikroservizet \u00abMikroservizet: madh\u00ebsia ka r\u00ebnd\u00ebsi\u00bb.<\/a><\/noindex> Kam hasur shum\u00eb her\u00eb q\u00eb njer\u00ebzit p\u00ebrpiqen t\u00eb p\u00ebrdorin nj\u00eb mikroskop p\u00ebr t\u00eb goditur thumba. Qasja \u00ebsht\u00eb e drejt\u00eb, ne vet\u00eb projektimin e softuerit t\u00eb brendsh\u00ebm e b\u00ebjm\u00eb pik\u00ebrisht n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb. Por kur e b\u00ebni k\u00ebt\u00eb, duhet t\u00eb kuptoni qart\u00eb se \u00e7far\u00eb po b\u00ebni. M\u00eb s\u00eb shumti n\u00eb mikroservizet un\u00eb e urrehem fjal\u00ebn \u00abmikro\u00bb. Historikisht, kjo fjal\u00eb ka lindur atje, dhe p\u00ebr ndonj\u00eb arsye njer\u00ebzit mendojn\u00eb se mikro \u00ebsht\u00eb shum\u00eb e vog\u00ebl, m\u00eb e vog\u00ebl se milimetri, si mikrometri. Nuk \u00ebsht\u00eb k\u00ebshtu.<\/p>\n

P.sh. ka nj\u00eb monolit q\u00eb e shkruajn\u00eb 300 njer\u00ebz, dhe t\u00eb gjith\u00eb q\u00eb kan\u00eb marr\u00eb pjes\u00eb n\u00eb zhvillim e kuptojn\u00eb se ka probleme, dhe duhet ta ndajn\u00eb n\u00eb mikro-pjes\u00eb \u2014 rreth 10, secila prej t\u00eb cilave e shkruajn\u00eb 30 njer\u00ebz n\u00eb versionin minimal. Kjo \u00ebsht\u00eb e r\u00ebnd\u00ebsishme, e nevojshme dhe e shk\u00eblqyer. Por kur na vjen nj\u00eb startup ku 3 djem shum\u00eb t\u00eb talentuar kan\u00eb shkruar n\u00eb kolltuk 60 mikrosh\u00ebrbime, \u00e7do her\u00eb un\u00eb k\u00ebrkoj korvalol.<\/p>\n

M\u00eb duket se p\u00ebr k\u00ebt\u00eb jan\u00eb folur mij\u00ebra her\u00eb \u2014 kemi marr\u00eb nj\u00eb monolit t\u00eb shp\u00ebrndar\u00eb n\u00eb at\u00eb ose k\u00ebt\u00eb form\u00eb. Kjo \u00ebsht\u00eb ekonomikisht e paarsyeshme, shum\u00eb e v\u00ebshtir\u00eb n\u00eb p\u00ebrgjith\u00ebsi. Thjesht e kam par\u00eb kaq her\u00eb sa m\u00eb dhemb, prandaj vazhdoj t\u00eb flas p\u00ebr t\u00eb.<\/p>\n

P\u00ebr pyetjen fillestare, q\u00eb ka nj\u00eb konflikt midis faktit q\u00eb, nga nj\u00ebra an\u00eb, Kubernetes \u00ebsht\u00eb tmerr\u00ebsisht e v\u00ebshtir\u00eb p\u00ebr t'u p\u00ebrdorur, sepse nuk e di se \u00e7far\u00eb mund t\u00eb prishet ose t\u00eb mos funksionoj\u00eb, nga ana tjet\u00ebr, \u00ebsht\u00eb e qart\u00eb se gjith\u00e7ka po shkon atje dhe nuk do t\u00eb ket\u00eb asgj\u00eb tjet\u00ebr p\u00ebrve\u00e7 Kubernetes. P\u00ebrgjigja \u00ebsht\u00eb \u2014 t\u00eb vler\u00ebsojm\u00eb sasin\u00eb e p\u00ebrfitimit q\u00eb vjen, sasin\u00eb e detyrave q\u00eb mund t\u00eb zgjidhni.<\/b>. Kjo \u00ebsht\u00eb nj\u00ebra an\u00eb e pesh\u00ebs. An\u00eb tjet\u00ebr jan\u00eb rreziqet q\u00eb lidhen me ndalesat ose me uljen e koh\u00ebs s\u00eb reagimit, nivelit t\u00eb disponueshm\u00ebris\u00eb \u2014 me uljen e treguesve t\u00eb performanc\u00ebs.<\/p>\n

\u00c7\u00ebshtja \u00ebsht\u00eb k\u00ebshtu \u2014 ose ne l\u00ebvizim shpejt, dhe Kubernetes lejon t\u00eb b\u00ebjm\u00eb shum\u00eb gj\u00ebra m\u00eb shpejt dhe m\u00eb mir\u00eb, ose p\u00ebrdorim zgjidhje t\u00eb besueshme dhe t\u00eb provuara, por l\u00ebvizim shum\u00eb m\u00eb ngadal\u00eb. Ky \u00ebsht\u00eb nj\u00eb vendim q\u00eb \u00e7do kompani duhet ta b\u00ebj\u00eb. Mund ta shohim si nj\u00eb rrug\u00eb n\u00eb xhung\u00ebl \u2014 kur e b\u00ebn p\u00ebr her\u00eb t\u00eb par\u00eb, mund t\u00eb has\u00ebsh nj\u00eb gjarp\u00ebr, nj\u00eb tig\u00ebr ose nj\u00eb derr t\u00eb \u00e7mendur, dhe kur ke shkuar 10 her\u00eb \u2014 e ke thyer rrug\u00ebn, hequr deg\u00ebt dhe \u00ebsht\u00eb m\u00eb e leht\u00eb t\u00eb ec\u00ebsh. Me \u00e7do her\u00eb e m\u00eb gjer\u00eb rruga. Pastaj, b\u00ebhet nj\u00eb rrug\u00eb e asfaltuar, dhe m\u00eb von\u00eb nj\u00eb bulevard i bukur.<\/p>\n

Kubernetes po\u00a0shpejt\u00eb dhe\u00a0nuk q\u00ebndron n\u00eb\u00a0vend. P\u00ebrs\u00ebri pyetja: Kubernetes, nga nj\u00ebra an\u00eb, \u00ebsht\u00eb 4-5 binar\u00eb, nga ana tjet\u00ebr \u2014 kjo \u00ebsht\u00eb e gjith\u00eb ekosistemi. Kjo \u00ebsht\u00eb nj\u00eb sistem operativ q\u00eb e kemi n\u00eb\u00a0makinat tona. \u00c7far\u00eb \u00ebsht\u00eb? Ubuntu apo Curios? Ky \u00ebsht\u00eb b\u00ebrthama Linux, shum\u00eb komponent\u00eb shtes\u00eb. T\u00eb gjitha k\u00ebto gj\u00ebra k\u00ebtu hodh\u00ebn nj\u00eb gjarp\u00ebr helmues nga rruga, aty vendos\u00ebn nj\u00eb gardh. Kubernetes evoluon shum\u00eb shpejt dhe dinamike, dhe sasia e rreziqeve, sasia e t\u00eb panjohurave zvog\u00eblohet me \u00e7do muaj dhe, p\u00ebr pasoj\u00eb, k\u00ebto pesha rikthehen n\u00eb ekuilib\u00ebr.<\/p>\n

N\u00eb p\u00ebrgjigje t\u00eb pyetjes se \u00e7far\u00eb duhet t\u00eb b\u00ebj\u00eb nj\u00eb startup, do t\u00eb thosha - vijini \"Flant\", paguani 150,000 rubla dhe merrni nj\u00eb sh\u00ebrbim DevOps t\u00eb leht\u00eb me \u00e7el\u00ebs n\u00eb dor\u00eb. N\u00ebse jeni nj\u00eb startup i vog\u00ebl me disa zhvillues, kjo funksionon. N\u00eb vend q\u00eb t\u00eb angazhoni nj\u00eb DevOps t\u00eb vetin, i cili do t\u00eb duhet t\u00eb m\u00ebsoj\u00eb t\u00eb zgjidh\u00eb problemet tuaja dhe t'i paguaj\u00eb atij rrog\u00ebn n\u00eb at\u00eb koh\u00eb, do t\u00eb merrni nj\u00eb zgjidhje p\u00ebr t\u00eb gjitha \u00e7\u00ebshtjet me \u00e7el\u00ebs n\u00eb dor\u00eb. Po, ka disa t\u00eb meta. Ne, si nj\u00eb outsourcer, nuk mund t\u00eb jemi aq t\u00eb involvuar dhe t\u00eb reagojm\u00eb shpejt ndaj ndryshimeve. Por, kemi shum\u00eb ekspertiz\u00eb, praktik\u00eb t\u00eb gatshme. Ne garantojm\u00eb se n\u00eb \u00e7do situat\u00eb ne do t\u00eb p\u00ebrballim shpejt dhe do t\u00eb rrisim \u00e7do Kubernetes nga bot\u00ebt e tjera. <\/p>\n

Un\u00eb k\u00ebmbyesht rekomandoj outsourcingun p\u00ebr startupet dhe bizneset e vendosura deri n\u00eb pik\u00ebn kur mund t\u00eb dedikoni nj\u00eb ekip prej 10 njer\u00ebzish p\u00ebr operacion, sepse p\u00ebrndryshe nuk ka asnj\u00eb kuptim. Kjo ka kuptim t\u00eb jasht\u00ebzakonsh\u00ebm p\u00ebr t'u outsourcuar.<\/p><\/blockquote>\n

<\/p>\n

P\u00ebr Amazonin dhe Google<\/h2>\n

\n- A mund t\u00eb konsiderohet si outsourcing hostimi nga zgjidhja e Amazon ose Google?<\/b><\/p>\n

Dmitri<\/b>: Po, sigurisht, kjo zgjidh disa \u00e7\u00ebshtje. Por ka p\u00ebrs\u00ebri nuanca. Megjithat\u00eb, duhet t\u00eb kuptohet si ta p\u00ebrdor\u00ebsh. P\u00ebr shembull, ka mij\u00ebra detaje n\u00eb pun\u00ebn e Amazon AWS: Load Balanceri duhet ngrohur ose duhet t\u00eb d\u00ebrgohet nj\u00eb k\u00ebrkes\u00eb paraprakisht q\u00eb 'djem, do t\u00eb kemi trafik, lutem ngrohni Load Balancerin!' K\u00ebto nuanca duhet t\u00eb dihen.<\/p>\n

Kur i drejtoheni njer\u00ebzve q\u00eb specializohen n\u00eb k\u00ebt\u00eb, merrni pothuajse t\u00eb gjitha gj\u00ebrat standarde t\u00eb mbyllura. Tani kemi 40 inxhinier\u00eb, deri n\u00eb fund t\u00eb vitit, ndoshta do t\u00eb jemi 60 - ne sigurisht q\u00eb kemi hasur me t\u00eb gjitha k\u00ebto gj\u00ebra. Edhe n\u00ebse n\u00eb ndonj\u00eb projekt ne p\u00ebrballemi me k\u00ebt\u00eb problem p\u00ebrs\u00ebri, ne tashm\u00eb pyesim shpejt nj\u00ebri-tjetrin dhe dim\u00eb se si ta zgjidhim.<\/p>\n

Ndoshta p\u00ebrgjigjja \u00ebsht\u00eb se, sigurisht, historia e hostimit leht\u00ebson nj\u00eb pjes\u00eb t\u00eb caktuar. Pyetja \u00ebsht\u00eb, a jeni t\u00eb gatsh\u00ebm t\u00eb besoni k\u00ebta ofrues hostimi dhe a do t\u00eb zgjidhin ata problemet tuaja? Amazon dhe Google kan\u00eb treguar rezultate t\u00eb mira. P\u00ebr t\u00eb gjitha rastet tona - gjithashtu. Nuk kemi p\u00ebrvoj\u00eb pozitive nga ndonj\u00eb tjet\u00ebr. T\u00eb gjitha cloud-et e tjera me t\u00eb cilat kemi provuar t\u00eb punojm\u00eb krijojn\u00eb shum\u00eb probleme - dhe Ager, dhe gjith\u00e7ka q\u00eb ka n\u00eb Rusi, dhe OpenStack t\u00eb ndrysh\u00ebm n\u00eb realizime t\u00eb ndryshme: Headster, Overage - \u00e7far\u00ebdo q\u00eb d\u00ebshironi. T\u00eb gjitha k\u00ebto krijojn\u00eb probleme q\u00eb nuk doni t'i zgjidhni.<\/p>\n

Pra, p\u00ebrgjigjja \u00ebsht\u00eb po, por, n\u00eb fakt, nuk ka shum\u00eb zgjidhje t\u00eb pjekura t\u00eb hostuara.<\/p>\n

Kush ka nevoj\u00eb p\u00ebr Kubernetes?<\/h2>\n

\n\u2014 Dhe megjithat\u00eb, kush ka nevoj\u00eb p\u00ebr Kubernetes? Kush duhet t\u00eb kaloj\u00eb n\u00eb Kubernetes, kush \u00ebsht\u00eb klienti tipik i \"Flant\" q\u00eb vjen p\u00ebr Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: Pyetja \u00ebsht\u00eb interesante, sepse tani, n\u00eb val\u00ebn e Kubernetes, shum\u00eb na afrohen: \u00abDjem, e dim\u00eb q\u00eb ju b\u00ebni Kubernetes, na e b\u00ebni!\u00bb Ne u p\u00ebrgjigjemi: \u00abZot\u00ebrinj, ne nuk b\u00ebjm\u00eb Kubernetes, ne b\u00ebjm\u00eb prodhim dhe gjith\u00e7ka q\u00eb lidhet me t\u00eb.\u00bb Sepse t\u00eb b\u00ebsh prodhim pa b\u00ebr\u00eb t\u00eb gjith\u00eb CI\/CD-n\u00eb dhe t\u00eb gjith\u00eb k\u00ebt\u00eb histori, n\u00eb koh\u00ebt moderne \u00ebsht\u00eb thjesht e pamundur. T\u00eb gjith\u00eb kan\u00eb dal\u00eb nga ndarja p\u00ebr t\u00eb th\u00ebn\u00eb se ne kemi zhvillim p\u00ebr zhvillimin dhe pastaj funksionim p\u00ebr funksionimin.<\/p>\n

Klient\u00ebt tan\u00eb presin gj\u00ebra t\u00eb ndryshme, por t\u00eb gjith\u00eb presin ndonj\u00eb mrekulli t\u00eb mir\u00eb, q\u00eb ata kan\u00eb k\u00ebto ose ato probleme, dhe tani \u2013 hop! \u2013 Kubernetes do t'i zgjidh\u00eb. Njer\u00ebzit besojn\u00eb n\u00eb mrekulli. Me mendje e kuptojn\u00eb q\u00eb s'ka p\u00ebr t\u00eb pasur mrekulli, por me shpirt shpresojn\u00eb \u2013 ndoshta ky Kubernetes tani do t\u00eb zgjidh\u00eb gjith\u00e7ka p\u00ebr ne, flitet kaq shum\u00eb p\u00ebr t\u00eb! Ndoshta ai tani \u2013 \u00e7ik! \u2013 dhe gjuha argjendi, \u00e7ik! \u2013 dhe ne kemi 100% uptime, t\u00eb gjith\u00eb zhvilluesit mund t\u00eb l\u00ebshojn\u00eb gjith\u00e7ka 50 her\u00eb n\u00eb prodhim, dhe nuk jepet. N\u00eb p\u00ebrgjith\u00ebsi, mrekulli!<\/p>\n

Kur njer\u00ebz t\u00eb till\u00eb na vizitojn\u00eb, ne themi: \"Na falni, por nuk ka mrekulli\". P\u00ebr t\u00eb q\u00ebn\u00eb t\u00eb sh\u00ebndetsh\u00ebm, duhet t\u00eb ushqehesh mir\u00eb dhe t\u00eb b\u00ebsh sport. P\u00ebr t\u00eb pasur nj\u00eb server t\u00eb sigurt, ai duhet t\u00eb nd\u00ebrtohet si\u00e7 duhet. P\u00ebr t\u00eb pasur nj\u00eb CI\/CD komod, ai duhet t\u00eb realizohet si i till\u00eb. Kjo \u00ebsht\u00eb shum\u00eb pun\u00eb q\u00eb duhen b\u00ebr\u00eb.<\/p>\n

Dhe p\u00ebrgjigjja p\u00ebr pyetjen, kush ka nevoj\u00eb p\u00ebr Kubernetes \u2014 Kubernetes nuk i nevojitet askujt.<\/p><\/blockquote>\n

\nDisa njer\u00ebz kan\u00eb nj\u00eb ndjenj\u00eb t\u00eb gabuar se u nevojitet Kubernetes. Njer\u00ebzve u nevojitet, ata kan\u00eb nj\u00eb nevoj\u00eb t\u00eb thell\u00eb p\u00ebr t\u00eb ndaluar s\u00eb menduari, s\u00eb punuari, dhe s\u00eb interesuar p\u00ebr t\u00eb gjitha problemet e infrastruktur\u00ebs dhe problemet e lan\u00e7imit t\u00eb aplikacioneve t\u00eb tyre. Ata duan q\u00eb aplikacionet t\u00eb funksionojn\u00eb thjesht dhe t\u00eb vendosen thjesht. P\u00ebr ta, Kubernetes \u00ebsht\u00eb shpresa se do t\u00eb ndalin s\u00eb d\u00ebgjuari historin\u00eb q\u00eb \"ne kemi pasur probleme\" apo \"nuk mund t\u00eb dalim live\", ose di\u00e7ka tjet\u00ebr.<\/p>\n

Zakon \u00ebsht\u00eb se zakonisht na vjen drejtori teknik. Prej tij k\u00ebrkohen dy gj\u00ebra: nga nj\u00ebra an\u00eb, na jep karakteristika, nga ana tjet\u00ebr - stabilitet. Ne e ofrojm\u00eb q\u00eb ta marrim k\u00ebt\u00eb mbi vete dhe ta realizojm\u00eb. Plani ideal, p\u00ebr t\u00eb qen\u00eb m\u00eb korrekt, \u00ebsht\u00eb q\u00eb ti t\u00eb ndalosh s\u00eb menduari p\u00ebr k\u00ebto probleme dhe t\u00eb mos humb\u00ebsh koh\u00eb. Do t\u00eb kesh njer\u00ebz t\u00eb ve\u00e7ant\u00eb q\u00eb do ta zgjidhin k\u00ebt\u00eb \u00e7\u00ebshtje.<\/p>\n

Formulimi se ne ose dikush tjet\u00ebr ka nevoj\u00eb p\u00ebr Kubernetes \u00ebsht\u00eb i gabuar.<\/p><\/blockquote>\n

\nKubernetes \u00ebsht\u00eb shum\u00eb i nevojsh\u00ebm p\u00ebr administrator\u00ebt, sepse \u00ebsht\u00eb nj\u00eb loj\u00eb shum\u00eb interesante me t\u00eb cil\u00ebn mund t\u00eb luash, t\u00eb eksperimentosh. Le t\u00eb jemi t\u00eb sinqert\u00eb - t\u00eb gjith\u00eb i duan lodrat. T\u00eb gjith\u00eb ne ndonj\u00ebher\u00eb jemi f\u00ebmij\u00eb, dhe kur shohim ndonj\u00eb gj\u00eb t\u00eb re - duam t\u00eb luajm\u00eb me t\u00eb. Disa e kan\u00eb humbur k\u00ebt\u00eb, p\u00ebr shembull, n\u00eb administrim, sepse tashm\u00eb jan\u00eb lodhur dhe ua ka tejkaluar deri n\u00eb pik\u00ebn q\u00eb thjesht nuk duan. Por kjo nuk \u00ebsht\u00eb humbur plot\u00ebsisht p\u00ebr ask\u00ebnd. P\u00ebr shembull, n\u00ebse m\u00eb jan\u00eb lodhur lodrat n\u00eb fush\u00ebn e administrat\u00ebs s\u00eb sistemeve dhe DevOps, un\u00eb ende i dua lodrat, dhe gjithsesi blej di\u00e7ka t\u00eb re.<\/p>\n

Mos luani me prodhimin. Ajo q\u00eb un\u00eb kategori\u00e7ikisht nuk e rekomandoj t\u00eb b\u00ebni dhe q\u00eb shoh tani masivisht \u00ebsht\u00eb: \"Ah, nj\u00eb lod\u00ebr e re!\" - vrapuam ta blejm\u00eb, e blen\u00eb dhe: \"Le t\u00eb shkojm\u00eb tani n\u00eb shkoll\u00eb, t'ua tregojm\u00eb t\u00eb gjith\u00ebve miqt\u00eb.\" Mos e b\u00ebni k\u00ebt\u00eb. M\u00eb vjen keq, ndjej vet\u00ebm se f\u00ebmij\u00ebt e mi po rriten, vazhdimisht shoh di\u00e7ka tek ta, e v\u00ebrej n\u00eb veten time dhe pastaj e p\u00ebrgjithsoj te t\u00eb tjer\u00ebt.<\/p>\n

P\u00ebrgjigja p\u00ebrfundimtare: nuk keni nevoj\u00eb p\u00ebr Kubernetes. Duhet t\u00eb zgjidhni problemet tuaja.<\/p><\/blockquote>\n

\nMund t\u00eb arrihet q\u00eb:<\/p>\n