{"id":34825,"date":"2019-10-31T22:00:35","date_gmt":"2019-10-31T19:00:35","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah\/"},"modified":"2019-10-31T22:00:35","modified_gmt":"2019-10-31T19:00:35","slug":"kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah","title":{"rendered":"Si t\u00eb lidhni klaster\u00ebt e Kubernetes n\u00eb qendra t\u00eb ndryshme t\u00eb t\u00eb dh\u00ebnave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Si
\nMir\u00eb se vini n\u00eb serin\u00eb e udh\u00ebzuesve t\u00eb shpejt\u00eb p\u00ebr Kubernetes.<\/strong> Kjo \u00ebsht\u00eb nj\u00eb kolon\u00eb e rregullt me pyetje nga m\u00eb interesante q\u00eb marrim online dhe n\u00eb trajnimet tona. P\u00ebgjigjet nj\u00eb ekspert i Kubernetes.<\/p>\n

<\/p>\n

Eksperti i sot\u00ebm \u00ebsht\u00eb Daniele Polencic (Daniele Polencic<\/a><\/noindex>). Daniele punon si instruktor dhe zhvillues softueri n\u00eb Learnk8s<\/a><\/noindex>.<\/p><\/blockquote>\n

N\u00ebse d\u00ebshironi t\u00eb merrni p\u00ebrgjigjen p\u00ebr pyetjen tuaj n\u00eb postimin e ardhsh\u00ebm, na kontaktoni p\u00ebrmes emailit<\/a><\/noindex> ose n\u00eb Twitter: @learnk8s<\/a><\/noindex>.<\/p>\n

<\/p>\n

A e keni humbur postimin e kaluar? K\u00ebrkoni ata k\u00ebtu<\/a><\/noindex>.<\/p>\n

<\/p>\n

Si t\u00eb lidhni klaster\u00ebt Kubernetes n\u00eb qendra t\u00eb ndryshme t\u00eb t\u00eb dh\u00ebnave?<\/h3>\n

<\/p>\n

N\u00eb p\u00ebrmbledhje<\/strong>: kubefed v2 shum\u00eb shpejt do t\u00eb lansohet<\/a><\/noindex>, dhe gjithashtu rekomandoj t\u00eb lexoni p\u00ebr Shipper<\/a><\/noindex> dhe projekti multi-cluster-scheduler<\/a><\/noindex>.
\n<\/a><\/noindex><\/p>\n

Shpesh infrastruktura riprodhohet dhe shp\u00ebrndahet n\u00eb rajone t\u00eb ndryshme, ve\u00e7an\u00ebrisht n\u00eb ambiente t\u00eb kontrolluara.<\/p><\/blockquote>\n

N\u00ebse nj\u00eb rajon nuk \u00ebsht\u00eb n\u00eb dispozicion, trafiku redirektohet n\u00eb nj\u00eb tjet\u00ebr p\u00ebr t\u00eb shmangur ndalesat.<\/strong><\/p>\n

<\/p>\n

Me Kubernetes mund t\u00eb p\u00ebrdorni nj\u00eb strategji t\u00eb ngjashme dhe t\u00eb shp\u00ebrndani ngarkesat e pun\u00ebs n\u00eb rajone t\u00eb ndryshme.<\/p>\n

<\/p>\n

Mund t\u00eb keni nj\u00eb ose m\u00eb shum\u00eb klaster\u00eb p\u00ebr ekip, rajon, ambient ose nj\u00eb kombinim t\u00eb k\u00ebtyre elementeve.<\/p>\n

<\/p>\n

Klaster\u00ebt tuaj mund t\u00eb vendosen n\u00eb re t\u00eb ndryshme dhe n\u00eb mjedise lokale.<\/p>\n

<\/p>\n

Por si t\u00eb planifikoni infrastruktur\u00ebn p\u00ebr nj\u00eb shp\u00ebrndarje t\u00eb till\u00eb gjeografike?
\nA duhet t\u00eb krijoni nj\u00eb klaster t\u00eb madh q\u00eb p\u00ebrfshin disa re n\u00ebn nj\u00eb rrjet t\u00eb vet\u00ebm?
\nOse t\u00eb vendosni shum\u00eb klaster\u00eb t\u00eb vegj\u00ebl dhe t\u00eb gjeni nj\u00eb m\u00ebnyr\u00eb p\u00ebr t'i kontrolluar dhe sinkronizuar ato?<\/em><\/p>\n

<\/p>\n

Nj\u00eb klaster udh\u00ebheq\u00ebs<\/h3>\n

<\/p>\n

Krijimi i nj\u00eb klasteri n\u00ebn nj\u00eb rrjet t\u00eb vet\u00ebm nuk \u00ebsht\u00eb aq e leht\u00eb.<\/em><\/p>\n

<\/p>\n

Imaginoni, keni nj\u00eb aksident, \u00ebsht\u00eb humbur lidhja midis segmenteve t\u00eb klasterit.<\/p>\n

<\/p>\n

N\u00ebse keni nj\u00eb server kryesor, gjysma e burimeve nuk do t\u00eb mund t\u00eb marrin urdhra t\u00eb rinj, sepse nuk do t\u00eb mund t\u00eb lidhen me kryesorin.<\/p>\n

<\/p>\n

Dhe n\u00eb k\u00ebt\u00eb rast, keni tabela t\u00eb vjetra ruterimi (kube-proxy<\/code> nuk mund t\u00eb ngarkoj\u00eb t\u00eb rejat) dhe asnj\u00eb pod t\u00eb shtuar (kubelet nuk mund t\u00eb k\u00ebrkoj\u00eb azhurnime).<\/p>\n

<\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb edhe m\u00eb e keqe, n\u00ebse Kubernetes nuk sheh nj\u00eb nyje, e markon at\u00eb si t\u00eb humbur dhe shp\u00ebrndan pod\u2019\u00ebt q\u00eb mungojn\u00eb n\u00eb nyjet ekzistuese.<\/p>\n

<\/p>\n

Si rezultat, keni dyfish pod\u2019\u00eb.<\/strong><\/p>\n

<\/p>\n

N\u00ebse krijoni nga nj\u00eb server kryesor p\u00ebr secilin rajon, do t\u00eb keni probleme me algoritmin p\u00ebr t\u00eb arritur konsensusin n\u00eb databaz\u00ebn etcd.Sh\u00ebn. red. \u2014 N\u00eb t\u00eb v\u00ebrtet\u00eb, baza e t\u00eb dh\u00ebnave etcd nuk ka nevoj\u00eb patjet\u00ebr t\u00eb ndodhet n\u00eb serverat kryesor\u00eb. Ajo mund t\u00eb aktivizohet n\u00eb nj\u00eb grup t\u00eb ve\u00e7ant\u00eb server\u00ebsh n\u00eb nj\u00eb rajon. Megjithat\u00eb, kjo do t\u00eb sjell\u00eb nj\u00eb pik\u00eb d\u00ebshtimi p\u00ebr klusterin. Sidoqoft\u00eb, \u00ebsht\u00eb e shpejt\u00eb.<\/em>)<\/p>\n

