{"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> Vitalij Khabarov<\/b> ka intervistuar\u00a0Dmitri Stolyarov<\/b> (distol<\/a><\/noindex>), drejtori teknik dhe bashk\u00ebthemelues i kompanis\u00eb \"Flant\". Vitalij e pyeti Dmitrin p\u00ebr at\u00eb \u00e7far\u00eb b\u00ebn \"Flant\", p\u00ebr Kubernetes, zhvillimin e ekosistemit, mb\u00ebshtetje. Diskutuan p\u00ebrse \u00ebsht\u00eb e nevojshme Kubernetes dhe a \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb e nevojshme. Gjithashtu fol\u00ebn p\u00ebr mikrosh\u00ebrbimet, Amazon AWS, qasjen \"Do 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 ndritshme dhe t\u00eb af\u00ebrt me thjeshtimin dhe rrjetet neuromore.<\/p>\n

Origjinali i intervist\u00ebs<\/a><\/noindex> n\u00eb form\u00ebn e nj\u00eb podkasti mund ta d\u00ebgjoni n\u00eb DevOps Deflope - podkastin n\u00eb gjuh\u00ebn ruse p\u00ebr DevOps, nd\u00ebrsa m\u00eb posht\u00eb - versioni tekstual. <\/p>\n

\"Kubernetes
\n
\nK\u00ebtu dhe m\u00eb tej pyetjet i b\u00ebn Vitalij Khabarov<\/a><\/noindex> inxhinieri nga Express42.
\n<\/a><\/noindex><\/p>\n

P\u00ebr \"Flant\"<\/h2>\n

\n- Dima, p\u00ebrsh\u00ebndetje. Ti je drejtori teknik i \"Flant<\/a><\/noindex>\" dhe gjithashtu themeluesi i saj. T\u00eb lutem, tregoi pak p\u00ebr at\u00eb \u00e7far\u00eb b\u00ebn kompania dhe ti n\u00eb t\u00eb?<\/b><\/p>\n

\"KubernetesDmitri<\/b>: Nga jasht\u00eb duket si t\u00eb ishim disa djem q\u00eb sh\u00ebtisin dhe vendosin Kubernetes dhe b\u00ebjn\u00eb di\u00e7ka me t\u00eb. Por nuk \u00ebsht\u00eb k\u00ebshtu. Ne kemi filluar si nj\u00eb kompani q\u00eb merret me Linux, por prej shum\u00eb koh\u00ebsh aktiviteti yn\u00eb kryesor \u00ebsht\u00eb p\u00ebrkujdesja p\u00ebr projekte me prodhim dhe highload nga fillimi n\u00eb fund. Zakonisht nd\u00ebrtojm\u00eb t\u00eb gjith\u00eb infrastruktur\u00ebn nga e para dhe pastaj mbajm\u00eb p\u00ebrgjegj\u00ebsi p\u00ebr t\u00eb p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb. Prandaj, puna kryesore q\u00eb kryen \"Flant\", p\u00ebr t\u00eb cil\u00ebn merr pages\u00eb, \u00ebsht\u00eb marrja e p\u00ebrgjegj\u00ebsis\u00eb dhe realizimi i prodhimit nga fillimi n\u00eb fund.<\/b>.
\n

\n

\nUn\u00eb, si drejtori teknik dhe nj\u00eb nga themeluesit e kompanis\u00eb, merrem gjat\u00eb gjith\u00eb dit\u00ebs me at\u00eb se si t\u00eb rris disponueshm\u00ebrin\u00eb e prodhimit, ta thjeshtoj p\u00ebrdorimin e tij, t'i leht\u00ebsoj jet\u00ebn administrator\u00ebve dhe t'u b\u00ebj jet\u00ebn zhvilluesve m\u00eb t\u00eb k\u00ebndshme.<\/p>\n

P\u00ebr Kubernetes<\/h2>\n

\n- Koh\u00ebt e fundit nga \"Flant\" shoh shum\u00eb ligj\u00ebrata dhe\u00a0artikull<\/a><\/noindex> p\u00ebr Kubernetes. Si e arrit\u00ebt at\u00eb?<\/b><\/p>\n

Dmitri<\/b>: Un\u00eb kam treguar p\u00ebr k\u00ebt\u00eb shum\u00eb her\u00eb, por fare nuk m\u00eb vjen keq ta p\u00ebrs\u00ebris. Mendoj se \u00ebsht\u00eb e duhur t\u00eb p\u00ebrs\u00ebris k\u00ebt\u00eb tem\u00eb, sepse ndodhin konfuzionet mes shkakut dhe pasoj\u00ebs.<\/p>\n

Na duhej na duhej na duhej na duhej na duhej nevoj\u00eb p\u00ebr nj\u00eb instrument. Kishim p\u00ebrballur me nj\u00eb mori problemesh, luftuam dhe i kaluam ato me metoda t\u00eb ndryshme dhe ndjenim nevoj\u00ebn p\u00ebr nj\u00eb instrument. Provonim shum\u00eb mund\u00ebsi t\u00eb ndryshme, krijonim bi\u00e7ikletat tona dhe grumbulloheshim p\u00ebrvoj\u00eb. Gradualisht arrit\u00ebm n\u00eb pik\u00ebn ku filluam t\u00eb p\u00ebrdornim Docker gati menj\u00ebher\u00eb sapo u shfaq \u2014 rreth vitit 2013. N\u00eb momentin e shfaqjes s\u00eb tij, ne tashm\u00eb kishim p\u00ebrvoj\u00eb t\u00eb madhe me kontejner\u00ebt, kishim shkruar nj\u00eb analog t\u00eb \"Docker\" \u2014 disa nga metodat tona t\u00eb ndryshme n\u00eb Python. Me shfaqjen e Docker ishte e mundur t\u00eb heqnim metodat e zakonshme dhe t\u00eb p\u00ebrdornim nj\u00eb zgjidhje t\u00eb sigurt dhe t\u00eb mb\u00ebshtetur nga komuniteti.<\/p>\n

Historia me Kubernetes \u00ebsht\u00eb e ngjashme. N\u00eb momentin kur ai filloi t\u00eb merrte pik\u00eb, \u2014 p\u00ebr ne kjo ishte versioni 1.2, \u2014 ne kishim tashm\u00eb nj\u00eb mori metodash t\u00eb ndryshme n\u00eb Shell dhe n\u00eb Chef, t\u00eb cilat tentonim t'i orkestronim me Docker. Ne shikonim seriozisht n\u00eb drejtim t\u00eb Rancher dhe zgjidhjeve t\u00eb tjera t\u00eb ndryshme, por k\u00ebtu u shfaq Kubernetes, n\u00eb t\u00eb cilin \u00ebsht\u00eb realizuar gjith\u00e7ka ashtu si do ta b\u00ebnim ne ose edhe m\u00eb mir\u00eb. Nuk ka asgj\u00eb p\u00ebr ta kritikuar.<\/p>\n

Po, po, ka ndodhin disa pap\u00ebrfundime, ka disa gj\u00ebra q\u00eb nuk jan\u00eb p\u00ebrfunduar \u2013 shum\u00eb pap\u00ebrfundime, dhe 1.2 \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb e frikshme, por\u2026 Kubernetes \u00ebsht\u00eb si nj\u00eb nd\u00ebrtes\u00eb n\u00eb nd\u00ebrtim \u2013 e shikon projektin dhe kupton se do t\u00eb jet\u00eb di\u00e7ka e shk\u00eblqyer. N\u00ebse nd\u00ebrtesa tani ka themelin dhe dy kate, kupton se \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb mos vendosesh akoma, nd\u00ebrsa me softin nuk ka k\u00ebto probleme \u2013 mund ta p\u00ebrdor\u00ebsh tashm\u00eb.<\/p>\n

Nuk pat\u00ebm ndonj\u00eb moment ku mendonim n\u00ebse do t\u00eb p\u00ebrdorim Kubernetes apo jo. E prit\u00ebm at\u00eb shum\u00eb p\u00ebrpara se t\u00eb shfaqej dhe provonim t\u00eb krijonim vet\u00eb analoge.<\/p><\/blockquote>\n

<\/p>\n

Rreth Kubernetes<\/h2>\n

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

Dmitri<\/b>: Pjes\u00ebrisht. M\u00eb tep\u00ebr jemi t\u00eb angazhuar n\u00eb zhvillimin e ekosistem\u00ebs. D\u00ebrgojm\u00eb nj\u00eb num\u00ebr t\u00eb caktuar k\u00ebrkesash pull: n\u00eb Prometheus, n\u00eb operator\u00eb t\u00eb ndrysh\u00ebm, n\u00eb Helm \u2014 n\u00eb ekosistem\u00eb. Fatkeq\u00ebsisht, nuk mund t\u00eb ndjek \u00e7do gj\u00eb q\u00eb b\u00ebjm\u00eb dhe mund t\u00eb gaboj, por nuk kemi asnj\u00eb pull p\u00ebr b\u00ebrtham\u00ebn.<\/p>\n

\u2014 Nd\u00ebrkoh\u00eb ju po zhvilloni dhe shum\u00eb instrumente t\u00eb tjer\u00eb p\u00ebrreth Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: Strategjia \u00ebsht\u00eb e till\u00eb: ne shkojm\u00eb dhe k\u00ebrkojm\u00eb pull n\u00eb gjith\u00e7ka q\u00eb ekziston. N\u00ebse atje nuk pranohen k\u00ebrkesat pull, ne thjesht e forkojm\u00eb p\u00ebr veten ton\u00eb dhe jetojm\u00eb deri sa ato t\u00eb pranohen me nd\u00ebrtimet tona. Pastaj, kur kjo arrin n\u00eb upstream, kthehemi n\u00eb versionin upstream.<\/p>\n

P\u00ebr shembull, ne kemi nj\u00eb operator Prometheus, me t\u00eb cilin kemi kaluar p\u00ebrtej upstream-it t\u00eb nd\u00ebrtimit ton\u00eb tashm\u00eb rreth 5 her\u00eb, ndoshta. Na nevojitet ndonj\u00eb funksionalitet, d\u00ebrguam nj\u00eb pull request, na duhet ta l\u00ebshojm\u00eb at\u00eb nes\u00ebr, dhe nuk d\u00ebshirojm\u00eb t\u00eb presim derisa ta publikojn\u00eb n\u00eb upstream. Prandaj, ne e p\u00ebrgatisim nd\u00ebrtimin ton\u00eb me funksionalitetin ton\u00eb q\u00eb na nevojitet, n\u00eb t\u00eb gjitha klasteret tona. M\u00eb pas, kjo ri-d\u00ebrgohet n\u00eb upstream me fjal\u00ebt: \u00abDjem, le t\u00eb b\u00ebjm\u00eb p\u00ebr nj\u00eb rast m\u00eb t\u00eb p\u00ebrgjithsh\u00ebm\u00bb, ne, ose dikush tjet\u00ebr, e p\u00ebrfundon at\u00eb, dhe me kalimin e koh\u00ebs, p\u00ebrs\u00ebri bashkohet.<\/p>\n

\u00c7do gj\u00eb q\u00eb ekziston, ne p\u00ebrpiqemi ta zhvillojm\u00eb.<\/b>. Shum\u00eb elemente, t\u00eb cilat ende nuk ekzistojn\u00eb, nuk jan\u00eb shpikur ende ose jan\u00eb shpikur, por nuk jan\u00eb realizuar ende \u2014 ne i b\u00ebjm\u00eb. Dhe jo sepse na p\u00eblqen procesi vet\u00eb ose nd\u00ebrtimi i bi\u00e7ikletave si nj\u00eb industri, por thjesht sepse na nevojitet ky mjet. Shpesh b\u00ebhet pyetja, pse kemi b\u00ebr\u00eb at\u00eb ose k\u00ebt\u00eb gj\u00eb? P\u00ebrgjigjja \u00ebsht\u00eb e thjesht\u00eb \u2014 sepse duhej t\u00eb shkonim p\u00ebrpara, t\u00eb zgjidhnim ndonj\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 me shum\u00eb kujdes dhe, n\u00ebse nuk gjejm\u00eb ndonj\u00eb zgjidhje, si t\u00eb b\u00ebjm\u00eb nj\u00eb buk\u00eb t\u00eb thekur nj\u00eb trolebuz, at\u00ebher\u00eb b\u00ebjm\u00eb buk\u00ebn ton\u00eb dhe trolebuzin ton\u00eb.<\/p><\/blockquote>\n

<\/p>\n

Mjetet e \u00abFlant\u00bb<\/h2>\n

\n\u2014 M\u00eb \u00ebsht\u00eb njoftuar se tani \u00abFlant\u00bb ka addon-operator\u00eb, operator\u00eb shell, mjete dapp\/werf. Si\u00e7 kuptoj, kjo \u00ebsht\u00eb e nj\u00ebjta mjet n\u00eb inkarnime t\u00eb ndryshme. Gjithashtu kuptoj q\u00eb brenda \u00abFlant\u00bb ekzistojn\u00eb shum\u00eb mjete t\u00eb tjera t\u00eb ndryshme. A \u00ebsht\u00eb k\u00ebshtu?<\/b><\/p>\n

Dmitri<\/b>: Ne kemi shum\u00eb gj\u00ebra t\u00eb tjera n\u00eb GitHub. nga ato q\u00eb un\u00eb mund t\u00eb kujtoj tani, kemi statusmap \u2014 nj\u00eb panel p\u00ebr Grafana, i cili ka qen\u00eb i njohur p\u00ebr t\u00eb gjith\u00eb. E p\u00ebrmend pak a shum\u00eb n\u00eb \u00e7do artikull t\u00eb dyt\u00eb mbi monitorimin e Kubernetes n\u00eb Medium. \u00cbsht\u00eb e pamundur t\u00eb flas\u00ebsh shkurtimisht p\u00ebr at\u00eb q\u00eb \u00ebsht\u00eb statusmap \u2014 k\u00ebrkohet nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb, por \u00ebsht\u00eb nj\u00eb gj\u00eb shum\u00eb e dobishme p\u00ebr monitorimin e statusit n\u00eb koh\u00eb, sepse n\u00eb Kubernetes na nevojitet shpesh t\u00eb tregojm\u00eb statusin n\u00eb koh\u00eb. Gjithashtu, ne kemi LogHouse \u2014 nj\u00eb gj\u00eb e bazuar n\u00eb ClickHouse dhe magji t\u00eb zez\u00eb p\u00ebr mbledhjen e logeve n\u00eb Kubernetes.<\/p>\n

M\u00ebnyra shum\u00eb utilitar\u00ebve! Dhe do t\u00eb ket\u00eb m\u00eb shum\u00eb, sepse nj\u00eb sasi e caktuar e zgjidhjeve t\u00eb brendshme do t\u00eb l\u00ebshohen k\u00ebt\u00eb vit. Nga utilitar\u00ebt e m\u00ebdhenj bazuar n\u00eb operatorin addon, ka nj\u00eb s\u00ebr\u00eb addons p\u00ebr Kubernetes si\u00e7 \u00ebsht\u00eb m\u00ebnyra e duhur p\u00ebr t\u00eb vendosur sert manager \u2014 nj\u00eb mjet p\u00ebr menaxhimin e certifikatave, si dhe m\u00ebnyra e duhur p\u00ebr t\u00eb vendosur Prometheus me shum\u00eb shtesa \u2014 k\u00ebto jan\u00eb rreth nj\u00ebzet binar\u00eb t\u00eb ndrysh\u00ebm q\u00eb eksportojn\u00eb t\u00eb dh\u00ebna dhe b\u00ebjn\u00eb di\u00e7ka, p\u00ebr k\u00ebt\u00eb Prometheus ofron grafik\u00eb t\u00eb shk\u00eblqyer dhe alarme. T\u00eb gjitha k\u00ebto jan\u00eb thjesht nj\u00eb s\u00ebr\u00eb addons p\u00ebr Kubernetes, t\u00eb cilat instalohen n\u00eb klaster dhe ai kthehet nga nj\u00eb i thjesht\u00eb n\u00eb nj\u00eb t\u00eb avancuar, automatik, n\u00eb t\u00eb cilin shum\u00eb pyetje tashm\u00eb jan\u00eb zgjidhur. Po, b\u00ebjm\u00eb shum\u00eb.<\/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 mjeti dhe metodave t\u00eb p\u00ebrdorimit t\u00eb tij. A mund t\u00eb b\u00ebsh nj\u00eb vler\u00ebsim se kush tjet\u00ebr do t\u00eb kontribuonte n\u00eb zhvillimin e ekosistemit?<\/b><\/p>\n

Dmitri<\/b>: N\u00eb Rusi, nga ato kompani q\u00eb veprojn\u00eb n\u00eb tregun ton\u00eb \u2014 askush, as edhe n\u00eb af\u00ebrsi<\/b>. Sigurisht, kjo \u00ebsht\u00eb nj\u00eb deklarat\u00eb e fuqishme, sepse ka lojtar\u00eb t\u00eb m\u00ebdhenj si Mail dhe Yandex \u2014 ata gjithashtu po b\u00ebjn\u00eb di\u00e7ka me Kubernetes, por edhe ata nuk i jan\u00eb afruar kontributit t\u00eb kompanive n\u00eb t\u00ebr\u00ebsi n\u00eb mbar\u00eb bot\u00ebn, 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 staf prej 80 njer\u00ebzish dhe Red Hat, ku vet\u00ebm p\u00ebr nj\u00eb Kubernetes ka 300 inxhinier\u00eb, n\u00ebse nuk gaboj. E v\u00ebshtir\u00eb t\u00eb krahasosh. Ne kemi n\u00eb departamentin ton\u00eb t\u00eb RnD 6 njer\u00ebz, duke p\u00ebrfshir\u00eb veten, q\u00eb punojn\u00eb n\u00eb t\u00eb gjitha mjetet tona. 6 njer\u00ebz p\u00ebrball\u00eb 300 inxhinier\u00ebve t\u00eb Red Hat \u2014 \u00ebsht\u00eb pak e v\u00ebshtir\u00eb p\u00ebr t'u krahasuar.<\/p>\n

\u2014 Megjithat\u00eb, kur edhe k\u00ebta 6 njer\u00ebz mund t\u00eb b\u00ebjn\u00eb di\u00e7ka me vler\u00eb t\u00eb v\u00ebrtet\u00eb dhe t\u00eb transferueshme, kur ata p\u00ebrballen me nj\u00eb problem praktik dhe japin zgjidhjen n\u00eb komunitet \u2014 \u00ebsht\u00eb nj\u00eb rast interesant. E kuptoj se n\u00eb kompanit\u00eb e m\u00ebdha teknologjike, ku ka zhvillim dhe nj\u00eb ekip mb\u00ebshtetje p\u00ebr Kubernetes, mund t\u00eb zhvillohen gjithashtu mjete t\u00eb tilla. Ky \u00ebsht\u00eb nj\u00eb shembull p\u00ebr ta se \u00e7far\u00eb mund t\u00eb zhvillohet dhe t\u00eb jepet n\u00eb komunitet, t\u00eb jap\u00eb nj\u00eb nxitje p\u00ebr t\u00eb gjith\u00eb komunitetin q\u00eb p\u00ebrdor Kubernetes.<\/b><\/p>\n

Dmitri<\/b>: Ndoshta \u00ebsht\u00eb kjo nj\u00eb ve\u00e7ori e integratorit. Ne kemi shum\u00eb projekte dhe shohim shum\u00eb situata t\u00eb ndryshme. P\u00ebr ne, m\u00ebnyra kryesore p\u00ebr t\u00eb krijuar vler\u00eb t\u00eb shtuar \u00ebsht\u00eb t\u00eb analizojm\u00eb k\u00ebto raste, t\u00eb gjejm\u00eb t\u00eb p\u00ebrbashk\u00ebtat dhe t'i ulim sa m\u00eb shum\u00eb kostot p\u00ebr ne. K\u00ebto jan\u00eb aktivitete me t\u00eb cilat merremi aktivisht. M\u00eb \u00ebsht\u00eb v\u00ebshtir\u00eb t\u00eb flas p\u00ebr Rusin\u00eb dhe bot\u00ebn, por kemi rreth 40 inxhinier\u00eb DevOps n\u00eb kompani q\u00eb merren me Kubernetes. Nuk mendoj se n\u00eb Rusi ka shum\u00eb kompani me nj\u00eb num\u00ebr t\u00eb ngjash\u00ebm specialist\u00ebsh q\u00eb kuptojn\u00eb Kubernetes, n\u00ebse ndonj\u00ebher\u00eb ka.<\/p>\n

E kuptoj gjith\u00e7ka p\u00ebr titullin e pun\u00ebs DevOps-inxhinier, t\u00eb gjith\u00eb e din\u00eb dhe jan\u00eb m\u00ebsuar ta quajn\u00eb DevOps-inxhinier\u00ebt si t\u00eb till\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, mjeti nuk do t\u00eb ket\u00eb vler\u00eb, sepse diku n\u00eb komunitet do t\u00eb shfaqet nj\u00eb mjet i gatsh\u00ebm. Nuk ka kuptim t\u00eb akumulojm\u00eb k\u00ebt\u00eb p\u00ebrvoj\u00eb brenda \u2014 \u00ebsht\u00eb thjesht nj\u00eb humbje kohe dhe energjie. Por ne jemi plot\u00ebsisht t\u00eb gatsh\u00ebm ta ndajm\u00eb. Ne me k\u00ebnaq\u00ebsi e publikojm\u00eb gjith\u00e7ka dhe kuptohet se duhet ta publikohet, zhvillohet, promovuar, q\u00eb njer\u00ebzit ta p\u00ebrdorin dhe t'i shtojn\u00eb p\u00ebrvojat e tyre \u2014 at\u00ebher\u00eb gjith\u00e7ka rritet dhe jeton. Pas dy vitesh, mjeti nuk do t\u00eb p\u00ebrfundonte n\u00eb plehra. Nuk na vjen keq t\u00eb vazhdojm\u00eb t\u00eb investojm\u00eb energji, sepse \u00ebsht\u00eb e qart\u00eb se dikush po e p\u00ebrdor mjetin ton\u00eb, dhe pas dy vitesh, tashm\u00eb t\u00eb gjith\u00eb po e p\u00ebrdorin at\u00eb.<\/p>\n

Kjo \u00ebsht\u00eb nj\u00eb pjes\u00eb e strategjis\u00eb son\u00eb t\u00eb madhe me dapp\/werf<\/b>. Nuk e mbaj mend se kur filluam ta b\u00ebjm\u00eb, duket se ishim rreth 3 vjet m\u00eb par\u00eb. Fillimisht ishte plot\u00ebsisht n\u00eb shell. Ishte nj\u00eb prov\u00eb e shk\u00eblqyer e konceptit, ne zgjidh\u00ebm disa nga problemet tona private \u2014 rezultoi! Por me shell ka probleme, nuk \u00ebsht\u00eb e mundur t\u00eb vazhdohet m\u00eb tej, programimi n\u00eb shell \u00ebsht\u00eb nj\u00eb aktivitet i v\u00ebshtir\u00eb. Kemi pasur zakonin t\u00eb shkruajm\u00eb n\u00eb Ruby, k\u00ebshtu q\u00eb, p\u00ebrkat\u00ebsisht, b\u00ebjm\u00eb disa riorganizime n\u00eb Ruby dhe vazhduam, vazhduam dhe ndesh\u00ebm n\u00eb faktin q\u00eb komuniteti, turma, q\u00eb nuk thot\u00eb 'ne duam apo nuk duam', mbron hund\u00ebt nga Ruby, saq\u00eb \u00ebsht\u00eb qesharake. E kuptuam se duhet t\u00eb shkruajm\u00eb gjith\u00e7ka n\u00eb Go, p\u00ebr t\u00eb p\u00ebrmbushur pik\u00ebn e par\u00eb n\u00eb list\u00ebn e kontrollit: Mjeti DevOps duhet t\u00eb jet\u00eb nj\u00eb binar statik.<\/b>N\u00eb Go ose jo n\u00eb Go nuk ka shum\u00eb r\u00ebnd\u00ebsi, por m\u00eb mir\u00eb nj\u00eb binar statik i shkruar n\u00eb Go.<\/p>\n

Kemi shpenzuar forca, rishkruam dapp-in n\u00eb Go dhe e quajt\u00ebm werf. Dapp-i nuk mb\u00ebshtetet m\u00eb, nuk zhvillohet, punon n\u00eb nj\u00eb version t\u00eb fundit, por ka nj\u00eb rrug\u00eb absolute p\u00ebr upgrade dhe mund t\u00eb ndiqet.<\/p>\n

Pse u krijua dapp<\/h2>\n

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

Dmitri<\/b>: Arsyeja e par\u00eb \u00ebsht\u00eb nd\u00ebrtimi. Fillimisht ishim p\u00ebrball\u00eb problemeve t\u00eb m\u00ebdha me nd\u00ebrtimin, kur Docker nuk dinte p\u00ebr multi-stage, dhe ne e b\u00ebm\u00eb multi-stage me forcat tona. Pastaj kishim nj\u00eb mori pyetjesh t\u00eb tjera lidhur me pastrimin e images. T\u00eb gjith\u00eb ata q\u00eb b\u00ebjn\u00eb CI\/CD, m\u00eb shpejt se m\u00eb von\u00eb, p\u00ebrballen me problemin se ka nj\u00eb mori images t\u00eb nd\u00ebrtuara, dhe duhet t\u00eb pastroni at\u00eb q\u00eb nuk \u00ebsht\u00eb e nevojshme dhe t\u00eb lini at\u00eb q\u00eb \u00ebsht\u00eb e nevojshme.<\/p>\n

Arsyeja e dyt\u00eb \u00ebsht\u00eb deploy-i. Po, ka Helm, por ai zgjidh vet\u00ebm nj\u00eb pjes\u00eb t\u00eb problemeve. \u00c7udit\u00ebrisht, \u00ebsht\u00eb shkruar se \"Helm - menaxheri i paketave p\u00ebr Kubernetes\". Sakt\u00ebsisht, \"ai\". Ka edhe fjal\u00ebt \"menaxheri i paketave\" - \u00e7far\u00eb pritet zakonisht nga nj\u00eb menaxher paketash? Ne themi: \"Menaxher pakete - vendos paket\u00ebn!\" dhe presim q\u00eb ai t\u00eb na thot\u00eb: \"Paket\u00eb e vendosur\". <\/p>\n

\u00cbsht\u00eb interesante se ne themi: \"Helm, vendos paket\u00ebn\", dhe kur ai p\u00ebrgjigjet q\u00eb e ka vendosur, zbulojm\u00eb se ai vet\u00ebm ka nisur instalimin - i tha Kubernetes: \"K\u00ebt\u00eb gj\u00eb nise!\", dhe n\u00ebse ajo ka filluar apo jo, n\u00ebse punon apo jo, Helm nuk e trajton k\u00ebt\u00eb \u00e7\u00ebshtje fare.<\/p>\n

K\u00ebshtu q\u00eb rezulton se Helm \u00ebsht\u00eb thjesht nj\u00eb preprocessori tekstual q\u00eb ngarkohet me t\u00eb dh\u00ebna n\u00eb Kubernetes.<\/p><\/blockquote>\n

\nPor ne n\u00eb kuad\u00ebr t\u00eb \u00e7do deploy-i duam t\u00eb dim\u00eb - a u nxorr aplikacioni n\u00eb prodhim apo jo? U nxorr n\u00eb prodhim do t\u00eb thot\u00eb q\u00eb aplikacioni atje doli, nj\u00eb version i ri u vendos dhe ai aty s\u00eb paku nuk bie dhe p\u00ebrgjigjet sakt\u00eb. Helm nuk e zgjidh k\u00ebt\u00eb detyr\u00eb. P\u00ebr ta zgjidhur, duhet t\u00eb shpenzojm\u00eb shum\u00eb forca, sepse duhet t'i japim Kubernetes komand\u00ebn t\u00eb nxjerr\u00eb dhe t\u00eb ndjekim se \u00e7far\u00eb po ndodh atje - a u vendos, a doli. Dhe ka nj\u00eb mori detyrash lidhur me deploy-in, pastrimin, nd\u00ebrtimin.<\/p>\n

Planet<\/h2>\n

\nEdhe k\u00ebt\u00eb vit ne do t\u00eb fillojm\u00eb zhvillimin lokal. Duam t\u00eb arrijm\u00eb n\u00eb at\u00eb q\u00eb ishte m\u00eb par\u00eb n\u00eb Vagrant - thjesht t\u00eb shkruajm\u00eb \u00abvagrant up\u00bb dhe t\u00eb kemi virtualet tona t\u00eb ngritura. D\u00ebshirojm\u00eb t\u00eb arrijm\u00eb nj\u00eb gjendje ku ka nj\u00eb projekt n\u00eb Git, ne shkruajm\u00eb \u00abwerf up\u00bb, dhe ai ngre nj\u00eb kopje lokale t\u00eb k\u00ebtij projekti, e cila funksionon n\u00eb nj\u00eb mini-Kub lokal, me t\u00eb gjitha drejtorit\u00eb e lidhura q\u00eb jan\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr zhvillim. Var\u00ebsisht nga gjuha e zhvillimit, kjo ekzekutohet n\u00eb m\u00ebnyra t\u00eb ndryshme, por megjithat\u00eb, duhet t\u00eb jet\u00eb e mundur t\u00eb b\u00ebhet zhvillimi lokal leht\u00ebsisht me skedar\u00eb t\u00eb instaluar.<\/p>\n

Hapi tjet\u00ebr p\u00ebr ne \u00ebsht\u00eb t\u00eb investojm\u00eb thell\u00eb n\u00eb komfortin e zhvilluesve.<\/b>. Q\u00eb me nj\u00eb mjet t\u00eb vet\u00ebm t\u00eb ngrem\u00eb shpejt nj\u00eb projekt lokal, t\u00eb zhvillojm\u00eb, t\u00eb shtypim n\u00eb Git, dhe ai gjithashtu do t\u00eb p\u00ebrfundoj\u00eb n\u00eb stage ose n\u00eb teste, var\u00ebsisht nga pipeline-t, dhe pastaj me t\u00eb nj\u00ebjtin mjet t\u00eb shkojm\u00eb n\u00eb prodhim. Ky unitet, unifikimi, p\u00ebrmbushshm\u00ebria e infrastruktur\u00ebs nga mjedisi lokal n\u00eb prodhim \u00ebsht\u00eb nj\u00eb pik\u00eb shum\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ne. Por p\u00ebr momentin, kjo nuk ekziston n\u00eb werf - vet\u00ebm e planifikojm\u00eb.<\/p>\n

Por rruga p\u00ebr dapp\/werf ka qen\u00eb gjithmon\u00eb e ngjashme me at\u00eb t\u00eb Kubernetes n\u00eb fillim. Ne u p\u00ebrball\u00ebm me probleme, i zgjidh\u00ebm ato me m\u00ebnyra t\u00eb drejta - shpik\u00ebm disa zgjidhje p\u00ebr vete mbi shell, mbi \u00e7far\u00ebdo q\u00eb t\u00eb ishte. M\u00eb pas, p\u00ebrpiqeshim t'i shkurtojm\u00eb, t'i p\u00ebrmbledhim dhe t'i konsolidonim ato n\u00eb binar\u00eb n\u00eb k\u00ebt\u00eb rast, t\u00eb cilat thjesht i ndajm\u00eb.<\/p>\n

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

Kubernetes \u00ebsht\u00eb si korniza e nj\u00eb makine me motor. S'ka dyer, xhama, radio, aromatizues - nuk ka asgj\u00eb. Vet\u00ebm korniz\u00eb dhe motor. Dhe ka Helm - ky \u00ebsht\u00eb timoni. Super, ka timon, por na nevojiten edhe buksi i timonit, sistemi i timonit, kutia e shpejt\u00ebsis\u00eb dhe rrotat, pa to nuk shkon.<\/p><\/blockquote>\n

\nN\u00eb rastin e werf - \u00ebsht\u00eb nj\u00eb komponent tjet\u00ebr p\u00ebr Kubernetes. Por tani ne kemi nj\u00eb version alfa t\u00eb werf, p\u00ebr shembull, Helm kompiluar brenda werf, sepse na ka bezdisur ta b\u00ebjm\u00eb at\u00eb vet\u00eb. Shum\u00eb arsye p\u00ebr ta b\u00ebr\u00eb k\u00ebt\u00eb, detajisht p\u00ebr arsyet pse e kemi kompiluar helm t\u00ebr\u00ebsisht me tiller brenda werf, do ta tregoj n\u00eb raportin n\u00eb RIT++.<\/a><\/noindex>.<\/p>\n

Tani tani werf \u00ebsht\u00eb nj\u00eb komponent m\u00eb i integruar. Ne po marrim nj\u00eb timon t\u00eb gatsh\u00ebm, nj\u00eb pin timoni - nuk e kam shum\u00eb iden\u00eb p\u00ebr makinat, por kjo \u00ebsht\u00eb nj\u00eb bllok i madh q\u00eb zgjidh nj\u00eb gam\u00eb t\u00eb madhe t\u00eb detyrave. Nuk \u00ebsht\u00eb e nevojshme t\u00eb shfletojm\u00eb katalogun vet\u00eb, t\u00eb kemi nj\u00eb pjes\u00eb te tjera, t\u00eb mendojm\u00eb si t'i bashkojm\u00eb ato. Ne po marrim nj\u00eb kombajna t\u00eb gatsh\u00ebm q\u00eb zgjidh nj\u00eb grup t\u00eb madh detyrash menj\u00ebher\u00eb. Por brenda, gjith\u00e7ka \u00ebsht\u00eb nd\u00ebrtuar nga ato komponent\u00eb open source, gjithashtu p\u00ebrdor Docker p\u00ebr nd\u00ebrtim, Helm p\u00ebr pjes\u00ebn e funksionalitetit, dhe ka disa bibliotekat t\u00eb tjera. Ky \u00ebsht\u00eb nj\u00eb instrument i integruar p\u00ebr t\u00eb marr\u00eb shpejt dhe leht\u00ebsisht CI\/CD t\u00eb shk\u00eblqyese nga kutia.<\/p>\n

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

\n\u2014 Ti po flet p\u00ebr p\u00ebrvoj\u00ebn, se si keni filluar t\u00eb p\u00ebrdorni Kubernetes, kjo \u00ebsht\u00eb p\u00ebr ju nj\u00eb korniz\u00eb, nj\u00eb motor, dhe se mund t\u00eb jet\u00eb shum\u00eb gj\u00ebra t\u00eb ndryshme: nj\u00eb trup, nj\u00eb timon, t\u00eb lidh\u00ebsh pedalet, ul\u00ebset. Shfaqet pyetja - sa e v\u00ebshtir\u00eb \u00ebsht\u00eb p\u00ebr ju mb\u00ebshtetje Kubernetes? Keni nj\u00eb p\u00ebrvoj\u00eb t\u00eb pasur, sa koh\u00eb dhe burime ju duhen p\u00ebr mb\u00ebshtetje Kubernetes n\u00eb ndarje nga t\u00eb gjitha t\u00eb tjerat?<\/b><\/p>\n

Dmitri<\/b>: Kjo \u00ebsht\u00eb nj\u00eb pyetje shum\u00eb e nd\u00ebrlikuar dhe p\u00ebr t\u00eb p\u00ebrgjigjur, duhen kuptuar \u00e7far\u00eb do t\u00eb thot\u00eb mb\u00ebshtetje dhe \u00e7far\u00eb duam nga Kubernetes. Ndoshta ti do ta sqarohet?<\/p>\n

\u2014 Sa di un\u00eb dhe si\u00e7 shoh, tani shum\u00eb ekipe d\u00ebshirojn\u00eb t\u00eb provoj\u00eb Kubernetes. T\u00eb gjith\u00eb po e provojn\u00eb, e instalojn\u00eb n\u00eb m\u00ebnyr\u00eb ad hoc. Kam ndjesin\u00eb se njer\u00ebzit nuk e kuptojn\u00eb gjithmon\u00eb kompleksitetin e k\u00ebtij sistemi.<\/b><\/p>\n

Dmitri<\/b>: E v\u00ebrtet\u00eb.<\/p>\n

\u2014 Sa e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb marr\u00ebsh dhe t\u00eb instalosh Kubernetes nga zero, n\u00eb m\u00ebnyr\u00eb 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, pyetje e ndjeshme. T\u00eb p\u00ebrdor\u00ebsh nj\u00eb thik\u00eb kirurgjikale dhe t\u00eb mos gabosh \u2014 nuk \u00ebsht\u00eb aq e v\u00ebshtir\u00eb. N\u00ebse t\u00eb japin udh\u00ebzime se ku t\u00eb prer\u00eb dhe ku t\u00eb qep\u00ebsh, at\u00ebher\u00eb procedura vet\u00eb nuk \u00ebsht\u00eb e komplikuar. E v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb garantosh q\u00eb gjith\u00e7ka do t\u00eb shkoj\u00eb si\u00e7 duhet nga nj\u00eb her\u00eb n\u00eb tjetr\u00ebn.<\/p>\n

T\u00eb instalosh Kubernetes dhe ta b\u00ebsh ta punoj\u00eb leht\u00eb: cick! \u2014 u instalua, ka shum\u00eb m\u00ebnyra p\u00ebr ta instaluar. Por \u00e7far\u00eb do t\u00eb ndodh\u00eb kur t\u00eb shfaqen problemet?<\/p><\/blockquote>\n

\nGjithmon\u00eb shfaqen pyetje - \u00e7far\u00eb nuk kemi marr\u00eb parasysh? \u00c7far\u00eb nuk kemi b\u00ebr\u00eb? Cilat parametra t\u00eb kernelit Linux kemi specifikuar gabimisht? Zoti, a i kemi specifikuar ne gjithsesi?! Cil\u00ebt komponent\u00eb Kubernetes kemi instaluar, dhe cil\u00ebt jo? Shfaqen mij\u00ebra pyetje, dhe p\u00ebr t'u p\u00ebrgjigjur n\u00eb to, nevojitet 15-20 vjet p\u00ebrvoj\u00eb n\u00eb k\u00ebt\u00eb industri.<\/p>\n

Kam kam nj\u00eb shembull t\u00eb fresk\u00ebt mbi k\u00ebt\u00eb tem\u00eb, i cili mund t\u00eb zbuloj\u00eb kuptimin e problemit \"A \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb mbash Kubernetes?\" Nj\u00eb koh\u00eb m\u00eb par\u00eb ne e shqyrtuam me seriozitet mund\u00ebsin\u00eb e implementimit t\u00eb Cilium si rrjet n\u00eb Kubernetes.<\/p>\n

Le t\u00eb shpjegoj se \u00e7far\u00eb \u00ebsht\u00eb Cilium. N\u00eb Kubernetes ka shum\u00eb realizime t\u00eb ndryshme t\u00eb sistemit t\u00eb rrjetit, dhe nj\u00eb nga ato \u00ebsht\u00eb shum\u00eb e shk\u00eblqyer - kjo \u00ebsht\u00eb Cilium. \u00c7far\u00eb e b\u00ebn at\u00eb t\u00eb ve\u00e7ant\u00eb? N\u00eb b\u00ebrtham\u00ebn e sistemit, nj\u00eb koh\u00eb m\u00eb par\u00eb u shfaq mund\u00ebsia p\u00ebr t\u00eb shkruar kapak\u00eb p\u00ebr b\u00ebrtham\u00ebn, t\u00eb cilat n\u00eb nj\u00eb m\u00ebnyr\u00eb ose n\u00eb nj\u00eb tjet\u00ebr nd\u00ebrhyjn\u00eb n\u00eb sistemin e rrjetit dhe n\u00eb shum\u00eb sisteme t\u00eb tjera, duke lejuar kalimin e pjes\u00ebve t\u00eb m\u00ebdha n\u00eb b\u00ebrtham\u00eb.<\/p>\n

N\u00eb b\u00ebrtham\u00ebn e Linux-it historikisht ka ip rout, filtra, bridge dhe shum\u00eb komponente t\u00eb tjera t\u00eb vjetra, t\u00eb cilat kan\u00eb 15, 20, ose madje 30 vjet. N\u00eb t\u00ebr\u00ebsi ato funksionojn\u00eb, gjith\u00e7ka \u00ebsht\u00eb super, por tani kemi shtuar nj\u00eb shum\u00ebllojshm\u00ebri container\u00ebsh, dhe kjo duket si nj\u00eb kulla prej 15 kockash nj\u00eb mbi tjetr\u00ebn, nd\u00ebrsa ti q\u00ebndron mbi t\u00eb me nj\u00eb k\u00ebmb\u00eb - nj\u00eb ndjenj\u00eb e \u00e7uditshme. Ky sistem ka evoluar 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 fantastik dhe mund\u00ebsin\u00eb p\u00ebr t\u00eb shkruar kapak\u00eb p\u00ebr b\u00ebrtham\u00ebn - djemt\u00eb kan\u00eb shkruar kapak\u00ebt e tyre p\u00ebr b\u00ebrtham\u00ebn. Pakoja arrin n\u00eb b\u00ebrtham\u00ebn Linux, ata e nxjerrin at\u00eb direkt n\u00eb hyrje, e trajtojn\u00eb vet\u00eb si\u00e7 duhet pa bridge, pa TCP, pa IP-steck - p\u00ebr ta th\u00ebn\u00eb shkurt, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb kalojn\u00eb gjith\u00e7ka q\u00eb \u00ebsht\u00eb shkruar n\u00eb b\u00ebrtham\u00ebn Linux, dhe menj\u00ebher\u00eb e nxjerrin n\u00eb container.<\/p>\n

\u00c7far\u00eb doli? Performanc\u00eb shum\u00eb e shk\u00eblqyer, ve\u00e7ori t\u00eb shk\u00eblqyera - thjesht e shk\u00eblqyer! Por ne e shikojm\u00eb k\u00ebt\u00eb dhe shohim se n\u00eb \u00e7do makin\u00eb ka nj\u00eb program q\u00eb lidhet me API-n\u00eb e Kubernetes dhe mbi t\u00eb dh\u00ebnat q\u00eb merr nga ky API, gjeneron kod C dhe kompilon binar\u00ebt q\u00eb i ngarkon n\u00eb b\u00ebrtham\u00eb, n\u00eb m\u00ebnyr\u00eb q\u00eb k\u00ebto kapak\u00eb t\u00eb funksionojn\u00eb n\u00eb hap\u00ebsir\u00ebn e b\u00ebrtham\u00ebs.<\/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 lexojm\u00eb t\u00eb gjith\u00eb k\u00ebt\u00eb kod, t\u00eb kuptojm\u00eb gjith\u00eb logjik\u00ebn, dhe kjo \u00ebsht\u00eb shum\u00eb e komplikuar. Por, nga ana tjet\u00ebr, ka k\u00ebto bridge, filtra rrjeti, ip rout - un\u00eb nuk kam lexuar burimin e tyre, as 40 inxhinier\u00ebt q\u00eb punojn\u00eb n\u00eb kompanin\u00eb ton\u00eb. Ndoshta disa fragmente i kuptojn\u00eb vet\u00ebm disa.<\/p>\n

Dhe \u00e7far\u00eb ndryshimi ka? K\u00ebshtu q\u00eb kemi ip rout, b\u00ebrtham\u00ebn Linux, dhe kemi nj\u00eb mjet t\u00eb ri - \u00e7far\u00eb ndryshimi, nuk kuptojm\u00eb asnj\u00eb, as tjetrin. Por kemi frik\u00eb t\u00eb p\u00ebrdorim t\u00eb rejat - pse? Sepse n\u00ebse mjeti ka 30 vjet, gjat\u00eb k\u00ebtyre 30 vjet\u00ebve jan\u00eb gjetur t\u00eb gjitha gabimet, kan\u00eb trokitur mbi t\u00eb gjitha pengesat dhe nuk \u00ebsht\u00eb e nevojshme t\u00eb dish p\u00ebr gjith\u00e7ka - funksionon, si nj\u00eb kuti e zez\u00eb, dhe funksionon gjithmon\u00eb. T\u00eb gjith\u00eb e din\u00eb se ku t\u00eb fusin nj\u00eb drejtk\u00ebnd\u00ebsh diagnostikues, cili tcpdump t\u00eb aktivizohet n\u00eb momentin e duhur. T\u00eb gjith\u00eb i njohin mir\u00eb mjetet diagnostikuese dhe kuptojn\u00eb si funksionon ky grup komponent\u00ebsh n\u00eb b\u00ebrtham\u00ebn Linux - jo si \u00ebsht\u00eb nd\u00ebrtuar, por si t\u00eb p\u00ebrdoret ai.<\/p>\n

Por Cilium i mrekulluesh\u00ebm nuk \u00ebsht\u00eb 30 vje\u00e7, ai nuk \u00ebsht\u00eb akoma p\u00ebrfunduar. Problemi \u00ebsht\u00eb i nj\u00ebjt\u00eb me Kubernetes, \u00ebsht\u00eb nj\u00eb kopje. Si Cilium instalohet shk\u00eblqyesh\u00ebm, ashtu edhe Kubernetes instalohet shk\u00eblqyesh\u00ebm, por kur di\u00e7ka nuk shkon n\u00eb prodhim, jeni t\u00eb aft\u00eb ta kuptoni shpejt \u00e7far\u00eb shkoi keq n\u00eb nj\u00eb situat\u00eb kritike? <\/p>\n

Kur flasim p\u00ebr sa e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb mbash Kubernetes - jo, \u00ebsht\u00eb shum\u00eb e thjesht\u00eb, dhe po, \u00ebsht\u00eb jasht\u00ebzakonisht e v\u00ebshtir\u00eb. Kubernetes funksionon shk\u00eblqyer vetvetiu, por me nj\u00eb miliard nuanca.<\/p><\/blockquote>\n

<\/p>\n

P\u00ebr qasjen \"M\u00eb p\u00eblqen fatin\"<\/h2>\n

\n- A ka kompani ku k\u00ebto nuanca do t\u00eb shfaqen pothuajse garantuar? Le t\u00eb supozojm\u00eb se Yandex papritmas kalon t\u00eb gjitha sh\u00ebrbimet n\u00eb Kubernetes, atje do t\u00eb ket\u00eb nj\u00eb ngarkes\u00eb t\u00eb madhe.<\/b><\/p>\n

Dmitri<\/b>: Jo, kjo 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 n\u00ebse po funksionon? Nuk ka nj\u00eb mjet t\u00eb gatsh\u00ebm p\u00ebr t\u00eb kuptuar q\u00eb aplikacioni nuk bie, thjesht nuk ekziston. Nuk ka nj\u00eb sistem t\u00eb gatsh\u00ebm q\u00eb t\u00eb d\u00ebrgoj\u00eb alarmin - duhet t\u00eb konfiguroni k\u00ebto alarme dhe \u00e7do grafik. Dhe ne po p\u00ebrdit\u00ebsojm\u00eb Kubernetes.<\/p>\n

Ka Ubuntu 16.04. Mund t\u00eb thuhet se kjo \u00ebsht\u00eb nj\u00eb version i vjet\u00ebr, por ne ende jemi mbi t\u00eb, sepse ka LTS. Atje ka systemd, dhe nuanca e tij \u00ebsht\u00eb se ai nuk pastron grupet C. Kubernetes nis pod-et, krijon grupe C, pastaj i heq pod-et, dhe ndodhin disa gj\u00ebra \u2013 nuk e mbaj mend n\u00eb detaje, m\u00eb falni \u2013 q\u00eb mbeten slices t\u00eb systemd. Kjo \u00e7on n\u00eb faktin se me kalimin e koh\u00ebs \u00e7do makin\u00eb fillon t\u00eb ngadal\u00ebsohet shum\u00eb. Kjo nuk \u00ebsht\u00eb as nj\u00eb \u00e7\u00ebshtje mbi highload. N\u00ebse nisen pod-et e vazhdueshme, p\u00ebr shembull, n\u00ebse ka nj\u00eb Cron Job q\u00eb vazhdimisht gjeneron pod-e, at\u00ebher\u00eb makina me Ubuntu 16.04 pas nj\u00eb jave do t\u00eb filloj\u00eb t\u00eb ngadal\u00ebsohet. Do t\u00eb ket\u00eb vazhdimisht nj\u00eb load average t\u00eb lart\u00eb p\u00ebr shkak t\u00eb krijimit t\u00eb shum\u00eb grupeve C. Kjo \u00ebsht\u00eb nj\u00eb problem me t\u00eb cilin p\u00ebrballet secili q\u00eb thjesht instalon Ubuntu 16 dhe vendos Kubernetes mbi t\u00eb.<\/p>\n

L\u00eb t\u00eb themi se ai ndonj\u00ebher\u00eb do ta p\u00ebrdit\u00ebsoj\u00eb systemd ose di\u00e7ka tjet\u00ebr, por n\u00eb b\u00ebrtham\u00ebn Linux deri n\u00eb versionin 4.16 \u00ebsht\u00eb akoma m\u00eb qesharake \u2013 kur hiqen grupet C, ato rrjedhin n\u00eb b\u00ebrtham\u00eb dhe faktikisht nuk largohen. Pra, pas nj\u00eb muaji pune n\u00eb k\u00ebt\u00eb makin\u00eb do t\u00eb jet\u00eb e pamundur t\u00eb shikosh statistikat e memories p\u00ebr pod-et. Ne nxjerrim nj\u00eb skedar, e rrotullojm\u00eb n\u00eb program, dhe nj\u00eb skedar rrotullohet p\u00ebr 15 sekonda, sepse b\u00ebrthama llogarit p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb brenda nj\u00eb milioni grupeve C, q\u00eb duket se jan\u00eb hequr, por jo \u2013 ato vazhdojn\u00eb t\u00eb rrjedhin.<\/p>\n

Ka shum\u00eb detaje t\u00eb tilla ende k\u00ebtu dhe atje. Kjo nuk \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje q\u00eb kompanit\u00eb gjigante mund t\u00eb p\u00ebrballen her\u00eb pas here n\u00eb ngarkesa shum\u00eb t\u00eb m\u00ebdha \u2013 jo, kjo \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje e p\u00ebrditshme. Njer\u00ebzit mund t\u00eb jetojn\u00eb k\u00ebshtu p\u00ebr muaj me radh\u00eb \u2013 vendos\u00ebn Kubernetes, vendos\u00ebn aplikacionin \u2013 duket se punon. M\u00eb shum\u00eb se shum\u00eb \u00ebsht\u00eb n\u00eb rregull. P\u00ebr faktin se ndonj\u00ebher\u00eb ky aplikacion ndonj\u00ebher\u00eb do t\u00eb bjer\u00eb, ata as nuk do ta din\u00eb, alerthi nuk do t\u00eb vij\u00eb, por p\u00ebr ta kjo \u00ebsht\u00eb normale. M\u00eb par\u00eb jetonin n\u00eb virtuale pa monitorim, tani u transferuan n\u00eb Kubernetes gjithashtu pa monitorim \u2013 \u00e7far\u00eb r\u00ebnd\u00ebsie ka?<\/p>\n

\u00c7\u00ebshtja \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 ecin dhe nuk shqet\u00ebsohen, sepse edhe m\u00eb par\u00eb kan\u00eb ecur.<\/p>\n

Nga pik\u00ebpamja ime, nuanca dhe kompleksiteti i eksploitimit t\u00eb \u00e7do sistemi \u00ebsht\u00eb se p\u00ebr t\u00eb garantuar q\u00eb trash\u00ebsia e akullit \u00ebsht\u00eb mjaft e mjaftueshme p\u00ebr t\u00eb zgjidhur detyrat tona. B\u00ebhet fjal\u00eb p\u00ebr k\u00ebt\u00eb.<\/p><\/blockquote>\n

\nN\u00eb IT, m\u00eb duket se ka shum\u00eb qasje t\u00eb stilit \"M\u00eb ka r\u00ebn\u00eb fatit\". Shum\u00eb vendosin software, p\u00ebrdorin biblioteka programore n\u00eb shpres\u00eb se do t'u ndodhi ndonj\u00eb fat. N\u00eb p\u00ebrgjith\u00ebsi, fatin e ka shum\u00eb njer\u00ebz. Ndoshta p\u00ebr k\u00ebt\u00eb arsye 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 nevojitet mb\u00ebshtetje nga \"Flant\", ndoshta nga Red Hat, ose k\u00ebrkohet nj\u00eb ekip i brendsh\u00ebm i dedikuar posa\u00e7\u00ebrisht p\u00ebr Kubernetes, i gatsh\u00ebm ta mbaj\u00eb at\u00eb.<\/b><\/p>\n

Dmitri<\/b>: Objekivisht, kjo \u00ebsht\u00eb e v\u00ebrtet\u00eb. T\u00eb futesh vet\u00eb n\u00eb histori me Kubernetes nga nj\u00eb ekip i vog\u00ebl - \u00ebsht\u00eb nj\u00eb sasi e caktuar rreziqesh.<\/p>\n

A na duhen konteiner\u00eb?<\/h2>\n

\n\u2014 A mund t\u00eb tregosh, sa i 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 dikush i ka ato. Ne flasim: \"Kubernetes, Kubernetes\", por ka nj\u00eb k\u00ebndv\u00ebshtrim tjet\u00ebr p\u00ebr k\u00ebt\u00eb \u00e7\u00ebshtje. Sa t\u00eb p\u00ebrhapura jan\u00eb konteiner\u00ebt, as k\u00ebt\u00eb nuk e di, por e di nj\u00eb shif\u00ebr nga raportet n\u00eb internet, q\u00eb 70% e konteiner\u00ebve orkestrohen nga Kubernetes. Ky ishte nj\u00eb burim i besuesh\u00ebm me nj\u00eb mostr\u00eb t\u00eb mjaftueshme nga bota.<\/p>\n

Pastaj, nj\u00eb pyetje tjet\u00ebr - a na duhen konteiner\u00eb?<\/b> Kam nj\u00eb ndjesi 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 ndryshues i loj\u00ebs absolute n\u00eb fush\u00ebn e menaxhimit t\u00eb infrastruktur\u00ebs. Thjesht absolut - asgj\u00eb m\u00eb shum\u00eb nga Ansible, Chef, makinat virtuale, Terraform. Nuk po flas p\u00ebr metodat e vjetra kolhoze. Kubernetes \u00ebsht\u00eb nj\u00eb ndryshues absolut i loj\u00ebs<\/b>, dhe tani do t\u00eb jet\u00eb vet\u00ebm k\u00ebshtu.<\/p>\n

\u00ebsht\u00eb e qart\u00eb se disa njer\u00ebz u duhet disa vite, ndonj\u00ebher\u00eb disa dhjet\u00ebra, q\u00eb ta kuptojn\u00eb k\u00ebt\u00eb. Nuk kam dyshime se nuk do t\u00eb ket\u00eb asgj\u00eb tjet\u00ebr p\u00ebrve\u00e7 Kubernetes dhe k\u00ebtij k\u00ebndv\u00ebshtrimi t\u00eb ri: nuk e l\u00ebndojm\u00eb m\u00eb operativin, por e p\u00ebrdorim infrastructure as code<\/b>, por 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 Pra, ato kompani q\u00eb ende nuk kan\u00eb kaluar n\u00eb Kubernetes, do t\u00eb kalojn\u00eb patjet\u00ebr n\u00eb t\u00eb ose do t\u00eb mbeten n\u00eb harres\u00eb. E kam kuptuar sakt\u00eb?<\/b><\/p>\n

Dmitri<\/b>: Kjo gjithashtu nuk \u00ebsht\u00eb krejt\u00ebsisht e sakt\u00eb. P\u00ebr shembull, n\u00ebse kemi si detyr\u00eb t\u00eb nisim nj\u00eb server dns, at\u00ebher\u00eb mund ta nisim at\u00eb n\u00eb FreeBSD 4.10 dhe ai mund t\u00eb funksionoj\u00eb shk\u00eblqyesh\u00ebm p\u00ebr 20 vjet. Thjesht t\u00eb funksionoj\u00eb dhe kaq. Ka mund\u00ebsi q\u00eb pas 20 vjet\u00ebsh t\u00eb jet\u00eb e nevojshme ta p\u00ebrmir\u00ebsojm\u00eb nj\u00eb her\u00eb. N\u00ebse flasim p\u00ebr softuer n\u00eb formatin se ne e nisim dhe ai v\u00ebrtet funksionon shum\u00eb vite pa ndonj\u00eb p\u00ebrmir\u00ebsim, pa b\u00ebr\u00eb ndryshime, at\u00ebher\u00eb natyrisht nuk do t\u00eb ket\u00eb Kubernetes. Ai atje nuk \u00ebsht\u00eb i nevojsh\u00ebm.<\/p>\n

Gjith\u00e7ka q\u00eb ka t\u00eb b\u00ebj\u00eb me CI\/CD \u2014 kudo ku nevojitet Continuous Delivery, ku k\u00ebrkohet t\u00eb p\u00ebrdit\u00ebsohen versionet, t\u00eb b\u00ebhen ndryshime aktive, kudo ku \u00ebsht\u00eb e nevojshme t\u00eb krijohet q\u00ebndrueshm\u00ebri \u2014 vet\u00ebm Kubernetes.<\/p><\/blockquote>\n

<\/p>\n

P\u00ebr mikroshedhjet<\/h2>\n

\n\u2014 K\u00ebtu m\u00eb lind nj\u00eb disonanc\u00eb t\u00eb vog\u00ebl. P\u00ebr t\u00eb punuar me Kubernetes, nevojitet mb\u00ebshtetje e jashtme ose t\u00eb brendshme \u2014 ky \u00ebsht\u00eb momenti i par\u00eb. I dyti \u2014 kur ne sapo fillojm\u00eb zhvillimin, jemi nj\u00eb startup t\u00eb vog\u00ebl, nuk kemi asgj\u00eb, zhvillimi n\u00ebn Kubernetes ose n\u00ebn nj\u00eb arkitektur\u00eb mikroshedhjesh mund t\u00eb jet\u00eb i komplikuar, dhe nuk gjithmon\u00eb \u00ebsht\u00eb i justifikuar ekonomikisht. M\u00eb intereson mendimi yt \u2014 duhet q\u00eb startupet q\u00eb nisin nga zero t\u00eb fillojn\u00eb menj\u00ebher\u00eb t\u00eb shkruajn\u00eb n\u00ebn Kubernetes apo mund t\u00eb shkruajn\u00eb fillimisht nj\u00eb monolit dhe m\u00eb pas t\u00eb kalojn\u00eb n\u00eb Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: Pyetje emocionuese. Kam nj\u00eb referat p\u00ebr mikroshedhjet \u00abMikroshedhjet: madh\u00ebsia ka r\u00ebnd\u00ebsi\u00bb.<\/a><\/noindex> Shum\u00eb her\u00eb jam p\u00ebrballur me faktin se njer\u00ebzit p\u00ebrpiqen t\u00eb godasin petka me nj\u00eb mikroskop. Vet\u00eb qasja \u00ebsht\u00eb e sakt\u00eb, ne projektuam brendsh\u00ebm softin ton\u00eb pik\u00ebrisht n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb. Por kur e b\u00ebn k\u00ebt\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb kuptosh qart\u00eb se \u00e7far\u00eb po b\u00ebn. M\u00eb shum\u00eb se gjith\u00e7ka n\u00eb mikroshedhje, urrej fjal\u00ebn \u00abmikro\u00bb. Historikisht \u00ebsht\u00eb krijuar kjo fjal\u00eb, dhe ndonj\u00eb m\u00ebnyr\u00eb njer\u00ebzit mendojn\u00eb se mikro do t\u00eb thot\u00eb shum\u00eb i vog\u00ebl, m\u00eb i vog\u00ebl se nj\u00eb milimet\u00ebr, si mikrometri. Nuk \u00ebsht\u00eb k\u00ebshtu.<\/p>\n

P\u00ebr shembull, ekziston nj\u00eb monolit, q\u00eb shkruhet nga 300 njer\u00ebz, dhe t\u00eb gjith\u00eb ata q\u00eb mor\u00ebn pjes\u00eb n\u00eb zhvillim e din\u00eb se n\u00eb at\u00eb ka probleme, dhe duhet q\u00eb t\u00eb ndahet n\u00eb copa mikro \u2014 rreth 10, \u00e7do nj\u00eb prej t\u00eb cilave shkruhen nga 30 njer\u00ebz n\u00eb variantin minimal. Kjo \u00ebsht\u00eb e r\u00ebnd\u00ebsishme, e nevojshme dhe e shk\u00eblqyer. Por kur vjen nj\u00eb startup te ne, ku 3 djem shum\u00eb t\u00eb zot\u00eb dhe t\u00eb talentuar kan\u00eb shkruar mbi gjak n\u00eb 60 mikroshedhje, \u00e7do her\u00eb un\u00eb k\u00ebrkoj Corvalol.<\/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 form\u00ebn e tij t\u00eb ndryshme. Kjo \u00ebsht\u00eb ekonomikisht e paarsyeshme, shum\u00eb e komplikuar n\u00eb p\u00ebrgjith\u00ebsi. Thjesht kam par\u00eb kaq shum\u00eb her\u00eb k\u00ebt\u00eb, sa q\u00eb m\u00eb b\u00ebn dhimbje, prandaj vazhdoj ta diskutoj.<\/p>\n

N\u00eb lidhje me pyetjen fillestare, ekziston nj\u00eb konflikt mes faktit q\u00eb, nga nj\u00ebra an\u00eb, Kubernetes \u00ebsht\u00eb shum\u00eb i friksh\u00ebm p\u00ebr t'u p\u00ebrdorur, sepse nuk e di se \u00e7far\u00eb mund t\u00eb prish\u00eb ose t\u00eb mos funksionoj\u00eb, dhe nga ana tjet\u00ebr, \u00ebsht\u00eb e qart\u00eb se t\u00eb gjith\u00eb po shkojn\u00eb drejt k\u00ebtij sistemi dhe nuk do t\u00eb ket\u00eb asgj\u00eb tjet\u00ebr p\u00ebrve\u00e7 Kubernetes. P\u00ebrgjigjia \u00ebsht\u00eb \u2014 t\u00eb peshohet sasia e p\u00ebrfitimit q\u00eb vjen, volumet e detyrave q\u00eb mund t\u00eb zgjidhni<\/b>. Kjo \u00ebsht\u00eb nga nj\u00ebra an\u00eb e pesh\u00ebs. Nga ana tjet\u00ebr \u2014 rreziqet q\u00eb lidhen me ndalimin e pun\u00ebs 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

K\u00ebtu \u00ebsht\u00eb k\u00ebshtu \u2014 ose ne l\u00ebvizim shpejt, dhe Kubernetes lejon t\u00eb realizohen shum\u00eb gj\u00ebra m\u00eb shpejt dhe m\u00eb mir\u00eb, ose p\u00ebrdorim zgjidhje t\u00eb besueshme, t\u00eb provuara me kalimin e koh\u00ebs, por l\u00ebvizim shum\u00eb m\u00eb ngadal\u00eb. Kjo zgjedhje duhet ta b\u00ebj\u00eb secila kompani. Mund ta shqyrtoni k\u00ebt\u00eb si nj\u00eb shtigje n\u00eb xhungla \u2014 kur e kaloni her\u00ebn e par\u00eb, mund t\u00eb takoni nj\u00eb gjarp\u00ebr, nj\u00eb tig\u00ebr ose nj\u00eb lloj matoshi t\u00eb \u00e7mendur, dhe kur e kaloni 10 her\u00eb \u2014 keni hapur nj\u00eb shtigje, hequr deg\u00ebt dhe e b\u00ebni m\u00eb t\u00eb leht\u00eb kalimin. Me \u00e7do her\u00eb, shtigji b\u00ebhet m\u00eb i gjer\u00eb. M\u00eb pas \u00ebsht\u00eb nj\u00eb rrug\u00eb e asfaltuar, e m\u00eb von\u00eb nj\u00eb bulevard i bukur.<\/p>\n

Kubernetes nuk q\u00ebndron n\u00eb vend. P\u00ebrs\u00ebri pyetje: Kubernetes, nga nj\u00ebra an\u00eb, \u00ebsht\u00eb 4-5 binar\u00eb, nga ana tjet\u00ebr \u2014 \u00ebsht\u00eb e gjith\u00eb ekosistemi. Kjo \u00ebsht\u00eb nj\u00eb sistem operativ q\u00eb kemi n\u00eb makinat tona. \u00c7far\u00eb \u00ebsht\u00eb? Ubuntu apo Curios? Kjo \u00ebsht\u00eb b\u00ebrthama Linux, nj\u00eb many komponent\u00ebsh shtes\u00eb. T\u00eb gjitha k\u00ebto gj\u00ebra k\u00ebtu kan\u00eb hequr nj\u00eb gjarp\u00ebr helmues nga rruga, atje kan\u00eb v\u00ebn\u00eb nj\u00eb gardh. Kubernetes zhvillohet shum\u00eb shpejt dhe dinamikisht, dhe sasia e rreziqeve, sasia e t\u00eb panjohurave me \u00e7do muaj po ulet dhe, p\u00ebr pasoj\u00eb, k\u00ebto peshore p\u00ebrs\u00ebri balancohen.<\/p>\n

Duke p\u00ebrgjigje pyetjes, \u00e7far\u00eb t\u00eb b\u00ebj\u00eb nj\u00eb startup, do t\u00eb thosha - ejani te \"Flant\", paguani 150 mij\u00eb rubla dhe merrni sh\u00ebrbimin 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 duhet t\u00eb m\u00ebsoj\u00eb p\u00ebr t\u00eb zgjidhur problemet tuaja dhe t\u00eb paguani gjat\u00eb k\u00ebtij koh\u00eb rrog\u00ebn, do t\u00eb merrni zgjidhjen e t\u00eb gjitha \u00e7\u00ebshtjeve me \u00e7el\u00ebs n\u00eb dor\u00eb. Po, ka disa disavantazhe. Ne, si outsourcer, nuk mund t\u00eb jemi kaq t\u00eb angazhuar dhe t\u00eb reagojm\u00eb shpejt ndaj ndryshimeve. Por kemi shum\u00eb ekspertiz\u00eb, praktika t\u00eb gatshme. Garantojm\u00eb q\u00eb n\u00eb \u00e7do situat\u00eb do ta zgjidhim me siguri dhe shpejt dhe do ta nxjerrim \u00e7far\u00ebdo Kubernetes nga k\u00ebt\u00eb bot\u00eb. <\/p>\n

Un\u00eb kategorikisht rekomandoj outsourcing p\u00ebr startup-et dhe bizneset e pjekura deri n\u00eb madh\u00ebsin\u00eb kur mund t\u00eb dedikoni nj\u00eb ekip prej 10 personash p\u00ebr operacionin, sepse ndryshe nuk ka kuptim. Ka kuptim t\u00ebr\u00ebsisht q\u00eb t\u00eb b\u00ebni outsourcing.<\/p><\/blockquote>\n

<\/p>\n

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

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

Dmitri<\/b>: Po, sigurisht, kjo zgjidh disa \u00e7\u00ebshtje. Por p\u00ebrs\u00ebri ka nuanca. S\u00ebrish duhet t\u00eb kuptoni se si ta p\u00ebrdorni. P\u00ebr shembull, ka mij\u00ebra detaje n\u00eb funksionimin e Amazon AWS: Load Balancer duhet t\u00eb ngrohet ose paraprakisht t\u00eb shkruani nj\u00eb k\u00ebrkes\u00eb, q\u00eb \"djem, do t\u00eb na vij\u00eb trafik, ngrohni Load Balancer-in ton\u00eb!\" K\u00ebto nuanca duhet t\u2019i dini.<\/p>\n

Kur iu drejtoheni njer\u00ebzve q\u00eb specializohen n\u00eb k\u00ebt\u00eb fush\u00eb, merrni pothuajse t\u00eb gjitha \u00e7\u00ebshtjet tipike t\u00eb mbyllura. Aktualisht kemi 40 inxhinier\u00eb, deri n\u00eb fund t\u00eb vitit ndoshta do t\u00eb jen\u00eb 60 - ne me siguri kemi hasur n\u00eb t\u00eb gjitha k\u00ebto \u00e7\u00ebshtje. Edhe n\u00ebse n\u00eb ndonj\u00eb projekt hasim s\u00ebrish n\u00eb k\u00ebt\u00eb problem, ne tashm\u00eb e pyesim shpejt nj\u00ebri-tjetrin dhe dim\u00eb se si ta zgjidhim.<\/p>\n

Ndoshta, p\u00ebrgjigjja \u00ebsht\u00eb kjo - sigurisht, historia e hostimit leht\u00ebson nj\u00eb pjes\u00eb. Pyetja \u00ebsht\u00eb, a jeni t\u00eb gatsh\u00ebm t\u00eb besoni k\u00ebtyre hostuesve, dhe a do ta zgjidhin ata problemin tuaj. Amazon dhe Google e kan\u00eb provuar veten mir\u00eb. P\u00ebr t\u00eb gjitha rastet tona - me siguri. Ne nuk kemi ndonj\u00eb experienc\u00eb pozitive t\u00eb tjera. T\u00eb gjith\u00eb 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 t\u00eb gjitha llojet e OpenStack n\u00eb realizime t\u00eb ndryshme: Headster, Overage - gjith\u00e7ka q\u00eb d\u00ebshironi. T\u00eb gjitha krijojn\u00eb probleme q\u00eb nuk d\u00ebshirojm\u00eb t\u2019i zgjidhim.<\/p>\n

Prandaj, p\u00ebrgjigjja \u00ebsht\u00eb - po, por, p\u00ebr fakt, zgjidhjet e mature t\u00eb hostimit nuk jan\u00eb shum\u00eb.<\/p>\n

Kush do t\u00eb ket\u00eb nevoj\u00eb p\u00ebr Kubernetes?<\/h2>\n

\n\u2014 E megjithat\u00eb kush do t\u00eb ket\u00eb nevoj\u00eb p\u00ebr Kubernetes? Kush duhet t\u00eb kaloj\u00eb tashm\u00eb n\u00eb Kubernetes, kush \u00ebsht\u00eb klienti tipik i \"Flanta\", i cili vjen p\u00ebr Kubernetes?<\/b><\/p>\n

Dmitri<\/b>: Pyetje interesante, sepse tani pik\u00ebrisht n\u00ebp\u00ebrmjet Kubernetes shum\u00eb njer\u00ebz po vijn\u00eb te ne: \"Djem, e dim\u00eb se ju b\u00ebni Kubernetes, na b\u00ebni nj\u00eb!\". Ne iu p\u00ebrgjigjemi: \"Zot\u00ebrinj, ne nuk b\u00ebjm\u00eb Kubernetes, ne b\u00ebjm\u00eb prodhim dhe gjith\u00e7ka q\u00eb lidhet me t\u00eb\". Sepse t\u00eb b\u00ebsh nj\u00eb prodhim, pa b\u00ebr\u00eb t\u00eb gjith\u00eb CI\/CD-n\u00eb dhe t\u00eb gjith\u00eb k\u00ebt\u00eb histori, n\u00eb dit\u00ebt e sotme \u00ebsht\u00eb thjesht e pamundur. T\u00eb gjith\u00eb kan\u00eb hequr dor\u00eb nga ndarja q\u00eb ne kemi zhvillimin si zhvillim dhe m\u00eb pas shfryt\u00ebzimin si shfryt\u00ebzim.<\/p>\n

Klient\u00ebt tan\u00eb presin gj\u00ebra t\u00eb ndryshme, por t\u00eb gjith\u00eb presin nj\u00ebfar\u00eb mrekullie, se ata kan\u00eb problemet e tyre dhe tani - hop! - Kubernetes do t'i zgjidh\u00eb ato. Njer\u00ebzit besojn\u00eb n\u00eb mrekulli. N\u00eb m\u00ebnyr\u00eb t\u00eb arsyeshme kuptojn\u00eb se nuk do t\u00eb ket\u00eb ndonj\u00eb mrekulli, por me shpirt shpresojn\u00eb - ndoshta ky Kubernetes tani do ta zgjidh\u00eb \u00e7\u00ebshtjen e gjitha, flitet aq shum\u00eb p\u00ebr t\u00eb! Mund t\u00eb ndodh\u00eb q\u00eb ai tani - chih! - dhe nj\u00eb plumb argjendi, chih! - dhe ne kemi 100% uptime, t\u00eb gjith\u00eb zhvilluesit mund t\u00eb publikojn\u00eb \u00e7far\u00ebdo n\u00eb prodhim 50 her\u00eb dhe ai nuk bie. N\u00eb p\u00ebrgjith\u00ebsi, nj\u00eb mrekulli!<\/p>\n

Kur njer\u00ebz t\u00eb till\u00eb vijn\u00eb te ne, ne themi: \"Na falni, por nuk ka mrekulli\". P\u00ebr t\u00eb qen\u00eb t\u00eb sh\u00ebndetsh\u00ebm, duhet t\u00eb ushqehesh mir\u00eb dhe t\u00eb ushtrosh sport. P\u00ebr t\u00eb pasur nj\u00eb prodhim t\u00eb besuesh\u00ebm, duhet t\u00eb b\u00ebsh at\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb besueshme. P\u00ebr t\u00eb pasur nj\u00eb CI\/CD funksionale, duhet ta b\u00ebsh at\u00eb t\u00eb till\u00eb. Kjo \u00ebsht\u00eb shum\u00eb pun\u00eb q\u00eb duhet t\u00eb b\u00ebhet.<\/p>\n

Duke iu p\u00ebrgjigjur pyetjes se kush do t\u00eb ket\u00eb nevoj\u00eb p\u00ebr Kubernetes - 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, kan\u00eb nj\u00eb nevoj\u00eb t\u00eb thell\u00eb p\u00ebr t\u00eb pushuar nga mendimet, angazhimet, dhe shqet\u00ebsimet rreth problemeve t\u00eb infrastruktur\u00ebs dhe problemeve t\u00eb lan\u00e7imit t\u00eb aplikacioneve t\u00eb tyre. Ata duan q\u00eb aplikacionet t\u00eb funksionojn\u00eb thjesht dhe t\u00eb deplojn\u00eb me leht\u00ebsi. P\u00ebr ta, Kubernetes \u00ebsht\u00eb shpresa se do t\u00eb pushonin s\u00eb d\u00ebgjuari histori si \"ne ishim atje\", ose \"nuk mund t\u00eb zhvillohemi\", ose di\u00e7ka tjet\u00ebr.<\/p>\n

Zakonisht te ne vjen nj\u00eb drejtor teknik. Nga ai k\u00ebrkohen dy gj\u00ebra: nga nj\u00ebra an\u00eb, na jepni funksionalitete, nga ana tjet\u00ebr - stabilitet. Ne propozojm\u00eb ta marrim k\u00ebt\u00eb mbi ne dhe ta realizojm\u00eb. Plumbi i argjendt\u00eb, m\u00eb sakt\u00ebsisht, i argjendosur, \u00ebsht\u00eb se do t\u00eb ndaloni s\u00eb menduari p\u00ebr k\u00ebto probleme dhe do t\u00eb kurseni koh\u00eb. Do t\u00eb keni njer\u00ebz t\u00eb ve\u00e7ant\u00eb q\u00eb do t\u00eb zgjidhin k\u00ebt\u00eb \u00e7\u00ebshtje.<\/p>\n

Formulimi q\u00eb na nevojitet Kubernetes ose dikujt tjet\u00ebr \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 g\u00ebrmosh. Le t\u00eb jemi t\u00eb sinqert\u00eb \u2013 t\u00eb gjith\u00eb i duam loj\u00ebrat. T\u00eb gjith\u00eb ndonj\u00ebher\u00eb jemi f\u00ebmij\u00eb, dhe kur shohim nj\u00eb t\u00eb re \u2013 duam ta provojm\u00eb. Disa e kan\u00eb humbur k\u00ebt\u00eb, p\u00ebr shembull n\u00eb administrimin e sistemit, sepse kan\u00eb luajtur mjaftuesh\u00ebm dhe u kan\u00eb ardhur n\u00eb maj\u00eb t\u00eb hund\u00ebs, saq\u00eb thjesht nuk d\u00ebshirojn\u00eb m\u00eb. Sidoqoft\u00eb, kjo nuk \u00ebsht\u00eb krejt\u00ebsisht e humbur p\u00ebr ask\u00ebnd. P\u00ebr shembull, n\u00ebse p\u00ebr mua loj\u00ebrat n\u00eb fush\u00ebn e administrat\u00ebs s\u00eb sistemeve dhe DevOps jan\u00eb b\u00ebr\u00eb t\u00eb m\u00ebrzitshme, akoma i p\u00eblqej loj\u00ebrat dhe gjithmon\u00eb blej disa t\u00eb reja. T\u00eb gjith\u00eb njer\u00ebzit, n\u00eb nj\u00eb m\u00ebnyr\u00eb ose n\u00eb nj\u00eb tjet\u00ebr, gjithmon\u00eb duan disa loj\u00ebra.<\/p>\n

Mos luani me prodhimin. \u00c7far\u00ebdo q\u00eb un\u00eb t\u00eb rekomandoj kategorikisht q\u00eb t\u00eb mos b\u00ebni dhe \u00e7far\u00eb shoh tani masivisht: \"Ah, nj\u00eb loj\u00eb e re!\" \u2013 u nxituam ta blejm\u00eb, e blejm\u00eb dhe: \"Le t\u00eb marrim tani n\u00eb shkoll\u00eb, t\u00eb tregojm\u00eb t\u00eb gjith\u00ebve miqt\u00eb\". Mos b\u00ebni k\u00ebshtu. M\u00eb falni, f\u00ebmij\u00ebt e mi po rriten dhe un\u00eb gjithmon\u00eb shoh di\u00e7ka n\u00eb f\u00ebmij\u00eb, e v\u00eb re te vetja, dhe pastaj e p\u00ebrgjith\u00ebsoj p\u00ebr t\u00eb tjer\u00ebt.<\/p>\n

P\u00ebrgjigjja p\u00ebrfundimtare: nuk ju nevojitet Kubernetes. Duhet t\u00eb zgjidhni problemet tuaja.<\/p><\/blockquote>\n

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