{"id":35059,"date":"2019-10-31T22:02:06","date_gmt":"2019-10-31T19:02:06","guid":{"rendered":"https:\/\/prohoster.info\/blog\/o-tom-kak-plesk-na-kubecon-pobyval\/"},"modified":"2019-10-31T22:02:06","modified_gmt":"2019-10-31T19:02:06","slug":"o-tom-kak-plesk-na-kubecon-pobyval","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/o-tom-kak-plesk-na-kubecon-pobyval","title":{"rendered":"Rreth asaj se si Plesk ishte n\u00eb KubeCon","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

K\u00ebt\u00eb vit, Plesk vendosi t\u00eb d\u00ebrgoj\u00eb disa njer\u00ebz n\u00eb KubeCon \u2014 ngjarja kryesore p\u00ebr Kubernetes n\u00eb bot\u00eb. Konferenca t\u00eb profilizuara mbi k\u00ebt\u00eb tem\u00eb nuk ka n\u00eb Rusi. Sigurisht, p\u00ebr K8s flitet dhe t\u00eb gjith\u00eb e duan, por kaq shum\u00eb kompani q\u00eb e praktikojn\u00eb at\u00eb n\u00eb nj\u00eb vend t\u00eb vetin nuk mblidhen askund tjet\u00ebr. Un\u00eb isha nj\u00eb nga pjes\u00ebmarr\u00ebsit, pasi punoj n\u00eb nj\u00eb platform\u00eb t\u00eb bazuar n\u00eb Kubernetes. <\/p>\n

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

P\u00ebr organizat\u00ebn<\/h3>\n

\nShkall\u00ebt e konferenc\u00ebs jan\u00eb mahnit\u00ebse: 7000 pjes\u00ebmarr\u00ebs, nj\u00eb qend\u00ebr e madhe ekspozitash. Kalimi nga nj\u00eb sall\u00eb n\u00eb tjetr\u00ebn merrte 5-7 minuta. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb po zhvilloheshin 30 kumtesa mbi tema t\u00eb ndryshme. Ishte nj\u00eb num\u00ebr i madh kompanish me stendat e tyre, disa prej t\u00eb cilave ofronin shum\u00eb \u00e7mime t\u00eb mira dhe ca t\u00eb shk\u00eblqyera, si dhe shp\u00ebrndanin gj\u00ebra t\u00eb ndryshme si bluzat, stilolapsat dhe sende t\u00eb tjera t\u00eb k\u00ebndshme. T\u00eb gjitha komunikimet ishin n\u00eb anglisht, por nuk pata ndonj\u00eb v\u00ebshtir\u00ebsi. N\u00ebse kjo \u00ebsht\u00eb e vet\u00ebmja faktor q\u00eb ju pengon t\u00eb shkoni n\u00eb konferenca nd\u00ebrkomb\u00ebtare, shkoni pa ngurrim. Anglishtja n\u00eb IT \u00ebsht\u00eb m\u00eb e leht\u00eb se anglishtja e zakonshme p\u00ebr shkak t\u00eb numrit t\u00eb madh t\u00eb fjal\u00ebve t\u00eb njohura q\u00eb shkruani dhe lexoni \u00e7do dit\u00eb n\u00eb kod dhe dokumentacion. Edhe n\u00eb kuptimin e kumtesave nuk kishte probleme. Informacioni ishte shum\u00eb i dh\u00ebn\u00eb. N\u00eb mbr\u00ebmje mundohesha me serverin, n\u00eb t\u00eb cilin ishte shfryt\u00ebzuar mbushja e memories dhe po derdhej direkt n\u00eb n\u00ebnnd\u00ebrgjegje. <\/p>\n

P\u00ebr kumtesat<\/h3>\n

\nD\u00ebshiroj t\u00eb flas shkurtimisht p\u00ebr kumtesat q\u00eb m\u00eb p\u00eblqyen m\u00eb shum\u00eb, dhe do t'i rekomandoja ato p\u00ebr t'u par\u00eb. <\/p>\n

Intro to CNAB: Packaging Cloud Native Applications with Multiple Toolchains \u2014 Chris Crone, Docker<\/a><\/noindex><\/h4>\n

\nKy k\u00ebtij raporti m\u00eb la nj\u00eb p\u00ebrshtypje t\u00eb madhe sepse theksoi nj\u00eb dhimbje t\u00eb fort\u00eb. Ne kemi shum\u00eb sh\u00ebrbime t\u00eb shp\u00ebrndara, t\u00eb cilat mb\u00ebshteten dhe hartohen nga njer\u00ebz t\u00eb ndrysh\u00ebm n\u00eb ekip. Ne ndjekim qasjet e infrastruktur\u00ebs si kod, por ka disa probleme t\u00eb pazgjidhura. Ekziston nj\u00eb repozitor me kod n\u00eb Ansible, por aktuali status dhe inventari ruhen te zhvilluesi q\u00eb ekzekuton skriptin n\u00eb makin\u00ebn e tij, aty ruhen edhe kredencialet. Disa informacione mund t\u00eb gjenden n\u00eb Confluence, por nuk \u00ebsht\u00eb gjithmon\u00eb e qart\u00eb ku. Nuk ka nj\u00eb vend ku mund t\u00eb shtypni nj\u00eb buton dhe gj\u00ebrat do t\u00eb b\u00ebhen t\u00eb mira. Propozohet q\u00eb t\u00eb b\u00ebhet nj\u00eb p\u00ebrshkrim dhe t\u00eb vendoset n\u00eb repozitor jo vet\u00ebm kodi, por edhe mjete p\u00ebr d\u00ebrgimin. T\u00eb p\u00ebrshkruhet se si t\u00eb merret statusi dhe kredencialet, t\u00eb b\u00ebhet make Install dhe t\u00eb shijoni rezultatin. Do t\u00eb donja m\u00eb shum\u00eb rregull n\u00eb sh\u00ebrbime, do t\u00eb ndjek marr\u00ebveshjet CNAB, do t'i p\u00ebrdor\u00eb, implementoj\u00eb dhe do t\u00eb bind. Nj\u00eb model i mir\u00eb p\u00ebr p\u00ebrgatitjen e Readme n\u00eb rep.<\/p>\n

Mbajeni Space Shuttle T\u00eb Fluturonte: Shkrimi i Operator\u00ebve t\u00eb Fort\u00eb \u2014 Illya Chekrygin, Upbound<\/a><\/noindex><\/h4>\n

\nEkziston shum\u00eb informacion mbi pengesat kur shkruani operator\u00ebt. E konsideroj k\u00ebt\u00eb raport t\u00eb domosdosh\u00ebm p\u00ebr ata q\u00eb jan\u00eb t\u00eb gatsh\u00ebm t\u00eb shkruajn\u00eb operatorin e tyre p\u00ebr Kubernetes. Aty jan\u00eb p\u00ebrfshir\u00eb t\u00eb gjitha gj\u00ebrat si statuset, mbledhja e mbeturinave, konkurrenca dhe shum\u00eb t\u00eb tjera. Shum\u00eb informuese. M\u00eb p\u00eblqeu shum\u00eb citimi nga kodi i volumeneve t\u00eb q\u00ebndrueshme t\u00eb Kubernetes:
\n\"Rreth
\n<\/p>\n

Plani Kontrollues i Kubernetes p\u00ebr Njer\u00ebz T\u00eb Z\u00ebn\u00eb Q\u00eb P\u00eblqejn\u00eb Imazhe \u2014 Daniel Smith, Google<\/a><\/noindex><\/h4>\n

\nK8s tepri me kompleksitetin e integrimit n\u00eb em\u00ebr t\u00eb thjesht\u00ebsis\u00eb s\u00eb realizimit.<\/p>\n

Ky raport zbulon n\u00eb detaje nj\u00eb nga element\u00ebt themelor t\u00eb arkitektur\u00ebs s\u00eb klasterit \u2014 plani kontrollues, konkretisht grupin e kontrollor\u00ebve. P\u00ebrshkruhen roli dhe arhitektura e tyre, parimet baz\u00eb t\u00eb krijimit t\u00eb nj\u00eb kontrollori t\u00eb vet n\u00eb shembullin e atyre ekzistuese.<\/p>\n

Nga momentet m\u00eb origjinale \u2014 rekomandimi p\u00ebr t\u00eb mos maskuar situatat e papritura me sjelljen e sakt\u00eb t\u00eb kontrollor\u00ebve, por t\u00eb ndryshohet sjellja n\u00eb nj\u00ebfar\u00eb m\u00ebnyre, p\u00ebr t\u00eb dh\u00ebn\u00eb nj\u00eb sinjal sistemit n\u00eb lidhje me shfaqjen e problemeve.<\/p>\n

Korrja e Ngarkesave Me Performanc\u00eb T\u00eb Lart\u00eb T\u00eb eBay me Kubernetes \u2014 Xin Ma, eBay<\/a><\/noindex><\/h4>\n

\nShum\u00eb p\u00ebrvoj\u00eb interesante, shum\u00eb informacion me receta p\u00ebr at\u00eb q\u00eb duhet marr\u00eb parasysh kur ke nj\u00eb ngarkes\u00eb t\u00eb v\u00ebrtet\u00eb t\u00eb lart\u00eb. N\u00eb Kubernetes ata jan\u00eb futur mir\u00eb, mb\u00ebshtesin 50 klastere. Fol\u00ebn p\u00ebr t\u00eb gjitha aspektet e nxjerrjes maksimale t\u00eb performanc\u00ebs. Rekomandoj t\u00eb shihni raportin, para se t\u00eb merrni ndonj\u00eb vendim teknik mbi klasteret.<\/p>\n

Grafana Loki: Si Prometheus, Por p\u00ebr logje. \u2014 Tom Wilkie, Grafana Labs<\/a><\/noindex><\/h4>\n

\nPasqyra, pas s\u00eb cil\u00ebs kuptova se Loki duhet patjet\u00ebr provuar p\u00ebr log-et n\u00eb klaster dhe, ndoshta, t\u00eb mbetet me t\u00eb. Thelbi: Elasticsearch \u00ebsht\u00eb i r\u00ebnd\u00eb. Grafana donte t\u00eb zhvillonte nj\u00eb zgjidhje t\u00eb leht\u00eb dhe t\u00eb shkall\u00ebzueshme, e p\u00ebrshtatshme p\u00ebr debugimin e problemeve. Zgjidhja rezultoi t\u00eb ishte elegante: Loki merr informacionin meta nga Kubernetes (etiketat, si Prometheus), dhe sipas tyre rendit log-et. K\u00ebshtu, mund t\u00eb zgjedh\u00ebsh fragmente log-u sipas sh\u00ebrbimit, t\u00eb gjesh pod-in konkret, t\u00eb zgjedh\u00ebsh koh\u00ebn specifike, t\u00eb filtrosh sipas kodit t\u00eb gabimit. K\u00ebto filtre punojn\u00eb pa k\u00ebrkim p\u00ebrmbajt\u00ebsor. K\u00ebshtu, gradualisht duke ngushtuar rrethin e k\u00ebrkimit, mund t\u00eb arrish te gabimi specifik i nevojsh\u00ebm. N\u00eb fund, k\u00ebrkimi aktivizohet p\u00ebrs\u00ebri, por pasi rrethi \u00ebsht\u00eb ngushtuar, mjafton shpejt\u00ebsia pa indeksim. Me klikimin mbi t\u00eb, ngarkohet konteksti - disa rreshta p\u00ebrpara dhe disa rreshta log-u pas. K\u00ebshtu, duket si k\u00ebrkimi n\u00eb nj\u00eb skedar log-esh dhe grepi mbi t\u00eb, por pak m\u00eb i rehatsh\u00ebm dhe n\u00eb t\u00eb nj\u00ebjtin nd\u00ebrfaqe ku jan\u00eb metrikat. Mund t\u00eb num\u00ebroj\u00eb sasin\u00eb e rasteve t\u00eb k\u00ebrkimit. K\u00ebrkesat vet\u00eb duken si nj\u00eb gjuh\u00eb e Prometheus dhe duken t\u00eb thjeshta. Paraqit\u00ebsi i raportit vuri n\u00eb dukje se zgjidhja nuk \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme p\u00ebr analitik\u00eb. Fort e rekomandoj t\u00eb shikohet nga t\u00eb gjith\u00eb ata q\u00eb kan\u00eb nevoj\u00eb p\u00ebr log-e, me nj\u00eb paraqitje shum\u00eb t\u00eb leht\u00eb.<\/p>\n

Si Intuit B\u00ebn Canary dhe Blue Green Deployments me nj\u00eb K8s Controller \u2014 Daniel Thomson<\/a><\/noindex><\/h4>\n

\nProceset e kanareve dhe t\u00eb deploy-eve blue-green jan\u00eb treguar shum\u00eb qart\u00eb. Rekomandoj t\u00eb shikohet ky raport p\u00ebr ata q\u00eb ende nuk jan\u00eb bindur p\u00ebr k\u00ebt\u00eb. Paraqit\u00ebsit kan\u00eb prezantuar zgjidhjen si nj\u00eb zgjerim p\u00ebr sistemin perspektiv ARGO CI-CD. M\u00eb leht\u00eb \u00ebsht\u00eb t\u00eb d\u00ebgjosh anglisht\u00ebn e paraqit\u00ebsit nga Rusia sesa t\u00eb tjer\u00ebt. <\/p>\n

Kontrolli m\u00eb i Men\u00e7ur i Aksesit p\u00ebr Kubernetes: Nj\u00eb Qasje m\u00eb e Thjesht\u00eb p\u00ebr Auth \u2014 Rob Scott, ReactiveOps<\/a><\/noindex><\/h4>\n

\nNj\u00eb nga aspektet m\u00eb t\u00eb v\u00ebshtira t\u00eb menaxhimit t\u00eb klastereve mbetet konfigurimi i siguris\u00eb, sidomos t\u00eb drejtave t\u00eb aksesit n\u00eb burime. Primitiv\u00ebt e integruar t\u00eb K8s lejojn\u00eb konfigurimin e autorizimit, si t\u00eb duash. Si t\u00eb mbash n\u00eb gjendje t\u00eb p\u00ebrdit\u00ebsuar pa dhimbje? Si t\u00eb kuptosh se \u00e7far\u00eb po ndodh me t\u00eb drejtat e aksesit dhe t\u00eb debatosh rolet e krijuara? N\u00eb k\u00ebt\u00eb raport \u00ebsht\u00eb paraqitur jo vet\u00ebm nj\u00eb p\u00ebrmbledhje e disa mjeteve p\u00ebr debugging t\u00eb autorizimit n\u00eb k8s, por jan\u00eb dh\u00ebn\u00eb gjithashtu rekomandime t\u00eb p\u00ebrgjithshme p\u00ebr nd\u00ebrtimin e politikave t\u00eb thjeshta dhe efektive.<\/p>\n

Raporte t\u00eb tjera<\/h4>\n

\nNuk e rekomandoj. Disa ishin kapiten\u00eb, disa t\u00eb tjera shum\u00eb t\u00eb komplikuara. Ju sugjeroj t\u00eb shihni k\u00ebt\u00eb playlist dhe t\u00eb shikoni gjith\u00e7ka q\u00eb \u00ebsht\u00eb e etiketuar si keynote. Kjo do t'ju lejoj\u00eb t\u00eb shihni nj\u00eb pamje t\u00eb gjer\u00eb mbi industrin\u00eb p\u00ebrreth aplikacioneve Cloud Native, dhe m\u00eb pas duhet t\u00eb p\u00ebrdorni ctrl+f p\u00ebr t\u00eb k\u00ebrkuar me fjal\u00eb ky\u00e7e, kompani, produkte dhe qasje q\u00eb ju interesojn\u00eb. <\/p>\n

K\u00ebtu \u00ebsht\u00eb lidhja e playlist-it me prezantimet, kushtojini v\u00ebmendje.<\/p><\/blockquote>\n

<\/p>\n

Youtube Playlist<\/a><\/noindex><\/h4>\n

Rreth standeve t\u00eb kompanive<\/h3>\n

\nN\u00eb stend\u00ebn e Haproxy m\u00eb dhuruan nj\u00eb fanell\u00eb p\u00ebr djalin tim. Dyshoj se p\u00ebr k\u00ebt\u00eb do ta z\u00ebvend\u00ebsoj Nginx-in me haproxy n\u00eb prodhim, por i mbajta mend ata m\u00eb shum\u00eb se t\u00eb tjer\u00ebt. Kush e di se \u00e7far\u00eb do t'u b\u00ebjn\u00eb pronar\u00ebt e rinj Nginx-it. <\/p>\n

\"Rreth
\nN\u00eb stend\u00ebn e IBM gjat\u00eb t\u00eb tre dit\u00ebve u mbajt\u00ebn prezantime t\u00eb shkurtra dhe ata t\u00ebrhiqnin njer\u00ebz duke ofruar Oculus Go, kufje Beats dhe nj\u00eb dron. Duhej t\u00eb ishe n\u00eb stend \u00e7do gjysm\u00eb ore. Dy her\u00eb gjat\u00eb tre dit\u00ebve e provova fatin - nuk fitova. Po ashtu pati prezantime t\u00eb shkurtra nga VMWare dhe Microsoft.<\/p>\n

N\u00eb stend\u00ebn e Ubuntu b\u00ebra at\u00eb q\u00eb duket se b\u00ebnte t\u00eb gjith\u00eb - u fotografova me Shuttleworth. Nj\u00eb njeri shum\u00eb shoq\u00ebror, u g\u00ebzua kur m\u00ebsova se e p\u00ebrdor nga versioni 8.04 dhe se serveri im ka punuar me t\u00eb p\u00ebr 10 vjet pa dist upgrade pa asnj\u00eb nd\u00ebrprerje (padyshim pa akses n\u00eb Internet).<\/p>\n

\"Rreth
\nUbuntu po zhvillon MicroK8s i saj - Fast, Light, Upstream Developer Kubernetes. microk8s.io<\/a><\/noindex><\/p>\n

Nuk mund t\u00eb kaloj pa biseduar me Dimitri Stolyarov, bisedova me t\u00eb p\u00ebr dit\u00ebt e v\u00ebshtira t\u00eb inxhinier\u00ebve q\u00eb mb\u00ebshtesin Kubernetes. Ai do t'i delegoj\u00eb prezantimet koleg\u00ebve t\u00eb tij, por po p\u00ebrgatit nj\u00eb format t\u00eb ri p\u00ebrpara materialit. Inkurkoi t\u00eb abonoheni n\u00eb kanalin e Flant n\u00eb youtube.<\/p>\n

\"Rreth
\nIBM, Cisco, Microsoft, VMWare kan\u00eb investuar shum\u00eb para n\u00eb stenda. Stendat ishin m\u00eb t\u00eb p\u00ebrfshira nga miqt\u00eb open source. Bisedova n\u00eb stend\u00eb me p\u00ebrfaq\u00ebsuesit e Grafana, ata m\u00eb bind\u00ebn - duhet ta provoj Loki. N\u00eb p\u00ebrgjith\u00ebsi, duket se nj\u00eb k\u00ebrkim i plot\u00eb n\u00eb sistemin e logjeve \u00ebsht\u00eb i nevojsh\u00ebm vet\u00ebm p\u00ebr analiza, nd\u00ebrsa p\u00ebr troubleshooting mjafton nj\u00eb sistem si Loki. Bisedova me zhvilluesit e Prometheus. Ata nuk planifikojn\u00eb t\u00eb b\u00ebjn\u00eb ruajtje afatgjat\u00eb t\u00eb metricave dhe downsampling t\u00eb t\u00eb dh\u00ebnave. Ata rekomandojn\u00eb t\u00eb shikoni cortex dhe thanos si nj\u00eb mjet zgjidhjeje. Pati shum\u00eb stenda, nevojitej nj\u00eb dit\u00eb p\u00ebr t\u00eb kaluar t\u00eb gjith\u00eb. Disa zgjidhje p\u00ebr monitorimin si sh\u00ebrbim. Nj\u00eb grup sh\u00ebrbimesh t\u00eb siguris\u00eb. Nj\u00eb grup sh\u00ebrbimesh performance. Disa UI p\u00ebr Kubernetes. Shum\u00eb kan\u00eb ofruar k8s si sh\u00ebrbim. T\u00eb gjith\u00eb duan pjes\u00ebn e tregut.<\/p>\n

Amazon dhe Google kan\u00eb marr\u00eb qera oborre me bar artificial n\u00eb \u00e7atin\u00eb e nd\u00ebrtesave dhe kan\u00eb vendosur aty krevat\u00eb dielli. Amazon shp\u00ebrndante gota dhe shiste limonad\u00eb, nd\u00ebrsa n\u00eb stend\u00eb shpjegonte risit\u00eb n\u00eb pun\u00ebn me instancat Spot. Google ofronte biskota me logon Kubernetes dhe kishte nj\u00eb zon\u00eb fotografike t\u00eb mir\u00eb, nd\u00ebrsa n\u00eb stend\u00eb peshkonte p\u00ebr peshq t\u00eb m\u00ebdhenj enterprise.<\/p>\n

P\u00ebr Barcelon\u00ebn<\/h3>\n

\nI dashuruar me Barcelon\u00ebn. Kam qen\u00eb atje p\u00ebr her\u00eb t\u00eb dyt\u00eb, hera e par\u00eb ishte n\u00eb vitin 2012 n\u00eb nj\u00eb ekskursione. \u00cbsht\u00eb e habitshme, por shum\u00eb fakte m\u00eb dol\u00ebn n\u00eb mendje, arrita t\u00eb tregoj shum\u00eb koleg\u00ebve t\u00eb mi, isha nj\u00eb mini-guide. Ajri i past\u00ebr detar m\u00eb \u00e7liroi menj\u00ebher\u00eb nga alergjit\u00eb. Ushqim deti i shijsh\u00ebm, paelja, sangria. Arkitektura shum\u00eb e ngroht\u00eb dhe diellore. Niveli i ul\u00ebt i nd\u00ebrtesave, shum\u00eb shum\u00eb gjelb\u00ebrim. Gjat\u00eb k\u00ebtyre tri dit\u00ebve, kemi ecur rreth 50 kilometra, dhe ky qytet t\u00eb b\u00ebn t\u00eb duash t\u00eb ec\u00ebsh edhe m\u00eb shum\u00eb. T\u00eb gjitha k\u00ebto pas ligj\u00ebratave, n\u00eb mbr\u00ebmje. <\/p>\n

\"Rreth
\n\"Rreth
\n\"Rreth<\/p>\n

\u00c7far\u00eb kuptova kryesisht<\/h3>\n

\nJam shum\u00eb i lumtur q\u00eb m\u00eb ra rasti t\u00eb vizitoj k\u00ebt\u00eb konferenc\u00eb. Ajo m\u00eb dha renditje p\u00ebr at\u00eb q\u00eb deri at\u00ebher\u00eb ishte pa renditje. M\u00eb inspiroi, b\u00ebri disa gj\u00ebra t\u00eb dukshme.<\/p>\n

Nj\u00eb mendim kaloi si nj\u00eb vij\u00eb e kuqe: Kubernetes nuk \u00ebsht\u00eb nj\u00eb pik\u00eb p\u00ebrfundimtare, por nj\u00eb mjet. Nj\u00eb platform\u00eb p\u00ebr nd\u00ebrtimin e platformave.<\/b><\/p>\n

Dhe detyra kryesore e gjith\u00eb l\u00ebvizjes: t\u00eb mbledh\u00eb dhe kontribuoj\u00eb n\u00eb aplikacione t\u00eb shkall\u00ebzueshme<\/b><\/p>\n

Direksionet kryesore mbi t\u00eb cilat punon komuniteti jan\u00eb p\u00ebrmbledhur. Nj\u00ebsoj si\u00e7 ndodhi m\u00eb par\u00eb me 12 faktor\u00ebt p\u00ebr aplikacione, u shfaq nj\u00eb list\u00eb se \u00e7far\u00eb dhe si duhet b\u00ebr\u00eb p\u00ebr infrastruktur\u00ebn n\u00eb t\u00ebr\u00ebsi. N\u00ebse d\u00ebshironi, mund ta quani k\u00ebt\u00eb trende:<\/p>\n