<\/p>\n

etcd p\u00ebrdor algoritmin raft<\/a><\/noindex>, p\u00ebr t\u00eb arritur nj\u00eb konsensus mbi vler\u00ebn para se ta shkruaj\u00eb at\u00eb n\u00eb disk.
\nK\u00ebshtu q\u00eb shumica e instancave duhet t\u00eb arrijn\u00eb konsensusin para se gjendja t\u00eb mund t\u00eb shkruhet n\u00eb etcd.<\/p>\n

<\/p>\n

N\u00ebse vonesa midis instancave t\u00eb etcd rritet ndjesh\u00ebm, si\u00e7 ndodh me tre instanca etcd n\u00eb regione t\u00eb ndryshme, k\u00ebrkohet shum\u00eb koh\u00eb p\u00ebr t\u00eb arritur konsensusin dhe p\u00ebr ta shkruar at\u00eb n\u00eb disk.
\nKjo ndikon edhe n\u00eb kontrollor\u00ebt e Kubernetes.<\/p>\n

<\/p>\n

Menaxheri i kontrollor\u00ebve ka nevoj\u00eb p\u00ebr m\u00eb shum\u00eb koh\u00eb p\u00ebr t\u00eb m\u00ebsuar mbi ndryshimin dhe p\u00ebr t\u00eb shkruar p\u00ebrgjigjen n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave.<\/p>\n

