{"id":54069,"date":"2019-12-17T00:00:00","date_gmt":"2019-12-16T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/kubernetes-eto-novyj-linux-intervyu-s-pavlom-selivanovym"},"modified":"2020-02-18T14:02:02","modified_gmt":"2020-02-18T11:02:02","slug":"kubernetes-eto-novyj-linux-intervyu-s-pavlom-selivanovym","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-eto-novyj-linux-intervyu-s-pavlom-selivanovym","title":{"rendered":"Kubernetes \u2014 je to nov\u00fd Linux? Rozhovor s Pavlom Selivanovom","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\r\n \"Prehrajte\r\n
<\/div>\r\n <\/div><\/center>
\nPreklad:
\nAzat Khadiev: Dobr\u00fd de\u0148. Vol\u00e1m sa Azat Khadiev. Som v\u00fdvoj\u00e1r v oblasti PaaS spolo\u010dnosti Mail.ru Cloud Solutions. So mnou je tu Pavel Selivanov z firmy Southbridge. Nach\u00e1dzame sa na konferencii DevOpsDays. Tam bude predn\u00e1\u0161a\u0165 o tom, ako je mo\u017en\u00e9 vybudova\u0165 DevOps s Kubernetes, ale pravdepodobne sa v\u00e1m to nepodar\u00ed. Pre\u010do tak\u00e1 pesimistick\u00e1 t\u00e9ma?
\n<\/a><\/noindex>
\nPavel Selivanov: V skuto\u010dnosti nie je pesimistick\u00e1. Hovor\u00ed o tom, \u017ee mnoh\u00e9 probl\u00e9my v na\u0161ej komunite sa sna\u017e\u00edme rie\u0161i\u0165 pomocou technol\u00f3gi\u00ed. A sna\u017e\u00edme sa ich rie\u0161i\u0165 pomerne jednostranne. Kubernetes je rovnak\u00e1 vec \u2014 je to nie\u010do, za \u010do s\u00fa zodpovedn\u00ed, d\u00e1 sa poveda\u0165, \u017ee Ops. Ale m\u00e1me skvel\u00fd pojem DevOps in\u017einier. Ten je zodpovedn\u00fd za Kubernetes. Pri tom\u2026 Akoby ste mali spravi\u0165 Kubernetes, ale Dev chlapci nemaj\u00fa v\u00f4bec preh\u013ead o v\u0161etk\u00fdch t\u00fdch kubernetesoch, ani netu\u0161ia, \u010do m\u00f4\u017ee robi\u0165 \u2014 a pre nich v\u0161etko funguje presne tak isto. A to v\u0161etko aj napriek tomu, \u017ee Kubernetes obsahuje pripraven\u00e9 rie\u0161enia, hotov\u00e9 n\u00e1stroje na to, aby sme s touto technol\u00f3giou roz\u0161\u00edrili tento DevOps pr\u00edstup, komunik\u00e1ciu medzi Dev a Ops. T\u00fato mo\u017enos\u0165 ve\u013emi m\u00e1lo vyu\u017e\u00edvame. T\u00fdm, \u017ee dokonca s\u00fa\u010dasn\u00e9 \u0161trukt\u00fary prev\u00e1dzame na v\u0161etky tieto n\u00e1stroje DevOps \u2014 Docker, Kubernetes, cloud a tak \u010falej \u2014 situ\u00e1ciu len zhor\u0161ujeme. A n\u00e1stroje za\u010d\u00edname pou\u017e\u00edva\u0165 nie tak, ako boli zam\u00fd\u0161\u013ean\u00e9. A okolo v\u0161etk\u00fdch t\u00fdchto technol\u00f3gi\u00ed sa vytv\u00e1raj\u00fa len stra\u0161n\u00e9 kr\u00ed\u017ee. <\/p>\n

Azat Khadiev: Ch\u00e1pe\u0161. Je c\u00edti\u0165, \u017ee t\u00e9ma je rozsiahla. Ako si mysl\u00ed\u0161, ak\u00fd je najroz\u0161\u00edrenej\u0161\u00ed probl\u00e9m spolo\u010dnost\u00ed teraz? S Kubernetes.<\/p>\n

Pavel Selivanov: Najroz\u0161\u00edrenej\u0161\u00ed probl\u00e9m s Kubernetes \u2014 je to nedostatok kompetenci\u00ed. V IT je to be\u017en\u00fd probl\u00e9m. V\u017edy ch\u00fdbaj\u00fa odborn\u00edci. V\u017edy ch\u00fdbaj\u00fa kompetencie. A teraz s Kubernetes kompetenci\u00ed ch\u00fdba. A pritom existuj\u00fa stoprocentne pripraven\u00e9 rie\u0161enia na trhu, ktor\u00e9 by umo\u017enili z\u00edska\u0165 Kubernetes, ale pritom nemaj\u00fa potrebn\u00e9 kompetencie, t\u00fdch je na trhu otvorene m\u00e1lo. A tie, ktor\u00e9 s\u00fa, vyvol\u00e1vaj\u00fa ot\u00e1zky. Neust\u00e1le h\u013ead\u00e1me \u013eud\u00ed, ktor\u00ed sa v Kubernetes vyznaj\u00fa. Sna\u017e\u00edme sa vyvin\u00fa\u0165 pod to. <\/p>\n

Azat Khadiev: A vzh\u013eadom na s\u00fa\u010dasn\u00fd nedostatok zamestnancov v IT, ktor\u00fd tu v\u017edy bol a st\u00e1le je, ako si mysl\u00ed\u0161, \u017ee sa d\u00e1 v tak\u00fdchto podmienkach \u017ei\u0165? Ak\u00e9 s\u00fa nejak\u00e9 tipy na pre\u017eitie? <\/p>\n

Pavel Selivanov: Tipy na pre\u017eitie. Po prv\u00e9, z poh\u013eadu cloudu to vyzer\u00e1 takto \u2014 odovzdajte n\u00e1m \u010das\u0165 svojich kompetenci\u00ed. My si ich vezmeme a budeme s nimi pracova\u0165 intern\u00e9. To je v poriadku. Okrem toho je d\u00f4le\u017eit\u00e9, aby t\u00ed, ktor\u00ed to pou\u017e\u00edvaj\u00fa, pochopili\u2026 Je to skuto\u010dne skvel\u00fd okamih\u2026 Ale je d\u00f4le\u017eit\u00e9 ch\u00e1pa\u0165, \u017ee ak odovzd\u00e1vate \u010das\u0165 svojich kompetenci\u00ed do cloudu alebo poskytovate\u013eovi, dost\u00e1vame univerz\u00e1lne rie\u0161enie. Jednoducho povedan\u00e9, m\u00e1me datab\u00e1zu, ktor\u00e1 vykon\u00e1va ve\u013emi \u0161pecifick\u00e9 \u00falohy a bola ve\u013emi \u0161pecificky nastaven\u00e1. Ak t\u00fato datab\u00e1zu d\u00e1me do cloudu, m\u00f4\u017eeme samozrejme prepusti\u0165 administr\u00e1tora, ktor\u00fd sa predt\u00fdm zaoberal datab\u00e1zov\u00fdmi klastrami \u2014 to ist\u00e9 urob\u00ed Amazon alebo Google za n\u00e1s. Ale z\u00e1rove\u0148 n\u00e1m Amazon alebo Google nedovolia presne nastavi\u0165 na\u0161u datab\u00e1zu. Ve\u013ek\u00e9 projekty a spolo\u010dnosti sa v ka\u017edom pr\u00edpade dostan\u00fa do bodu, ke\u010f v nejakom okamihu svojho \u017eivota vyu\u017e\u00edvaj\u00fa cloudov\u00e9 rie\u0161enia, a potom sa v ka\u017edom pr\u00edpade vracaj\u00fa sp\u00e4\u0165 k tomu, aby si prevzali svoje kompetencie, preto\u017ee potrebuj\u00fa nie\u010do \u0161pecifickej\u0161ie.<\/p>\n

Azat Khadiev: S\u00fa univerz\u00e1lne rie\u0161enia zl\u00e9, alebo mo\u017eno na ich z\u00e1klade postavi\u0165 viac? <\/p>\n

Pavel Selivanov: Nie, univerz\u00e1lne rie\u0161enia ur\u010dite nie s\u00fa zl\u00e9. Univerz\u00e1lne rie\u0161enia s\u00fa dobr\u00e9. Len univerz\u00e1lne rie\u0161enia \u2026 s\u00fa univerz\u00e1lne. Je d\u00f4le\u017eit\u00e9 to pochopi\u0165. Je to ako vzia\u0165 spolo\u010dn\u00fd skript\u2026 Ak okolo tohto spolo\u010dn\u00e9ho skriptu, vykon\u00e1vaj\u00faceho v\u0161eobecn\u00e9 \u00falohy, dok\u00e1\u017ee cel\u00fa logiku fungovania spolo\u010dnosti postavi\u0165 \u2014 to je skvel\u00e9. Ale ak je logika pr\u00e1ce in\u00e1 a vezme\u0161 toto univerz\u00e1lne rie\u0161enie, univerz\u00e1lny skript \u2014 a za\u010dne\u0161 ho prisp\u00f4sobova\u0165, to je zl\u00e9. Ale v samotnom univerzalizme nie je ni\u010d zl\u00e9. <\/p>\n

Azat Khadiev: Ak m\u00e1\u0161 administr\u00e1tora, probl\u00e9m nie je v jeho prepusten\u00ed. M\u00f4\u017ee jednoducho robi\u0165 viac. <\/p>\n

Pavel Selivanov: \u00c1no, odstr\u00e1ni\u0165 od neho rutinn\u00fa pr\u00e1cu a odovzda\u0165 ju niekomu in\u00e9mu, aby to robil tam. To je bezpochyby dobr\u00fd pr\u00edstup. D\u00f4le\u017eit\u00e1 vec je, \u010di toto \u0161tandardn\u00e9 rie\u0161enie vyhovuje konkr\u00e9tnemu pr\u00edpadu. <\/p>\n

Azat Khadiev: Z vlastnej sk\u00fasenosti vid\u00edm, \u017ee mnoh\u00e9 spolo\u010dnosti sa zaoberaj\u00fa rovnak\u00fdmi vecami. Nastavuj\u00fa Kubernetes klastre a prem\u00fd\u0161\u013eaj\u00fa o ich \u0161k\u00e1lovan\u00ed. V\u0161etky tieto oper\u00e1cie s\u00fa ve\u013emi opakuj\u00face sa. <\/p>\n

Pavel Selivanov: \u00c1no, ur\u010dite. Navy\u0161e, ak vezmeme konkr\u00e9tne Kubernetes, je tu tak\u00fd aspekt, \u017ee hlbok\u00fdch a dobr\u00fdch znalost\u00ed o Kubernetes je moment\u00e1lne na trhu naozaj m\u00e1lo. Kubernetes je obrovsk\u00fd stavebnicov\u00fd syst\u00e9m a ak ho zav\u00e1dzate do spolo\u010dnosti, bu\u010fte pripraven\u00ed na to, \u017ee s n\u00edm pr\u00eddete aj s in\u017einierom, ktor\u00fd sa tomu bude na pln\u00fd \u00fav\u00e4zok venova\u0165. A to je drah\u00e9. A tak\u00e9ho in\u017einiera e\u0161te len sk\u00faste n\u00e1js\u0165. Pokia\u013e hovor\u00edm o sebe, nem\u00e1m ve\u013emi r\u00e1d cloudov\u00e9 rie\u0161enia, preto\u017ee dobre a hlboko rozumiem fungovaniu Kubernetes. A v cloude mi \u010dasto ch\u00fdba ur\u010dit\u00e1 funk\u010dnos\u0165, ktor\u00fa si \u017eiadam \u2014 a povedia mi \u201eNie, to nie je mo\u017en\u00e9\u201c. No, v takom pr\u00edpade sa ospravedl\u0148ujem, ale dok\u00e1\u017eem to robi\u0165 lep\u0161ie ako cloud. Ale ak nem\u00e1te in\u017einiera na pln\u00fd \u00fav\u00e4zok a nem\u00e1te z\u00e1ujem plati\u0165 za tohto in\u017einiera, ktor\u00fd spravuje Kubernetes, a st\u00e1le mu plat\u00edte ve\u013ea pe\u0148az\u00ed len na experimentovanie, tak cloud je skuto\u010dne skvel\u00e9 rie\u0161enie. Preto\u017ee tam aspo\u0148 pracuj\u00fa \u013eudia, ktor\u00fdch si poskytovate\u013e u\u017e najal. A rozumej\u00fa tomu, \u010do robia. A z\u00e1kladn\u00e9 veci, ktor\u00e9 potrebujete na ka\u017edodenn\u00fd z\u00e1klad, s\u00fa tam.<\/p>\n

Azat Khadiev: \u010co si mysl\u00ed\u0161 o s\u00fa\u010dasnom stave Kubernetes? \u010co s n\u00edm bude za p\u00e4\u0165 a za desa\u0165 rokov?<\/p>\n

Pavol Selivanov: Dobr\u00fd ot\u00e1zka. Viem, \u010do sa u n\u00e1s deje v komunite oh\u013eadom toho. Niektor\u00ed \u013eudia veria, \u017ee okrem Kubernetes ni\u010d nezostane. Situ\u00e1cia, ktor\u00e1 sa u\u017e d\u00e1vno stala s Linuxom. To znamen\u00e1, \u017ee mimo Linuxu s\u00fa \u013eudia, ktor\u00ed \u017eij\u00fa na BSD, pravdepodobne s ve\u013emi \u0161pecifick\u00fdmi \u00falohami. S\u00fa aj \u013eudia, ktor\u00ed pracuj\u00fa na Windows \u2014 windows servery \u2014 pravdepodobne maj\u00fa tie\u017e \u0161pecifick\u00e9 \u00falohy, alebo jednoducho maj\u00fa kompetenciu v tejto oblasti a nie s\u00fa pripraven\u00ed od\u00eds\u0165. V ka\u017edom pr\u00edpade je \u0161tandardom v na\u0161ej sf\u00e9re Linux. Existuje n\u00e1zor, \u017ee Kubernetes sa stane tak\u00fdm ist\u00fdm de facto \u0161tandardom, a okrem Kubernetes ni\u010d in\u00e9ho nebude. Kubernetes bude spravova\u0165 nielen aplik\u00e1cie, ich nasadenie, deploy, \u0161k\u00e1lovanie. Vlastne v\u0161etko. U\u017e sa p\u00fdtaj\u00fa: \u201eM\u00f4\u017ee sa do Kubernetes vlo\u017ei\u0165 datab\u00e1za?\u201c. Zvy\u010dajne hovor\u00edm, \u017ee tu nejde o Kubernetes, ale o Docker. Ak ste pripraven\u00ed, \u017ee va\u0161a datab\u00e1za bude fungova\u0165 v kontajneroch, ako bude fungova\u0165? Odpovedaj\u00fa mi: \u201eNie, nie, nie, po\u010dkajte. Do kontajnerov to netreba. Potrebujeme to v Kubernetes. Pripoj\u00edme ju k node. Teda v\u0161etko bude ako to m\u00e1me teraz, len t\u00fdmto v\u0161etk\u00fdm bude spravova\u0165 Kubernetes.\u201c A to je vlastne dobr\u00fd n\u00e1pad. Teda Kubernetes je nie\u010do tak\u00e9, \u017ee m\u00f4\u017eete pr\u00eds\u0165 do spolo\u010dnosti, ak m\u00e1 spolo\u010dnos\u0165 Kubernetes a na \u0148om postaven\u00e9 procesy, tak pre osobu, ktor\u00e1 sa v tom vyzn\u00e1 \u2014 sta\u010d\u00ed pozrie\u0165 sa na p\u00e1r dn\u00ed, aby povedala: \u201eSom pripraven\u00fd v\u00e1s podporova\u0165. \u00daplne. Celkom. Pochopil som, ako to u v\u00e1s funguje.\u201c Na rozdiel od pr\u00edstupov bez Kubernetes \u2014 tu sa daj\u00fa ko\u013eajnice na jedno miesto, tu druh\u00e9. Tu Ansible, tu Terraform. Niekto to cel\u00e9 nap\u00edsal a trv\u00e1 to pol roka, aby ste to pochopili. Tak\u017ee, stane sa Kubernetes de facto \u0161tandardom, neviem. V s\u00fa\u010dasnosti vyzer\u00e1 ove\u013ea ambici\u00f3znej\u0161ie a istej\u0161ie ako rie\u0161enia, ktor\u00e9 s\u00fa okolo neho. <\/p>\n

Azat Khadiev: No, porovnanie s Linuxom je dos\u0165 odv\u00e1\u017ene. Ten toti\u017e funguje na jednom stroji \u2014 a to je v\u0161etko. Ale Kubernetes funguje na mnoh\u00fdch strojoch. Hne\u010f na to vznik\u00e1 mili\u00f3n vari\u00e1ci\u00ed, d\u00f4vodov. \u00c1no, to je odv\u00e1\u017ene. Ak sa zoh\u013eadn\u00ed, \u017ee m\u00e1me konkurentov tejto paradigme. Napr\u00edklad, Serverless. Je Kubernetes v ohrozen\u00ed pred tak\u00fdmi konkurentmi? <\/p>\n

Pavel Selivanov: Od Serverless\u2026 (smiech) Serverless \u2014 predsa len ch\u00e1peme, \u017ee servera<\/a> predsa len existuj\u00fa. Ned\u00e1vno som po\u010dul predn\u00e1\u0161ku na t\u00fato t\u00e9mu. Tam jeden \u010dlovek povedal, \u017ee servery predsa len existuj\u00fa \u2014 a to je cloud. Ale v\u017edy si mus\u00edme uvedomi\u0165, \u017ee aj v cloude s\u00fa servery. Tam s\u00fa naozaj fyzick\u00e9 servery, racky a niekde s\u00fa nain\u0161talovan\u00e9. To je cloud. Nad t\u00fdm existuje Serverless, kde serverov<\/a> \u201enie\u201c. Preto sa ot\u00e1zka, \u010di Serverless zv\u00ed\u0165az\u00ed nad Kubernetes? M\u00e1m pocit, \u017ee Serverless sa presunie do Kubernetes. Pre poskytovate\u013eov, ktor\u00ed pon\u00fakaj\u00fa Serverless, je Kubernetes ve\u013emi pohodln\u00e1 platforma na to, aby to mohli poskytova\u0165. \u00c1no, mo\u017eno v nejakom momente prestaneme rozpr\u00e1va\u0165 o Kubernetes ako takom, ako o be\u017enom v\u00fdvoji obchodn\u00fdch aplik\u00e1ci\u00ed. Ale niekde hlboko, u poskytovate\u013eov a in\u017einierov, bude st\u00e1\u0165 Kubernetes, kde sa to cel\u00e9 realizuje. <\/p>\n

Azat Khadiev: Trochu in\u00e1 t\u00e9ma. Existuje tak\u00fd pojem fullstack in\u017einier. \u010co si o nich mysl\u00ed\u0161? Oni v\u00f4bec existuj\u00fa? <\/p>\n

Pavel Selivanov: Ehm\u2026 Fullstack in\u017einier\u2026 Nu\u017e, mysl\u00edm si, \u017ee by sme mali rozli\u0161ova\u0165 tieto veci. Vie\u0161, existuje nie\u010do tak\u00e9 ako T-shaped people. Potrebujeme tak\u00e9to osoby v dne\u0161nom odvetv\u00ed? \u00c1no, bezpochyby. Potrebujeme \u013eud\u00ed, ktor\u00ed maj\u00fa \u0161irok\u00fd rozh\u013ead, ale z\u00e1rove\u0148 s\u00fa \u0161pecialistami v nejakej \u00fazkej oblasti. A tu je to ist\u00e9 s Fullstack in\u017einierom \u2014 \u010dlovek, ktor\u00fd rob\u00ed v\u0161etko. Za\u010d\u00edna od v\u00fdvoja frontendu, testovania, backendu, serverov a v\u0161etk\u00e9ho ostatn\u00e9ho. Never\u00edm, \u017ee v ve\u013ekej firme m\u00f4\u017ee by\u0165 t\u00fdmto povolan\u00edm zodpovedn\u00fd jeden \u010dlovek, bez \u00fazkych \u0161pecializ\u00e1ci\u00ed v ka\u017edom z t\u00fdchto aspektov. Ale z\u00e1rove\u0148, ak m\u00e1\u0161 len \u00fazku \u0161pecializ\u00e1ciu, a neinvestuje\u0161 do toho, \u010do sa okolo deje, to tie\u017e v modernom svete nefunguje. Tak\u017ee by som povedal\u2026 slovo Fullstack by som vynechal. Potrebujeme in\u017einierov ve\u013emi. Potrebujeme DevOps. C\u00edtim, \u017ee \u010doskoro prehodnot\u00edme tento aspekt. A t\u00ed u\u017e nebud\u00fa potrebn\u00ed. <\/p>\n

Azat Khadiev: M\u00f4\u017ee\u0161 to objasni\u0165? <\/p>\n

Pavol Selivanov: Mysl\u00edm si, \u017ee v na\u0161om odvetv\u00ed sa \u010doskoro dostaneme do bodu, kedy tieto role Dev a Ops u\u017e nebud\u00fa potrebn\u00e9. Ak potrebujeme odborn\u00edkov a lov\u00edme... Potrebujeme ur\u010dit\u00e9ho v\u00fdvoj\u00e1ra, potrebujeme ur\u010dit\u00e9ho administr\u00e1tora, potrebujeme DevOps in\u017einierov \u2014 teraz ich u\u017e m\u00e1me, a \u010doskoro sa objavia aj in\u017einieri pre produkciu a SRE in\u017einieri. Hoci v skuto\u010dnosti to, \u010do potrebujeme, s\u00fa in\u017einieri, ktor\u00fdch chceme zamestna\u0165. Pozadie v z\u00e1sade nie je d\u00f4le\u017eit\u00e9. Preto\u017ee... Napr\u00edklad SRE hovor\u00ed, \u017ee probl\u00e9my infra\u0161trukt\u00fary s\u00fa v\u017edy softv\u00e9rov\u00e9. A \u010do... Po\u010fme zobra\u0165 v\u00fdvoj\u00e1rov \u2014 z poh\u013eadu, \u017ee v\u00fdvoj\u00e1r je in\u017einier \u2014 priradi\u0165 ich do oddelenia podpory a oni bud\u00fa rie\u0161i\u0165 tieto probl\u00e9my presne tak, ako rie\u0161ia obchodn\u00e9 probl\u00e9my pomocou k\u00f3du a in\u017einierstva ako tak\u00e9ho. <\/p>\n

Azat Khadiev: A z tohto h\u013eadiska... Ako sa pohov\u00e1ra\u0165 s tak\u00fdmi in\u017einiermi? <\/p>\n

Pavol Selivanov: Och, dobr\u00e1 ot\u00e1zka. Mo\u017eno je to u\u017e za hranicou toho, \u010do ch\u00e1pem v tomto \u017eivote. Ale dal by som pr\u00edklad. Nem\u00e1 to ni\u010d spolo\u010dn\u00e9 s pohovorom. Ide o n\u00e1\u0161 vzdel\u00e1vac\u00ed syst\u00e9m v Rusku. V IT vieme, \u017ee n\u00e1\u0161 vzdel\u00e1vac\u00ed syst\u00e9m v Rusku je pre IT svet ve\u013emi zastaran\u00fd, nie je tak\u00fd, ak\u00fd by mal by\u0165. Hovor\u00edm v priemere o nekone\u010dnej Rusku \u2014 a \u010do sa tam deje. Vyp\u00fa\u0161\u0165aj\u00fa sa \u013eudia, ktor\u00ed s\u00fa \u00faplne nepripraven\u00ed \u00eds\u0165 hne\u010f po ukon\u010den\u00ed do webov\u00e9ho v\u00fdvoja, do technologickej spolo\u010dnosti. A to je zl\u00e9. U\u010d\u00edme ich nejak\u00fdm zvl\u00e1\u0161tnym veciam, hoci by sme ich mali u\u010di\u0165, ako vyv\u00edja\u0165 pre Android, pre iOS, ako pou\u017e\u00edva\u0165 Git a v\u0161etky tieto veci. V skuto\u010dnosti sa zd\u00e1, \u017ee nie. In\u0161tit\u00fat je tak\u00e9 obdobie, ke\u010f za teba v\u00e4\u010d\u0161inou platia rodi\u010dia. Po cel\u00fd tvoj \u017eivot. A m\u00f4\u017ee\u0161 venova\u0165 p\u00e4\u0165 rokov svojho \u017eivota, aby si sa u\u010dil podrobne. A \u0161tudova\u0165 cel\u00fd tento T-shaped. Ke\u010f m\u00f4\u017ee\u0161 na in\u0161tit\u00fate \u0161tudova\u0165, \u010do je syst\u00e9m riadenia verzi\u00ed, ak\u00e9 s\u00fa v\u00fdvojov\u00e9 vzory, ako to v\u0161etko testova\u0165, ak\u00e9 s\u00fa datab\u00e1zy, vyrovn\u00e1va\u010de z\u00e1\u0165a\u017ee. A ke\u010f u\u017e ide\u0161 pracova\u0165, za\u010dne\u0161 sa prehlbova\u0165 v nejakej konkr\u00e9tnej oblasti. A takto z\u00edskavame in\u017einierov. A n\u00e1\u0161 vzdel\u00e1vac\u00ed syst\u00e9m v Rusku je ove\u013ea bli\u017e\u0161ie k tejto pravde, ne\u017e sa n\u00e1m zd\u00e1. D\u00e1vaj\u00fa n\u00e1m dobr\u00e9 matematick\u00e9 vzdelanie, poskytuj\u00fa n\u00e1m dobr\u00e9 algoritmick\u00e9 \u0161kolenie, d\u00e1vaj\u00fa n\u00e1m nejak\u00fa predstavu o programovac\u00edch jazykoch. A o pohovore si mysl\u00edm, \u017ee to je nie\u010do bl\u00edzke tomu. Potrebujeme in\u017einierov na pohovor. Potrebujeme horn\u00fa \u010das\u0165 p\u00edsmena T z T-shaped. Preto\u017ee vertik\u00e1lnu \u010diaru p\u00edsmena T z\u00edska. <\/p>\n

Azat Khadiev: \u00c1no, zauj\u00edmav\u00e9. Po piatich rokoch po in\u0161tit\u00fate sa mi zdalo, \u017ee moje vzdelanie bolo ak\u00e9si zvl\u00e1\u0161tne a neadekv\u00e1tne. A potom, ke\u010f sa \u00falohy prehlbovali, projekty narastali, uvedomil som si, \u017ee nie, u\u010dili ma ve\u013emi d\u00f4le\u017eit\u00fdm veciam. Pavol, \u010fakujem ti. Bolo ve\u013emi zauj\u00edmav\u00e9 po\u010du\u0165 tvoje odpovede. Po\u010dujeme tvoju predn\u00e1\u0161ku. <\/p>\n

Pavol Selivanov: \u010eakujem v\u00e1m.
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0420\u0430\u0441\u0448\u0438\u0444\u0440\u043e\u0432\u043a\u0430: \u0410\u0437\u0430\u0442 \u0425\u0430\u0434\u0438\u0435\u0432: \u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435. \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0410\u0437\u0430\u0442 \u0425\u0430\u0434\u0438\u0435\u0432. \u042f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a PaaS \u043d\u0430\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f Mail.ru Cloud Solutions. \u0421\u043e \u043c\u043d\u043e\u0439 \u0437\u0434\u0435\u0441\u044c \u041f\u0430\u0432\u0435\u043b \u0421\u0435\u043b\u0438\u0432\u0430\u043d\u043e\u0432 \u0438\u0437 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Southbridge. \u041c\u044b \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u043d\u0430 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u0438 DevOpsDays. \u041e\u043d \u0437\u0434\u0435\u0441\u044c \u0432\u044b\u0441\u0442\u0443\u043f\u0438\u0442 \u0441 \u0434\u043e\u043a\u043b\u0430\u0434\u043e\u043c \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u0441 Kubernetes \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u0441\u0442\u0440\u043e\u0438\u0442\u044c DevOps, \u043d\u043e \u0441\u043a\u043e\u0440\u0435\u0435 \u0432\u0441\u0435\u0433\u043e \u0443 \u0432\u0430\u0441 \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u0435 \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u0441\u044f. \u041f\u043e\u0447\u0435\u043c\u0443 \u0442\u0430\u043a\u0430\u044f \u043c\u0440\u0430\u0447\u043d\u0430\u044f \u0442\u0435\u043c\u0430? \u041f\u0430\u0432\u0435\u043b \u0421\u0435\u043b\u0438\u0432\u0430\u043d\u043e\u0432: […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-54069","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kubernetes \u2014 je to nov\u00fd Linux? Rozhovor s Pavlom Selivanovom | ProHoster","description":"Prepis: Azat Khadiev: Dobr\u00fd de\u0148.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-eto-novyj-linux-intervyu-s-pavlom-selivanovym","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 \u2014 \u044d\u0442\u043e \u043d\u043e\u0432\u044b\u0439 Linux? \u0418\u043d\u0442\u0435\u0440\u0432\u044c\u044e \u0441 \u041f\u0430\u0432\u043b\u043e\u043c \u0421\u0435\u043b\u0438\u0432\u0430\u043d\u043e\u0432\u044b\u043c | ProHoster","og:description":"\u0420\u0430\u0441\u0448\u0438\u0444\u0440\u043e\u0432\u043a\u0430: \u0410\u0437\u0430\u0442 \u0425\u0430\u0434\u0438\u0435\u0432: \u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kubernetes-eto-novyj-linux-intervyu-s-pavlom-selivanovym","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-12-16T21:00:00+00:00","article:modified_time":"2020-02-18T11:02:02+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"54069","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-02-22 15:57:24","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:12:24","updated":"2026-02-22 15:57:24","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\/54069","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=54069"}],"version-history":[{"count":2,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/54069\/revisions"}],"predecessor-version":[{"id":162117,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/54069\/revisions\/162117"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=54069"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=54069"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=54069"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}