{"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\/bs\/blog\/administrirovanie\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah","title":{"rendered":"Kako povezati Kubernetes klastere u razli\u010ditim podatkovnim centrima","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Kako povezati Kubernetes klastere u razli\u010ditim podatkovnim centrima\" src=\"\/wp-content\/uploads\/2019\/06\/fa408b406e31840857bbbe13e1d7ee5a.JPG\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<strong>Dobrodo\u0161li u seriju kratkih vodi\u010da o Kubernetesu.<\/strong> Ovo je redovni kolumn s najzanimljivijim pitanjima koja dobijamo online i na na\u0161im treninzima. Odgovara stru\u010dnjak za Kubernetes.<\/p>\n<p><\/p>\n<blockquote><p>Dana\u0161nji stru\u010dnjak je Daniele Polencic (<noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/danielepolencic\">Daniele Polencic<\/a><\/noindex>). Daniele je instruktor i programer u <noindex><a rel=\"nofollow\" href=\"https:\/\/learnk8s.io\/\">Learnk8s<\/a><\/noindex>.<\/p><\/blockquote>\n<p>Ako \u017eelite odgovor na svoje pitanje u slede\u0107em postu, <noindex><a rel=\"nofollow\" href=\"http:\/\/hello@learnk8s.io\">kontaktirajte nas putem e-po\u0161te<\/a><\/noindex> ili na <noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/learnk8s\">Twitteru: @learnk8s<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Da li ste propustili prethodne postove? <noindex><a rel=\"nofollow\" href=\"https:\/\/learnk8s.io\/visualise-dependencies-kubernetes\">Potra\u017eite ih ovde<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"kak-soedinit-klastery-kubernetes-v-raznyh-data-centrah\">Kako povezati Kubernetes klastere u razli\u010ditim podatkovnim centrima?<\/h3>\n<p><\/p>\n<blockquote><p><strong>Ukratko<\/strong>: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/federation-v2\">uskoro izlazi Kubefed v2<\/a><\/noindex>, a preporu\u010dujem i da pro\u010ditate o <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/bookingcom\/shipper\">Shipper<\/a><\/noindex> i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/admiraltyio\/multicluster-scheduler\">projekat multi-cluster-scheduler<\/a><\/noindex>.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Prili\u010dno \u010desto se infrastruktura replicira i raspore\u0111uje po razli\u010ditim regionima, posebno u kontrolisanim okru\u017eenjima.<\/p><\/blockquote>\n<p><strong>Ako jedan region nije dostupan, saobra\u0107aj se preusmerava na drugi kako bi se izbegli prekidi.<\/strong><\/p>\n<p><\/p>\n<p>Sa Kubernetesom mo\u017eete koristiti sli\u010dnu strategiju i raspore\u0111ivati radne optere\u0107enja po razli\u010ditim regionima.<\/p>\n<p><\/p>\n<p>Mo\u017eete imati jedan ili vi\u0161e klastera po timu, regionu, okru\u017eenju ili kombinaciji ovih elemenata.<\/p>\n<p><\/p>\n<p>Va\u0161i klasteri mogu biti sme\u0161teni u razli\u010ditim oblacima i lokalnom okru\u017eenju.<\/p>\n<p><\/p>\n<p><em>Ali kako planirati infrastrukturu za takvu geografsku disperziju?<br \/>\nTreba da kreirate jedan veliki klaster koji se prote\u017ee preko vi\u0161e oblaka putem jedne mre\u017ee?<br \/>\nIli da imate mnogo malih klastera i prona\u0111ete na\u010din da ih kontroli\u0161ete i sinhronizujete?<\/em><\/p>\n<p><\/p>\n<h3 id=\"odin-rukovodyaschiy-klaster\">Jedan upravlja\u010dki klaster<\/h3>\n<p><\/p>\n<p><em>Kreirati jedan klaster putem jedne mre\u017ee nije tako jednostavno.<\/em><\/p>\n<p><\/p>\n<p>Zamislite, imate havariju, izgubljena je povezanost izme\u0111u segmenata klastera.<\/p>\n<p><\/p>\n<p>Ako imate jedan master server, polovina resursa ne\u0107e mo\u0107i da dobije nove komande jer se ne\u0107e mo\u0107i povezati sa masterom.<\/p>\n<p><\/p>\n<p>A pri tome imate stare tabele rutiranja (<code>kube-proxy<\/code> ne mo\u017ee da u\u010dita nove) i nijedne dodatne pod-ove (kubelet ne mo\u017ee da zahteva a\u017euriranja).<\/p>\n<p><\/p>\n<p>\u0160to je jo\u0161 gore, ako Kubernetes ne vidi \u010dvor, ozna\u010dava ga kao izgubljenog i raspore\u0111uje nedostaju\u0107e pod-ove na postoje\u0107e \u010dvore.<\/p>\n<p><\/p>\n<p><strong>Na kraju imate dvostruko vi\u0161e pod-ova.<\/strong><\/p>\n<p><\/p>\n<p>Ako napravite po jedan master server za svaku oblast, do\u0107i \u0107e do problema sa algoritmom postizanja konsenzusa u bazi podataka etcd. (<em>napomena urednika \u2014 U stvarnosti, etcd baza podataka ne mora nu\u017eno biti na master serverima. Mo\u017ee se pokrenuti na odvojenoj grupi servera u jednom regionu. Me\u0111utim, to \u0107e rezultirati ta\u010dkom kvara klastera. Ali je br\u017ea.<\/em>)<\/p>\n<p><\/p>\n<p>etcd koristi <noindex><a rel=\"nofollow\" href=\"http:\/\/thesecretlivesofdata.com\/raft\/\">raft algoritam<\/a><\/noindex>, da postigne saglasnost pre nego \u0161to upi\u0161e vrednost na disk.<br \/>\nDrugim re\u010dima, ve\u0107ina instanci mora posti\u0107i saglasnost pre nego \u0161to se stanje mo\u017ee zabele\u017eiti u etcd.<\/p>\n<p><\/p>\n<p>Ako se latencija izme\u0111u instanci etcd naglo pove\u0107a, kao u slu\u010daju sa tri instance etcd u razli\u010ditim regionima, potrebno je mnogo vremena da se postigne saglasnost i zabele\u017ei vrednost na disk.<br \/>\nTo se odra\u017eava i na Kubernetes kontrolerima.<\/p>\n<p><\/p>\n<p>Kontroleru je potrebno vi\u0161e vremena da sazna o promeni i zabele\u017ei odgovor u bazu podataka.<\/p>\n<p><\/p>\n<p>A po\u0161to nije samo jedan kontroler, ve\u0107 vi\u0161e njih, <strong>dolazimo do lan\u010dane reakcije, i \u010ditav klaster po\u010dinje raditi veoma sporo.<\/strong>.<\/p>\n<p><\/p>\n<p>etcd je toliko osetljiv na latenciju da <noindex><a rel=\"nofollow\" href=\"https:\/\/coreos.com\/etcd\/docs\/latest\/faq.html#deployment\">u zvani\u010dnoj dokumentaciji se preporu\u010duje kori\u0161\u0107enje SSD umesto obi\u010dnih hard diskova.<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p><strong>Trenutno ne postoje dobri primeri velike mre\u017ee za jedan klaster.<\/strong><\/p>\n<p><\/p>\n<p>Uglavnom, zajednica programera i grupa SIG-cluster poku\u0161avaju da shvate kako orkestrirati klastere kao \u0161to Kubernetes orkestrira kontejnere.<\/p>\n<p><\/p>\n<h3 id=\"variant-1-federaciya-klasterov-s-kubefed\">Opcija 1: federacija klastera sa kubefed<\/h3>\n<p><\/p>\n<p>Zvani\u010dan odgovor od SIG-cluster-a je <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/federation-v2\">kubefed2, nova verzija klijenta i operatora kube federacije.<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Prvi put su poku\u0161ali upravljati kolekcijom klastera kao jednom jedinicom pomo\u0107u alata kube federacija.<\/p>\n<p><\/p>\n<p>Po\u010detak je bio dobar, ali na kraju kube federacija nije postala popularna, jer nije podr\u017eavala sve resurse.<\/p>\n<p><\/p>\n<p>Podr\u017eavala je zajedni\u010dke isporuke i servise, ali na primer, nije podr\u017eavala StatefulSets.<br \/>\nA tako\u0111e, konfiguracija federacije se prosle\u0111ivala u obliku anotacija i nije se odlikovala fleksibilno\u0161\u0107u.<\/p>\n<p><\/p>\n<p><em>Zamislite kako bi mogli opisati podelu replika za svaki klaster u federaciji koriste\u0107i samo anotacije.<\/em><\/p>\n<p><\/p>\n<p><strong>Iza\u0161lo je potpuno zbrkan.<\/strong><\/p>\n<p><\/p>\n<p>SIG-cluster je uradio veliki posao nakon kubefed v1 i odlu\u010dio je pristupiti problemu iz drugog ugla.<\/p>\n<p><\/p>\n<p><strong>Umesto anotacija, odlu\u010dili su da izdaju kontroler koji se instalira na klasterima. Mogu\u0107e ga je konfigurisati pomo\u0107u korisni\u010dkih definicija resursa (Custom Resource Definition, CRD).<\/strong><\/p>\n<p><\/p>\n<p>Za svaku resursu koja \u0107e biti deo federacije, imate prilago\u0111enu definiciju CRD koja se sastoji od tri dela:<\/p>\n<p><\/p>\n<ul>\n<li>standardna definicija resursa, kao \u0161to je deploy;<\/li>\n<li>odjeljak <code>placement<\/code>, gde defini\u0161ete kako \u0107e se resurs rasporediti u federaciji;<\/li>\n<li>odjeljak <code>override<\/code>, gde se za odre\u0111eni resurs mogu prepisati te\u017eina i parametri iz placementa.<\/li>\n<\/ul>\n<p><\/p>\n<p>Evo primera objedinjene isporuke sa delovima placement i override.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: types.federation.k8s.io\/v1alpha1\nkind: FederatedDeployment\nmetadata:\n  name: test-deployment\n  namespace: test-namespace\nspec:\n  template:\n    metadata:\n      labels:\n        app: nginx\n    spec:\n      replicas: 3\n      selector:\n        matchLabels:\n          app: nginx\n      template:\n        metadata:\n          labels:\n            app: nginx\n        spec:\n          containers:\n            - image: nginx\n              name: nginx\n  placement:\n    clusterNames:\n      - cluster2\n      - cluster1\n  overrides:\n    - clusterName: cluster2\n      clusterOverrides:\n        - path: spec.replicas\n          value: 5<\/code><\/pre>\n<p><\/p>\n<p>Kao \u0161to mo\u017eete videti, isporuka je raspore\u0111ena na dva klastera: <code>cluster1<\/code> i <code>cluster2<\/code>.<\/p>\n<p><\/p>\n<p>Prvi klaster isporu\u010duje tri replike, dok je za drugi navedena vrednost 5.<\/p>\n<p><\/p>\n<p>Ako vam je potrebna ve\u0107a kontrola nad brojem replikacija, kubefed2 pru\u017ea novi objekat ReplicaSchedulingPreference, gde se replike mogu raspore\u0111ivati prema te\u017eini:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: scheduling.federation.k8s.io\/v1alpha1\nkind: ReplicaSchedulingPreference\nmetadata:\n  name: test-deployment\n  namespace: test-ns\nspec:\n  targetKind: FederatedDeployment\n  totalReplicas: 9\n  clusters:\n    A:\n      weight: 1\n    B:\n      weight: 2<\/code><\/pre>\n<p><\/p>\n<p>Struktura CRD i API jo\u0161 uvek nisu potpuno spremni, a u zvani\u010dnom repozitorijumu projekta se aktivno radi.<\/p>\n<p><\/p>\n<p><strong>Pratite kubefed2, ali imajte na umu da za radnu sredinu jo\u0161 uvek nije pogodna.<\/strong><\/p>\n<p><\/p>\n<p>Saznajte vi\u0161e o kubefed2 iz <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/blog\/2018\/12\/12\/kubernetes-federation-evolution\/\">zvani\u010dnog \u010dlanka o kubefed2<\/a><\/noindex> u blogu o Kubernetes i u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/federation-v2\">zvani\u010dnom repozitorijumu projekta kubefed<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"variant-2-obedinenie-klasterov-v-stile-bookingcom\">Opcija 2: objedinjavanje klastera u stilu Booking.com<\/h3>\n<p><\/p>\n<p>Razvijeteji Booking.com nisu se bavili kubefed v2, ali su smislili Shipper \u2014 operator za isporuku na vi\u0161e klastera, u vi\u0161e regiona i u vi\u0161e oblaka.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/bookingcom\/shipper\">Shipper<\/a><\/noindex> ne\u0161to sli\u010dno kubefed2.<\/p>\n<p><\/p>\n<p>Oba alata omogu\u0107uju pode\u0161avanje strategije implementacije na vi\u0161e klastera (koji se klasteri koriste i koliko imaju replikacija).<\/p>\n<p><\/p>\n<p>Ali <strong>zadatak Shippera je smanjiti rizik od gre\u0161aka pri isporuci.<\/strong><\/p>\n<p><\/p>\n<p>U Shipperu mo\u017eete definisati niz koraka koji opisuju raspodelu replikacija izme\u0111u prethodnog i trenutnog deploya i obima dolaznog saobra\u0107aja.<\/p>\n<p><\/p>\n<p>Kada \u0161aljete resurs u klaster, kontroler Shipper postepeno implementira ovu promenu na svim objedinj\u0435\u043d\u0438\u043c klasterima.<\/p>\n<p><\/p>\n<p><em>A tako\u0111e, Shipper je vrlo ograni\u010den.<\/em><\/p>\n<p><\/p>\n<p>Na primer, <strong>on prihvata Helm-\u010darate kao ulazne podatke.<\/strong> i ne podr\u017eava vanilla resurse.<br \/>\nU su\u0161tini, Shipper funkcioni\u0161e na slede\u0107i na\u010din.<\/p>\n<p><\/p>\n<p>Umesto standardne isporuke, potrebno je kreirati resurs aplikacije koji uklju\u010duje Helm chart:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: shipper.booking.com\/v1alpha1\nkind: Application\nmetadata:\n  name: super-server\nspec:\n  revisionHistoryLimit: 3\n  template:\n    chart:\n      name: nginx\n      repoUrl: https:\/\/storage.googleapis.com\/shipper-demo\n      version: 0.0.1\n    clusterRequirements:\n      regions:\n        - name: local\n    strategy:\n      steps:\n        - capacity:\n            contender: 1\n            incumbent: 100\n          name: staging\n          traffic:\n            contender: 0\n            incumbent: 100\n        - capacity:\n            contender: 100\n            incumbent: 0\n          name: full on\n          traffic:\n            contender: 100\n            incumbent: 0\n    values:\n      replicaCount: 3<\/code><\/pre>\n<p><\/p>\n<p><strong>Shipper je dobar izbor za upravljanje vi\u0161e klastera, ali njegova tesna povezanost sa Helm-om to samo ote\u017eava.<\/strong><\/p>\n<p><\/p>\n<p><em>A \u0161ta ako svi pre\u0111emo sa Helm-a na <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/blog\/2018\/05\/29\/introducing-kustomize-template-free-configuration-customization-for-kubernetes\/\">kustomize<\/a><\/noindex> ili <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/deepmind\/kapitan\">kapitan<\/a><\/noindex>?<\/em><\/p>\n<p><\/p>\n<p>Saznajte vi\u0161e o Shipper-u i njegovoj filozofiji u <noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/booking-com-infrastructure\/introducing-shipper-daf9244e3882\">ovom zvani\u010dnom saop\u0161tenju za medije<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Ako \u017eelite da se upustite u kod, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/bookingcom\/shipper\">posetite zvani\u010dni repozitorij projekta<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"variant-3-magicheskoe-obedinenie-klasterov\">Opcija 3: \u201emagi\u010dni\u201c spoj klastera<\/h3>\n<p><\/p>\n<p>Kubefed v2 i Shipper rade sa federacijom klastera, pru\u017eaju\u0107i klasterima nove resurse putem korisni\u010dki definisanih resursa.<\/p>\n<p><\/p>\n<p><em>Ali mo\u017eda ne \u017eelite da prepisujete sve isporuke, StatefulSets, DaemonSets i sl. za spajanje?<\/em><\/p>\n<p><\/p>\n<p><em>Kako uklju\u010diti postoje\u0107i klaster u federaciju, bez menjanja YAML-a?<\/em><\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/admiraltyio\/multicluster-scheduler\">multi-cluster-scheduler je projekat Admirality<\/a><\/noindex>, koji se bavi optere\u0107enjima raspore\u0111ivanja u klasterima.<\/p>\n<p><\/p>\n<p>Ali umesto da izmi\u0161lja novi na\u010din interakcije sa klasterom i obavija resurse u korisni\u010dke definicije, multi-cluster-scheduler se integri\u0161e u standardni \u017eivotni ciklus Kubernetes-a i presre\u0107e sve pozive koji kreiraju podove.<\/p>\n<p><\/p>\n<p><strong>Svaki kreirani pod odmah se zamenjuje prazninom.<\/strong><\/p>\n<p><\/p>\n<blockquote><p>multi-cluster-scheduler koristi <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/reference\/access-authn-authz\/extensible-admission-controllers\/\">web-hooks za modifikaciju pristupa<\/a><\/noindex>, kako bi presreo poziv i stvorio neaktivni pod-prazninu.<\/p><\/blockquote>\n<p>Izvorni pod prolazi kroz jo\u0161 jedan ciklus raspore\u0111ivanja, gde, nakon upitne federacije, donosi se odluka o sme\u0161taju.<\/p>\n<p><\/p>\n<p>Na kraju, pod se dostavlja u ciljni klaster.<\/p>\n<p><\/p>\n<p>Kao rezultat, imate dodatni pod koji ni\u0161ta ne radi, samo zauzima prostor.<\/p>\n<p><\/p>\n<p>Prednost je u tome \u0161to niste morali pisati nove resurse za spajanje isporuka.<\/p>\n<p><\/p>\n<p><strong>Svaki resurs koji stvara pod automatski je spreman za spajanje.<\/strong><\/p>\n<p><\/p>\n<p>To je zanimljivo, jer odjednom dobijate isporuke raspore\u0111ene po nekoliko regija, a niste ni primetili. Ipak, to je prili\u010dno rizi\u010dno, jer se sve ovde oslanja na magiju.<\/p>\n<p><\/p>\n<p>Ali ako Shipper nastoji prete\u017eno da ubla\u017ei posledice isporuka, multi-cluster-scheduler preuzima op\u0107enitije zadatke i verovatno je bolje prilago\u0111en za paketa zadatke.<\/p>\n<p><\/p>\n<p>Nema naprednog mehanizma postepenih isporuka.<\/p>\n<p><\/p>\n<p>Vi\u0161e o multi-cluster-scheduleru mo\u017eete saznati na <noindex>stranici zvani\u010dnog repozitorijuma.<\/noindex>.<\/p>\n<p><\/p>\n<p>Ako \u017eelite \u010ditati o multi-cluster-scheduleru u akciji, Admiralty ima <noindex><a rel=\"nofollow\" href=\"https:\/\/admiralty.io\/blog\/running-argo-workflows-across-multiple-kubernetes-clusters\/\">interesantan slu\u010daj primene sa Argom<\/a><\/noindex> \u2014 radnim procesima, doga\u0111anjima, CI i CD Kubernetes.<\/p>\n<p><\/p>\n<h3 id=\"drugie-instrumenty-i-resheniya\">Ostali alati i re\u0161enja<\/h3>\n<p><\/p>\n<p>Povezivanje vi\u0161e klastera i upravljanje njima je slo\u017een zadatak, sveobuhvatno re\u0161enje ne postoji.<\/p>\n<p><\/p>\n<p>Ako \u017eelite detaljnije istra\u017eiti ovu temu, evo nekoliko resursa:<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/submariner.io\/\">Submariner od Ranchera<\/a><\/noindex> \u2014 alat koji povezuje overlay mre\u017ee razli\u010ditih Kubernetes klastera.<\/li>\n<li>Maloprodajna mre\u017ea Target koristi <noindex><a rel=\"nofollow\" href=\"https:\/\/tech.target.com\/infrastructure\/2018\/06\/20\/enter-unimatrix.html\">Unimatrix u kombinaciji sa Spinnakerom za orkestraciju implementacije na vi\u0161e klastera.<\/a><\/noindex>.<\/li>\n<li>Poku\u0161ajte koristiti IPV6 i <noindex><a rel=\"nofollow\" href=\"https:\/\/itnext.io\/kubernetes-multi-cluster-networking-made-simple-c8f26827813\">jednu mre\u017eu u nekoliko regija.<\/a><\/noindex>.<\/li>\n<li>Mo\u017eete koristiti service mesh, na primer <noindex><a rel=\"nofollow\" href=\"https:\/\/istio.io\/docs\/setup\/kubernetes\/install\/multicluster\/\">Istio za povezivanje nekoliko klastera.<\/a><\/noindex>.<\/li>\n<li>Cilium, dodatak za mre\u017eu kontejnera, nudi <noindex><a rel=\"nofollow\" href=\"https:\/\/cilium.io\/blog\/2019\/03\/12\/clustermesh\/\">funkciju cluster mesh<\/a><\/noindex>, koja omogu\u0107ava kombinovanje vi\u0161e klastera.<\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"vot-i-vse-na-segodnya\">To je sve za danas.<\/h3>\n<p><\/p>\n<p><em>Hvala \u0161to ste pro\u010ditali do kraja!<\/em><\/p>\n<p><\/p>\n<p>Ako znate kako efikasnije povezati nekoliko klastera, <noindex><a rel=\"nofollow\" href=\"http:\/\/hello@learnk8s.io\">javite nam.<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Dodajemo va\u0161 metod k linkovima.<\/p>\n<p><\/p>\n<p>Posebna zahvalnost Krisu Nesbittu-Smitu (<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/chrisns\">Chris Nesbitt-Smith<\/a><\/noindex>) i Vincentu de Smetu (<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/so0k\">Vincent De Smet<\/a><\/noindex>) (in\u017eenjeru pouzdanosti na <noindex><a rel=\"nofollow\" href=\"https:\/\/swatmobile.io\/\">swatmobile.io<\/a><\/noindex>) za \u010ditanje \u010dlanka i deljenje korisnih informacija o tome kako funkcioni\u0161e federacija.<\/p>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/454056\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0414\u043e\u0431\u0440\u043e \u043f\u043e\u0436\u0430\u043b\u043e\u0432\u0430\u0442\u044c \u0432 \u0441\u0435\u0440\u0438\u044e \u043a\u0440\u0430\u0442\u043a\u0438\u0445 \u0440\u0443\u043a\u043e\u0432\u043e\u0434\u0441\u0442\u0432 \u043f\u043e Kubernetes. \u042d\u0442\u043e \u0440\u0435\u0433\u0443\u043b\u044f\u0440\u043d\u0430\u044f \u043a\u043e\u043b\u043e\u043d\u043a\u0430 \u0441 \u0441\u0430\u043c\u044b\u043c\u0438 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u043c\u0438 \u0432\u043e\u043f\u0440\u043e\u0441\u0430\u043c\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u044b \u043f\u043e\u043b\u0443\u0447\u0430\u0435\u043c \u043e\u043d\u043b\u0430\u0439\u043d \u0438 \u043d\u0430 \u043d\u0430\u0448\u0438\u0445 \u0442\u0440\u0435\u043d\u0438\u043d\u0433\u0430\u0445. \u041e\u0442\u0432\u0435\u0447\u0430\u0435\u0442 \u044d\u043a\u0441\u043f\u0435\u0440\u0442 \u043f\u043e Kubernetes. \u0421\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u044d\u043a\u0441\u043f\u0435\u0440\u0442 \u2014 \u0414\u0430\u043d\u0438\u044d\u043b\u044c \u041f\u043e\u043b\u0435\u043d\u0447\u0438\u043a (Daniele Polencic). \u0414\u0430\u043d\u0438\u044d\u043b\u044c \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0442\u043e\u0440\u043e\u043c \u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u043e\u043c \u041f\u041e \u0432 Learnk8s. \u0415\u0441\u043b\u0438 \u0432\u044b \u0445\u043e\u0442\u0438\u0442\u0435 \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u0441\u0432\u043e\u0439 \u0432\u043e\u043f\u0440\u043e\u0441 \u0432 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c \u043f\u043e\u0441\u0442\u0435, \u0441\u0432\u044f\u0436\u0438\u0442\u0435\u0441\u044c \u0441 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26226,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34825","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0414\u043e\u0431\u0440\u043e \u043f\u043e\u0436\u0430\u043b\u043e\u0432\u0430\u0442\u044c \u0432 \u0441\u0435\u0440\u0438\u044e.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"bs_BA\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u0430\u043a \u0441\u043e\u0435\u0434\u0438\u043d\u0438\u0442\u044c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u044b Kubernetes \u0432 \u0440\u0430\u0437\u043d\u044b\u0445 \u0434\u0430\u0442\u0430-\u0446\u0435\u043d\u0442\u0440\u0430\u0445 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0414\u043e\u0431\u0440\u043e \u043f\u043e\u0436\u0430\u043b\u043e\u0432\u0430\u0442\u044c \u0432 \u0441\u0435\u0440\u0438\u044e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:00:35+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:00:35+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kako povezati Kubernetes klastere u razli\u010ditim data centrima | ProHoster","description":"Dobrodo\u0161li u seriju.","canonical_url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"bs_BA","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u0430\u043a \u0441\u043e\u0435\u0434\u0438\u043d\u0438\u0442\u044c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u044b Kubernetes \u0432 \u0440\u0430\u0437\u043d\u044b\u0445 \u0434\u0430\u0442\u0430-\u0446\u0435\u043d\u0442\u0440\u0430\u0445 | ProHoster","og:description":"\u0414\u043e\u0431\u0440\u043e \u043f\u043e\u0436\u0430\u043b\u043e\u0432\u0430\u0442\u044c \u0432 \u0441\u0435\u0440\u0438\u044e.","og:url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/kak-soedinit-klastery-kubernetes-v-raznyh-data-tsentrah","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:00:35+00:00","article:modified_time":"2019-10-31T19:00:35+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34825","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 20:45:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:14:06","updated":"2026-01-21 20:45:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/34825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/comments?post=34825"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/34825\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media\/26226"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media?parent=34825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/categories?post=34825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/tags?post=34825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}