{"id":81130,"date":"2020-05-11T01:42:39","date_gmt":"2020-05-10T23:42:39","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo"},"modified":"2020-05-11T01:42:39","modified_gmt":"2020-05-10T23:42:39","slug":"kubernetes-open-source-protiv-vendorskogo","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo","title":{"rendered":"Kubernetes: open source proti proprietary","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><b>Ahoj, vol\u00e1m sa Dmitrij Krasnov. U\u017e viac ako p\u00e4\u0165 rokov sa zaober\u00e1m administr\u00e1ciou Kubernetes klastrov a budovan\u00edm zlo\u017eit\u00fdch mikroservisn\u00fdch architekt\u00far. Na za\u010diatku tohto roka sme spustili slu\u017ebu na spr\u00e1vu Kubernetes klastrov zalo\u017een\u00fa na Containerum. Pri tejto pr\u00edle\u017eitosti poviem, \u010do vlastne Kubernetes predstavuje a ak\u00fd je rozdiel medzi integr\u00e1ciou s dod\u00e1vate\u013eom a open source.<\/b><\/p>\n<p>Najprv, \u010do je to <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/overview\/what-is-kubernetes\/\">Kubernetes<\/a><\/noindex>. Je to syst\u00e9m na spr\u00e1vu kontajnerov na ve\u013ekom po\u010dte hostite\u013eov. Z gr\u00e9\u010dtiny sa preklad\u00e1 ako \u201epilot\u201c alebo \u201ekormideln\u00edk\u201c. P\u00f4vodne ho vyvinul Google, a potom ho ako technologick\u00fd pr\u00edspevok odovzdal Cloud Native Computing Foundation, medzin\u00e1rodnej neziskovej organiz\u00e1cii, ktor\u00e1 sp\u00e1ja popredn\u00fdch svetov\u00fdch v\u00fdvoj\u00e1rov, koncov\u00fdch pou\u017e\u00edvate\u013eov a dod\u00e1vate\u013eov kontajnerov\u00fdch technol\u00f3gi\u00ed. <\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source proti proprietary\" src=\"\/wp-content\/uploads\/2020\/05\/7cbe773adf691ad29c4aaa7a2c8f0461.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Riadi\u0165 ve\u013ek\u00e9 mno\u017estvo kontajnerov <\/h3>\n<p>\nTeraz sa pozrime na to, \u010do s\u00fa to vlastne kontajnery. Je to aplik\u00e1cia so v\u0161etk\u00fdm svoj\u00edm okol\u00edm \u2013 preva\u017ene kni\u017enicami, od ktor\u00fdch z\u00e1vis\u00ed funkcia programu. To v\u0161etko je zabalen\u00e9 do arch\u00edvov a prezentovan\u00e9 vo forme obrazu, ktor\u00fd je mo\u017en\u00e9 sp\u00fa\u0161\u0165a\u0165 nez\u00e1visle od opera\u010dn\u00e9ho syst\u00e9mu, testova\u0165 a nielen to. Ale existuje probl\u00e9m \u2013 riadi\u0165 kontajnery na ve\u013ekom po\u010dte hostite\u013eov je ve\u013emi zlo\u017eit\u00e9. Preto bol vytvoren\u00fd Kubernetes. <\/p>\n<p>Obraz kontajnera predstavuje aplik\u00e1ciu plus jej z\u00e1vislosti. Aplik\u00e1cia, jej z\u00e1vislosti a obraz s\u00faborov\u00e9ho syst\u00e9mu OS s\u00fa umiestnen\u00e9 v r\u00f4znych \u010dastiach obrazu, takzvan\u00fdch vrstv\u00e1ch. Vrstvy sa m\u00f4\u017eu op\u00e4tovne pou\u017e\u00edva\u0165 pre r\u00f4zne kontajnery. Napr\u00edklad, pre v\u0161etky aplik\u00e1cie v spolo\u010dnosti m\u00f4\u017ee by\u0165 pou\u017eit\u00e1 z\u00e1kladn\u00e1 vrstva Ubuntu. Pri sp\u00fa\u0161\u0165an\u00ed kontajnerov nie je potrebn\u00e9 uchov\u00e1va\u0165 na hostite\u013eovi mno\u017estvo k\u00f3pi\u00ed jednej z\u00e1kladnej vrstvy. To umo\u017e\u0148uje optimalizova\u0165 spracovanie a dodanie obrazov.<\/p>\n<p>Ke\u010f chceme spusti\u0165 aplik\u00e1ciu z kontajnera, potrebn\u00e9 vrstvy sa navz\u00e1jom ukladaj\u00fa a vytv\u00e1ra sa prekr\u00fdvac\u00ed s\u00faborov\u00fd syst\u00e9m. Zhora sa prid\u00e1va vrstva na z\u00e1pis, ktor\u00e1 sa pri zastaven\u00ed kontajnera odstr\u00e1ni. To zaru\u010duje, \u017ee pri spusten\u00ed kontajnera m\u00e1 aplik\u00e1cia v\u017edy rovnak\u00e9 prostredie, ktor\u00e9 nemo\u017eno zmeni\u0165. To zaru\u010duje reprodukovate\u013enos\u0165 prostredia na r\u00f4znych hos\u0165uj\u00facich opera\u010dn\u00fdch syst\u00e9moch. Nech je to Ubuntu alebo CentOS, \u2013 prostredie bude v\u017edy rovnak\u00e9. Okrem toho je kontajner izolovan\u00fd od hostite\u013ea pomocou mechanizmov zabudovan\u00fdch v jadre Linuxu. Aplik\u00e1cie v kontajneri nevidia s\u00fabory, procesy hostite\u013ea a susedn\u00fdch kontajnerov. Tak\u00e1to izol\u00e1cia aplik\u00e1ci\u00ed od hostite\u013esk\u00e9ho opera\u010dn\u00e9ho syst\u00e9mu poskytuje dodato\u010dn\u00fa vrstvu zabezpe\u010denia. <\/p>\n<p>Na spr\u00e1vu kontajnerov na hostite\u013eovi existuje mno\u017estvo n\u00e1strojov. Najpopul\u00e1rnej\u0161\u00ed z nich je Docker. Umo\u017e\u0148uje zabezpe\u010di\u0165 cel\u00fd \u017eivotn\u00fd cyklus pr\u00e1ce kontajnerov. Av\u0161ak funguje iba na jednom hostite\u013eovi. Pri potrebe spr\u00e1vy kontajnerov na viacer\u00fdch hostite\u013eoch m\u00f4\u017ee Docker obr\u00e1ti\u0165 \u017eivot in\u017einierov na peklo. Preto bol vytvoren\u00fd Kubernetes.<\/p>\n<p>Dopyt po Kubernetes je pr\u00e1ve ur\u010den\u00fd mo\u017enos\u0165ou riadi\u0165 skupiny kontajnerov na viacer\u00fdch hostite\u013eoch ako nejak\u00e9 jednotn\u00e9 entity. Popularita syst\u00e9mu zabezpe\u010duje mo\u017enos\u0165 vytvori\u0165 DevOps alebo Development Operations, v ktor\u00fdch sa Kubernetes pou\u017e\u00edva na sp\u00fa\u0161\u0165anie procesov tohto DevOps.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source proti proprietary\" src=\"\/wp-content\/uploads\/2020\/05\/40f253f4445595376231bb384253763d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Obr\u00e1zok 1. Sch\u00e9matick\u00e9 zobrazenie princ\u00edpu fungovania Kubernetes<\/i><\/p>\n<h3>\u00dapln\u00e1 automatiz\u00e1cia<\/h3>\n<p>\nDevOps predstavuje v podstate automatiz\u00e1ciu procesu v\u00fdvoja. Jednoducho povedan\u00e9, v\u00fdvoj\u00e1ri p\u00ed\u0161u k\u00f3d, ktor\u00fd sa nahr\u00e1va do repozit\u00e1ra. N\u00e1sledne sa tento k\u00f3d m\u00f4\u017ee automaticky zostavi\u0165 priamo do kontajnera so v\u0161etk\u00fdmi kni\u017enicami, testova\u0165 a \u201evyd\u00e1va\u0165\u201c na \u010fal\u0161iu etapu \u2013 Staging a potom rovno na Production.<\/p>\n<p>Spolu s Kubernetes DevOps umo\u017e\u0148uje automatizova\u0165 tento proces, aby prebiehal prakticky bez \u00fa\u010dasti samotn\u00fdch v\u00fdvoj\u00e1rov. V\u010faka tomu sa v\u00fdrazne zr\u00fdch\u013euje zostavovanie, preto\u017ee v\u00fdvoj\u00e1r sa nemus\u00ed zaobera\u0165 touto \u00falohou na svojom po\u010d\u00edta\u010di \u2014 jednoducho nap\u00ed\u0161e kus k\u00f3du, nahr\u00e1 k\u00f3d do repozit\u00e1ra a spust\u00ed sa pipeline, ktor\u00e1 m\u00f4\u017ee zah\u0155\u0148a\u0165 proces zostavovania, testovania a nasadzovania. A to sa deje pri ka\u017edom commite, preto testovanie prebieha nepretr\u017eite.<\/p>\n<p>Navy\u0161e pou\u017eitie kontajnera umo\u017e\u0148uje ma\u0165 istotu, \u017ee cel\u00e9 prostredie tejto aplik\u00e1cie p\u00f4jde do produkcie presne v takej podobe, v akej bolo testovan\u00e9. Teda nevznikn\u00fa \u017eiadne probl\u00e9my typu \u201ena teste boli in\u00e9 verzie, v produkcii \u2013 in\u00e9, a ke\u010f sme ich nasadili \u2013 v\u0161etko spadlo\u201c. A ke\u010f\u017ee dnes m\u00e1me trend na mikroslu\u017ebov\u00fa architekt\u00faru, pri ktorej namiesto jedn\u00e9ho obrovsk\u00e9ho aplika\u010dn\u00e9ho celku existuj\u00fa stovky mal\u00fdch, na to, aby sme ich spravovali ru\u010dne, by sme potrebovali obrovsk\u00fd po\u010det zamestnancov. Preto pou\u017e\u00edvame Kubernetes.<\/p>\n<p><b><\/p>\n<h3>V\u00fdhody, v\u00fdhody, v\u00fdhody<\/h3>\n<p><\/b><br \/>\nAk hovor\u00edme o prednostiach Kubernetes ako platformy, m\u00e1 v\u00fdznamn\u00e9 v\u00fdhody z h\u013eadiska spr\u00e1vy mikroslu\u017ebovej architekt\u00fary. <\/p>\n<ul>\n<li> <b>Spr\u00e1va mnoh\u00fdch replik.<\/b> Najd\u00f4le\u017eitej\u0161ie je spravova\u0165 kontajnery na viacer\u00fdch hostite\u013eoch. A \u010do je d\u00f4le\u017eitej\u0161ie \u2014 spr\u00e1va mno\u017estva replik aplik\u00e1ci\u00ed v kontajneroch ako jednej entity. V\u010faka tomu sa in\u017einierom nemus\u00ed stara\u0165 o ka\u017ed\u00fd jednotliv\u00fd kontajner. Ak jeden z kontajnerov spadne, Kubernetes to zist\u00ed a znovu ho spust\u00ed. <\/li>\n<li> <b>Klastrov\u00e1 sie\u0165.<\/b> Kubernetes m\u00e1 tie\u017e takzvan\u00fa klastrov\u00fa sie\u0165 s vlastn\u00fdm adresn\u00fdm priestorom. V\u010faka tomu m\u00e1 ka\u017ed\u00fd pod svoju adresu. Podom sa rozumie minim\u00e1lna \u0161truktur\u00e1lna jednotka klastra, v ktorej sa priamo sp\u00fa\u0161\u0165aj\u00fa kontajnery. Navy\u0161e Kubernetes m\u00e1 funkciu, ktor\u00e1 kombinuje load balancer a Service Discovery. To umo\u017e\u0148uje zbavi\u0165 sa ru\u010dn\u00e9ho riadenia IP adresami a prenies\u0165 t\u00fato \u00falohu na Kubernetes. A automatick\u00e9 health checky pom\u00f4\u017eu odhali\u0165 probl\u00e9my a presmerova\u0165 prev\u00e1dzku na funguj\u00face pody.<\/li>\n<li> <b>Spr\u00e1va konfigur\u00e1ci\u00ed. <\/b>Spr\u00e1va ve\u013ek\u00e9ho po\u010dtu aplik\u00e1ci\u00ed komplikuje riadenie konfigur\u00e1cie aplik\u00e1ci\u00ed. Na tento \u00fa\u010del m\u00e1 Kubernetes \u0161peci\u00e1lne prostriedky ConfigMap. Tieto prostriedky umo\u017e\u0148uj\u00fa centralizovan\u00e9 uchov\u00e1vanie konfigur\u00e1ci\u00ed a ich vkladanie do podov pri sp\u00fa\u0161\u0165an\u00ed aplik\u00e1ci\u00ed. Tak\u00fdto mechanizmus zaru\u010duje konzistentnos\u0165 konfigur\u00e1cie, \u010di u\u017e je v desiatich alebo stovk\u00e1ch replik\u00e1ci\u00ed aplik\u00e1ci\u00ed. <\/li>\n<li> <b>Trval\u00e9 objemy. <\/b>Kontajnery s\u00fa vo svojej podstate nemenn\u00e9 a pri zastaven\u00ed kontajnera bud\u00fa v\u0161etky d\u00e1ta zap\u00edsan\u00e9 do s\u00faborov\u00e9ho syst\u00e9mu zni\u010den\u00e9. Av\u0161ak niektor\u00e9 aplik\u00e1cie uchov\u00e1vaj\u00fa d\u00e1ta priamo na disku. Na rie\u0161enie tohto probl\u00e9mu m\u00e1 Kubernetes funkciu spr\u00e1vy diskov\u00e9ho \u00falo\u017eiska \u2013 trval\u00e9 objemy. Tento mechanizmus vyu\u017e\u00edva extern\u00e9 \u00falo\u017eisko pre d\u00e1ta a m\u00f4\u017ee pren\u00e1\u0161a\u0165 trval\u00e9 \u00falo\u017eisko, blokov\u00e9 alebo s\u00faborov\u00e9, do kontajnerov. Toto rie\u0161enie umo\u017e\u0148uje uchov\u00e1va\u0165 d\u00e1ta oddelene od pracovn\u00edkov, \u010do ich chr\u00e1ni v pr\u00edpade poruchy t\u00fdchto pracovn\u00edkov.<\/li>\n<li> <b>Vyrovn\u00e1va\u010d z\u00e1\u0165a\u017ee.<\/b> Napriek tomu, \u017ee v Kubernetes riadime abstraktn\u00e9 entity ako Deployment, StatefulSet a pod., v kone\u010dnom d\u00f4sledku s\u00fa kontajnery sp\u00fa\u0161\u0165an\u00e9 na oby\u010dajn\u00fdch <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sk\/vps\/abuzoustojchivye-vps\/\"   title=\"virtu\u00e1lnych strojoch\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"4246\">virtu\u00e1lnych strojoch<\/a> alebo fyzick\u00fdch serveroch. Nie s\u00fa dokonal\u00e9 a m\u00f4\u017eu sa kedyko\u013evek zr\u00fati\u0165. Kubernetes to zaznamen\u00e1 a presmeruje vn\u00fatorn\u00fd prenos na in\u00e9 repliky. Ale \u010do robi\u0165 s prenosom, ktor\u00fd prich\u00e1dza zvonku? Ak by sme jednoducho presmerovali prenos na jedn\u00e9ho z pracovn\u00edkov, \u010do sa stane, ak sa zr\u00fati, slu\u017eba sa stane nedostupnou. Na rie\u0161enie tohto probl\u00e9mu m\u00e1 Kubernetes slu\u017eby typu Load Balancer. Tieto slu\u017eby s\u00fa ur\u010den\u00e9 na automatick\u00fa konfigur\u00e1ciu vonkaj\u0161ieho cloudov\u00e9ho vyrovn\u00e1va\u010da za\u0165a\u017eenia pre v\u0161etk\u00fdch pracovn\u00edkov v klastri. Tento vonkaj\u0161\u00ed vyrovn\u00e1va\u010d pren\u00e1\u0161a vonkaj\u0161\u00ed prenos na pracovn\u00edkov a s\u00e1m sleduje ich stav. Ak sa jeden alebo viac pracovn\u00edkov stan\u00fa nedostupn\u00fdmi, pren\u00e1\u0161a sa prenos na in\u00e9. To umo\u017e\u0148uje vytv\u00e1ra\u0165 vysoko dostupn\u00e9 slu\u017eby pomocou Kubernetes.<\/li>\n<\/ul>\n<p>\nKubernetes najlep\u0161ie preukazuje svoju hodnotu pr\u00e1ve pri sp\u00fa\u0161\u0165an\u00ed mikroslu\u017ebovej architekt\u00fary. Zavedenie syst\u00e9mu do klasickej architekt\u00fary je mo\u017en\u00e9, ale nezmyseln\u00e9. Ak aplik\u00e1cia nem\u00f4\u017ee fungova\u0165 v nieko\u013ek\u00fdch replik\u00e1ch, ak\u00fd je rozdiel, \u010di u\u017e ide o Kubernetes, alebo nie?<\/p>\n<p><b><\/p>\n<h3>Open source Kubernetes<\/h3>\n<p><\/b><br \/>\nOpen source Kubernetes \u2013 skvel\u00e1 vec: nain\u0161talujete a funguje. M\u00f4\u017eete ho nasadi\u0165 na vlastn\u00e9 servery, na svojej infra\u0161trukt\u00fare, nain\u0161talova\u0165 mastera a workery, na ktor\u00fdch bud\u00fa spusten\u00e9 v\u0161etky aplik\u00e1cie. A najd\u00f4le\u017eitej\u0161ie \u2013 to v\u0161etko je zadarmo. Av\u0161ak s\u00fa tu nuansy.<\/p>\n<ul>\n<li> Prv\u00fd \u2013 po\u017eiadavky na vedomosti a sk\u00fasenosti administr\u00e1torov a in\u017einierov, ktor\u00ed to v\u0161etko bud\u00fa rozv\u00edja\u0165 a udr\u017eiava\u0165. Ke\u010f\u017ee klient dost\u00e1va pln\u00fa slobodu v klastre, zodpovednos\u0165 za jeho funk\u010dnos\u0165 nesie s\u00e1m. A je ve\u013emi jednoduch\u00e9 v\u0161etko pokazi\u0165.<\/li>\n<li> Druh\u00fd \u2013 nedostatok integr\u00e1ci\u00ed. Ak spust\u00edte Kubernetes bez nejakej popul\u00e1rnej virtualiza\u010dnej platformy, nez\u00edskate v\u0161etky v\u00fdhody programu. Ako napr\u00edklad vyu\u017e\u00edvanie Persistent Volumes a Load balancer slu\u017eieb.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Kubernetes: open source proti proprietary\" src=\"\/wp-content\/uploads\/2020\/05\/8445e46889ca4c4d53bd91abeaa49256.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Obr\u00e1zok 2. Architekt\u00fara k8s<\/i><\/p>\n<p><b><\/p>\n<h3>Kubernetes od dod\u00e1vate\u013ea<\/h3>\n<p><\/b><br \/>\nIntegr\u00e1cia s cloudov\u00fdm poskytovate\u013eom pon\u00faka dve mo\u017enosti: <\/p>\n<ul>\n<li> Po prv\u00e9, \u010dlovek m\u00f4\u017ee jednoducho stla\u010di\u0165 tla\u010didlo \u201evytvori\u0165 klaster\u201c a z\u00edska\u0165 u\u017e nastaven\u00fd a pripraven\u00fd klaster.<\/li>\n<li> Po druh\u00e9, dod\u00e1vate\u013e s\u00e1m nain\u0161taluje klaster a nastav\u00ed integr\u00e1ciu s cloudom.<\/li>\n<\/ul>\n<p>\nAko to funguje u n\u00e1s. In\u017einier, ktor\u00fd sp\u00fa\u0161\u0165a klaster, uv\u00e1dza, ko\u013eko potrebuje workerov a s ak\u00fdmi parametrami (napr\u00edklad 5 workerov, ka\u017ed\u00fd s 10 CPU, 16 GB RAM a povedzme 100 GB disku). Potom z\u00edska pr\u00edstup do u\u017e vytvoren\u00e9ho klastru. Pri tom workery, na ktor\u00fdch sa sp\u00fa\u0161\u0165a z\u00e1\u0165a\u017e, s\u00fa plne odovzdan\u00e9 klientovi, ale cel\u00e1 spr\u00e1va zost\u00e1va v z\u00f3ne zodpovednosti dod\u00e1vate\u013ea (v pr\u00edpade, \u017ee slu\u017eba sa poskytuje pod\u013ea modelu spravovan\u00fdch slu\u017eieb).<\/p>\n<p>Av\u0161ak tento model m\u00e1 svoje nev\u00fdhody. Preto\u017ee spr\u00e1va zost\u00e1va u dod\u00e1vate\u013ea, ned\u00e1va dod\u00e1vate\u013e klientovi pln\u00fd pr\u00edstup, \u010do zni\u017euje flexibilitu pri pr\u00e1ci s Kubernetes. Niekedy sa st\u00e1va, \u017ee klient chce pripoji\u0165 k Kubernetes nejak\u00fa \u0161pecifick\u00fa funkcionalitu, napr\u00edklad autentifik\u00e1ciu cez LDAP, ale konfigur\u00e1cia mana\u017ementu to neumo\u017e\u0148uje.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source proti proprietary\" src=\"\/wp-content\/uploads\/2020\/05\/e5cff16e4280cf041917c886c146a2d0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Obr\u00e1zok 3. Pr\u00edklad Kubernetes klastra od cloudov\u00e9ho poskytovate\u013ea<\/i><\/p>\n<p><b><\/p>\n<h3>\u010co si vybra\u0165: open source alebo poskytovate\u013esk\u00fd<\/h3>\n<p><\/b><br \/>\nTak\u017ee, open source Kubernetes alebo vendorov\u00fd? Ak zoberieme open source Kubernetes, pou\u017e\u00edvate\u013e m\u00f4\u017ee robi\u0165, \u010do chce. Ale je tu ve\u013ek\u00e1 \u0161anca, \u017ee si s\u00e1m vystrel\u00ed do nohy. S vendorov\u00fdm je to zlo\u017eitej\u0161ie, preto\u017ee v\u0161etko je premyslen\u00e9 a nastaven\u00e9. Najv\u00e4\u010d\u0161\u00edm nedostatkom open source Kubernetes je po\u017eiadavka na odborn\u00edkov. S vendorov\u00fdm je spolo\u010dnos\u0165 zbaven\u00e1 tejto bolesti hlavy, ale mus\u00ed sa rozhodn\u00fa\u0165: plati\u0165 svojim odborn\u00edkom alebo vendorovi.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes: open source proti proprietary\" src=\"\/wp-content\/uploads\/2020\/05\/f14130c42049e20b2f33121e4d789cca.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<img decoding=\"async\" alt=\"Kubernetes: open source proti proprietary\" src=\"\/wp-content\/uploads\/2020\/05\/4fb1feaacd42a67a444ae1600e37d0f0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNu\u017e, klady s\u00fa zrejm\u00e9, z\u00e1pory tie\u017e zn\u00e1me. Nezmenn\u00e9 je jedno: Kubernetes rie\u0161i mno\u017estvo probl\u00e9mov, automatizuje spr\u00e1vu mnoh\u00fdch kontajnerov. A ktor\u00fd si vybra\u0165, open source alebo vendorov\u00fd, si ka\u017ed\u00fd rozhoduje s\u00e1m.<\/p>\n<p><i>\u010cl\u00e1nok pripravil Dmitrij Krasnov, ved\u00faci architekt slu\u017eby Containerum poskytovate\u013ea #CloudMTS. <\/i><br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ru_mts\/blog\/500728\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440. \u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u044d\u0442\u043e\u0433\u043e \u0433\u043e\u0434\u0430 \u043c\u044b \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0441\u0435\u0440\u0432\u0438\u0441 \u043f\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044e \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430\u043c\u0438 Kubernetes \u043d\u0430 \u0431\u0430\u0437\u0435 Containerum. \u041f\u043e\u043b\u044c\u0437\u0443\u044f\u0441\u044c \u043f\u043e\u0432\u043e\u0434\u043e\u043c \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u043e\u0431\u043e\u0439 \u044d\u0442\u043e\u0442 \u0441\u0430\u043c\u044b\u0439 Kubernetes \u0438 \u0447\u0435\u043c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u044f \u0441 \u0432\u0435\u043d\u0434\u043e\u0440\u043e\u043c \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u043e\u0442 open source. \u0414\u043b\u044f \u043d\u0430\u0447\u0430\u043b\u0430, \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":81131,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-81130","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.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440.\" \/>\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\/sk\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\udd47Kubernetes: open source \u043f\u0440\u043e\u0442\u0438\u0432 \u0432\u0435\u043d\u0434\u043e\u0440\u0441\u043a\u043e\u0433\u043e | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo\" \/>\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=\"2020-05-10T23:42:39+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-10T23:42:39+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\udd47Kubernetes: open source proti vendorov\u00e9mu | ProHoster","description":"Ahoj, vol\u00e1m sa Dmitrij Krasnov. U\u017e viac ako p\u00e4\u0165 rokov sa zaober\u00e1m administr\u00e1ciou klastrov Kubernetes a budovan\u00edm komplexn\u00fdch mikroslu\u017ebov\u00fdch architekt\u00far.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\udd47Kubernetes: open source \u043f\u0440\u043e\u0442\u0438\u0432 \u0432\u0435\u043d\u0434\u043e\u0440\u0441\u043a\u043e\u0433\u043e | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442, \u043c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0414\u043c\u0438\u0442\u0440\u0438\u0439 \u041a\u0440\u0430\u0441\u043d\u043e\u0432. \u0423\u0436\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes \u0438 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u0435\u043c \u0441\u043b\u043e\u0436\u043d\u044b\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0445 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-open-source-protiv-vendorskogo","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":"2020-05-10T23:42:39+00:00","article:modified_time":"2020-05-10T23:42:39+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"81130","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 16:04:23","updated":"2022-09-27 22:17:56","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/81130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=81130"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/81130\/revisions"}],"predecessor-version":[{"id":164121,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/81130\/revisions\/164121"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/81131"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=81130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=81130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=81130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}