<\/p>\n

Dhe pasi q\u00eb kontrollor\u00ebt nuk jan\u00eb vet\u00ebm nj\u00eb, por disa, ndodhin nj\u00eb reaksion n\u00eb zinxhir, dhe e gjith\u00eb klasteri fillon t\u00eb funksionoj\u00eb shum\u00eb ngadal\u00eb.<\/strong>.<\/p>\n

<\/p>\n

etcd \u00ebsht\u00eb aq i ndjesh\u00ebm ndaj vonesave, saq\u00eb n\u00eb dokumentacionin zyrtar rekomandohet p\u00ebrdorimi i SSD-ve n\u00eb vend t\u00eb hard disqeve t\u00eb zakonsh\u00ebm.<\/a><\/noindex>.<\/p>\n

<\/p>\n

Momentalisht, nuk ka shembuj t\u00eb mir\u00eb t\u00eb nj\u00eb rrjeti t\u00eb madh p\u00ebr nj\u00eb klaster.<\/strong><\/p>\n

<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, komuniteti i zhvilluesve dhe grupi SIG-cluster po p\u00ebrpiqen t\u00eb kuptojn\u00eb se si t\u00eb orkestrojn\u00eb klaster\u00ebt ashtu si Kubernetes orkestrojn\u00eb konteinerit.<\/p>\n

<\/p>\n

Opsioni 1: federata e klaster\u00ebve me kubefed<\/h3>\n

<\/p>\n

Pergjigjja zyrtare nga SIG-cluster \u00ebsht\u00eb kubefed2, versioni i ri i klientit dhe operatorit t\u00eb kube federation.<\/a><\/noindex>.<\/p>\n

<\/p>\n

P\u00ebr her\u00eb t\u00eb par\u00eb, doli t\u00eb menaxhohej nj\u00eb koleksion klaster\u00ebsh si nj\u00eb objekt t\u00eb vet\u00ebm p\u00ebrmes mjetit kube federation.<\/p>\n

<\/p>\n

Fillimi ishte i mir\u00eb, por p\u00ebrfundimisht kube federation nuk arriti t\u00eb b\u00ebhej popullor, sepse nuk mb\u00ebshteste t\u00eb gjitha burimet.<\/p>\n

<\/p>\n

Ai mb\u00ebshteste shp\u00ebrndarjen e kombinuar dhe sh\u00ebrbimet, por, p\u00ebr shembull, nuk mb\u00ebshteste StatefulSets.
\nDhe gjithashtu konfigurimi i federat\u00ebs u transmetua n\u00eb form\u00eb anotacionesh dhe nuk ishte fleksib\u00ebl.<\/p>\n

<\/p>\n

Imagjinoni se si mund t\u00eb p\u00ebrshkruhet ndarja e kopjeve p\u00ebr \u00e7do klaster n\u00eb federat\u00eb duke p\u00ebrdorur vet\u00ebm dhe vet\u00ebm anotacione.<\/em><\/p>\n

<\/p>\n

Rezultoi nj\u00eb kaos i plot\u00eb.<\/strong><\/p>\n

<\/p>\n

SIG-cluster b\u00ebri nj\u00eb pun\u00eb t\u00eb madhe pas kubefed v1 dhe vendosi t\u00eb qaset problemit nga nj\u00eb k\u00ebndv\u00ebshtrim tjet\u00ebr.<\/p>\n

<\/p>\n

N\u00eb vend t\u00eb anotacioneve, ata vendos\u00ebn t\u00eb l\u00ebshonin nj\u00eb kontrollor q\u00eb instalon n\u00eb klaster\u00ebt. Ai mund t\u00eb konfigurohet me ndihm\u00ebn e p\u00ebrcaktimeve t\u00eb burimeve t\u00eb personalizuara (Custom Resource Definition, CRD).<\/strong><\/p>\n

<\/p>\n

P\u00ebr \u00e7do burim q\u00eb do t\u00eb jet\u00eb pjes\u00eb e federat\u00ebs, keni nj\u00eb p\u00ebrcaktim personal t\u00eb CRD nga tre seksione:<\/p>\n

<\/p>\n