{"id":82223,"date":"2020-05-20T13:42:34","date_gmt":"2020-05-20T11:42:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen"},"modified":"2020-05-20T13:42:34","modified_gmt":"2020-05-20T11:42:34","slug":"luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","title":{"rendered":"Najlep\u0161ie praktiky Kubernetes. Organiz\u00e1cia Kubernetes s men\u0161\u00edm priestorom","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Najlep\u0161ie praktiky Kubernetes. Vytvorenie mal\u00fdch kontajnerov<\/a><\/noindex><\/p>\n

Ako za\u010dnete vytv\u00e1ra\u0165 st\u00e1le viac a viac slu\u017eieb Kubernetes, jednoduch\u00e9 \u00falohy na za\u010diatku sa za\u010d\u00ednaj\u00fa komplikova\u0165. Napr\u00edklad v\u00fdvojov\u00e9 t\u00edmy nem\u00f4\u017eu vytv\u00e1ra\u0165 slu\u017eby alebo nasadenia s rovnak\u00fdm menom. Ak m\u00e1te tis\u00edce podov, ich jednoduch\u00e9 vyp\u00edsanie zabere ve\u013ea \u010dasu, nieto e\u0161te zabezpe\u010di\u0165 riadne spravovanie. A to je len \u0161pi\u010dka \u013eadovca.<\/p>\n

Po\u010fme sa pozrie\u0165, ako namespace u\u013eah\u010duje spr\u00e1vu zdrojov Kubernetes. \u010co je teda namespace? Namespace m\u00f4\u017eeme pova\u017eova\u0165 za virtu\u00e1lny klaster vo vn\u00fatri v\u00e1\u0161ho klastera Kubernetes. M\u00f4\u017eete ma\u0165 nieko\u013eko navz\u00e1jom izolovan\u00fdch namespaces v r\u00e1mci jedn\u00e9ho klastera Kubernetes. Skuto\u010dne v\u00e1m m\u00f4\u017eu a va\u0161im t\u00edmom pom\u00f4c\u0165 s organiz\u00e1ciou, bezpe\u010dnos\u0165ou a dokonca aj v\u00fdkonom syst\u00e9mu.<\/p>\n

\"Najlep\u0161ie
\n
\nVo v\u00e4\u010d\u0161ine distrib\u00faci\u00ed Kubernetes je klaster 'out of the box' so namespace nazvan\u00fdm 'default'. V skuto\u010dnosti existuj\u00fa tri namespaces, s ktor\u00fdmi Kubernetes pracuje: default, kube-system a kube-public. Kube-public sa aktu\u00e1lne pou\u017e\u00edva pomerne zriedka.<\/a><\/noindex><\/p>\n

\"Najlep\u0161ie
\n
\nNedot\u00fdka\u0165 sa namespace kube je dobr\u00fd n\u00e1pad, najm\u00e4 v takto spravovanej s\u00fastave ako Google Kubernetes Engine. Pou\u017e\u00edva namespace 'default' ako miesto, kde s\u00fa vytv\u00e1ran\u00e9 va\u0161e slu\u017eby a aplik\u00e1cie. Nie je tam absol\u00fatne ni\u010d zvl\u00e1\u0161tne, okrem toho, \u017ee Kubernetes je 'out of the box' nastaven\u00fd na jeho pou\u017eitie a nem\u00f4\u017eete ho odstr\u00e1ni\u0165. To je skvel\u00e9 na za\u010diatok a pre syst\u00e9my s n\u00edzkym v\u00fdkonom, ale neodpor\u00fa\u010dal by som pou\u017e\u00edvanie namespace default vo ve\u013ek\u00fdch produk\u010dn\u00fdch syst\u00e9moch. V poslednom pr\u00edpade m\u00f4\u017ee jeden t\u00edm v\u00fdvoj\u00e1rov \u013eahko prep\u00edsa\u0165 k\u00f3d in\u00e9ho t\u00edmu a naru\u0161i\u0165 pr\u00e1cu in\u00e9ho t\u00edmu, ani\u017e by si to uvedomovali.<\/p>\n

Preto by ste mali vytvori\u0165 nieko\u013eko namespaces a pou\u017ei\u0165 ich na segment\u00e1ciu va\u0161ich slu\u017eieb do spravovan\u00fdch celkov. Namespace m\u00f4\u017eete vytvori\u0165 pomocou jedn\u00e9ho pr\u00edkazu. Ak chcete vytvori\u0165 namespace s n\u00e1zvom test, pou\u017eite pr\u00edkaz $ kubectl create namespace test alebo jednoducho vytvorte YAML s\u00fabor a pou\u017eite ho ako ak\u00fdko\u013evek in\u00fd zdroj Kubernetes.<\/p>\n

\"Najlep\u0161ie
\n
\nV\u0161etky namespaces m\u00f4\u017eete zobrazi\u0165 pomocou pr\u00edkazu $ kubectl get namespace. <\/p>\n

\"Najlep\u0161ie
\n
\nPo jej \u00faspe\u0161nom vykonan\u00ed uvid\u00edte tri zabudovan\u00e9 menov\u00e9 priestory a nov\u00fd menov\u00fd priestor s n\u00e1zvom \u201etest\u201c. Pozrime sa na jednoduch\u00fd YAML s\u00fabor, ktor\u00fd je ur\u010den\u00fd na vytvorenie podu. Je zauj\u00edmav\u00e9, \u017ee v \u0148om nie je \u017eiadna zmienka o menovom priestore.<\/p>\n

\"Najlep\u0161ie
\n
\nAk pou\u017eijete kubectl na spustenie tohto s\u00faboru, vytvor\u00ed modul mypod v aktu\u00e1lnom akt\u00edvnom menovom priestore. Tento menov\u00fd priestor bude predvolen\u00fd, pok\u00fdm ho nezmen\u00edte. Existuj\u00fa dva sp\u00f4soby, ako poveda\u0165 Kubernetes, v akom menovom priestore chcete vytvori\u0165 svoj zdroj. Prv\u00fd sp\u00f4sob je pou\u017eit\u00edm vlajky menov\u00e9ho priestoru pri vytv\u00e1ran\u00ed zdroja. <\/p>\n

\"Najlep\u0161ie
\n
\nDruh\u00fd sp\u00f4sob spo\u010d\u00edva v uveden\u00ed menov\u00e9ho priestoru v deklar\u00e1cii YAML.<\/p>\n

\"Najlep\u0161ie
\n
\nAk uvediete menov\u00fd priestor v YAML, bude sa zdroj v\u017edy vytv\u00e1ra\u0165 v tomto priestore. Ak sa pok\u00fasite pou\u017ei\u0165 in\u00fd menov\u00fd priestor pri pou\u017eit\u00ed vlajky menov\u00e9ho priestoru, pr\u00edkaz skon\u010d\u00ed chybou. Teraz, ak sa pok\u00fasite n\u00e1js\u0165 svoj pod, nebude sa v\u00e1m to podari\u0165. <\/p>\n

\"Najlep\u0161ie
\n
\nTo sa deje, preto\u017ee v\u0161etky pr\u00edkazy sa vykon\u00e1vaj\u00fa mimo aktu\u00e1lneho akt\u00edvneho menov\u00e9ho priestoru. Aby ste na\u0161li svoj pod, mus\u00edte pou\u017ei\u0165 vlajku menov\u00e9ho priestoru, av\u0161ak to r\u00fdchlo otravuje, najm\u00e4 ak pracujete ako v\u00fdvoj\u00e1r v skupine, ktor\u00e1 pou\u017e\u00edva vlastn\u00fd menov\u00fd priestor a nechce pou\u017e\u00edva\u0165 t\u00fato vlajku pre ka\u017ed\u00fd jednotliv\u00fd pr\u00edkaz. Pozrime sa, ako to m\u00f4\u017eete opravi\u0165.<\/p>\n

\"Najlep\u0161ie
\n
\nZ predpokladom sa v\u00e1\u0161 akt\u00edvny menov\u00fd priestor naz\u00fdva default. Ak v YAML zdroja neur\u010d\u00edte menov\u00fd priestor, v\u0161etky pr\u00edkazy Kubernetes bud\u00fa pou\u017e\u00edva\u0165 tento akt\u00edvny predvolen\u00fd menov\u00fd priestor. Bohu\u017eia\u013e, pokusy o spr\u00e1vu akt\u00edvneho menov\u00e9ho priestoru pomocou kubectl m\u00f4\u017eu skon\u010di\u0165 ne\u00faspechom. Existuje v\u0161ak ve\u013emi dobr\u00fd n\u00e1stroj s n\u00e1zvom Kubens, ktor\u00fd tento proces zna\u010dne zjednodu\u0161uje. Ke\u010f spust\u00edte pr\u00edkaz kubens, uvid\u00edte v\u0161etky menov\u00e9 priestory s vyzna\u010den\u00fdm akt\u00edvnym menov\u00fdm priestorom. <\/p>\n

\"Najlep\u0161ie
\n
\nNa prepnutie akt\u00edvneho menov\u00e9ho priestoru na menov\u00fd priestor test jednoducho spust\u00edte pr\u00edkaz $ kubens test. Ak potom znova zad\u00e1te pr\u00edkaz $ kubens, m\u00f4\u017eete vidie\u0165, \u017ee sa teraz zv\u00fdraznil nov\u00fd akt\u00edvny menov\u00fd priestor \u2013 test.<\/p>\n

\"Najlep\u0161ie
\n
\nTo znamen\u00e1, \u017ee na zobrazenie podu v testovacom priestore mien nepotrebujete vlajku priestoru mien.<\/p>\n

\"Najlep\u0161ie
\n
\nTakto s\u00fa priestory mien skryt\u00e9 navz\u00e1jom, ale nie s\u00fa od seba izolovan\u00e9. Slu\u017eba z jedn\u00e9ho priestoru mien m\u00f4\u017ee pomerne \u013eahko komunikova\u0165 so slu\u017ebou v inom priestore mien, \u010do b\u00fdva velmi u\u017eito\u010dn\u00e9. Mo\u017enos\u0165 komunik\u00e1cie medzi r\u00f4znymi priestormi mien znamen\u00e1, \u017ee slu\u017eba va\u0161ich v\u00fdvoj\u00e1rov m\u00f4\u017ee interagova\u0165 so slu\u017ebou in\u00e9ho dev-t\u00edmu v inom priestore mien.<\/p>\n

Zvy\u010dajne, ke\u010f va\u0161a aplik\u00e1cia chce komunikova\u0165 so slu\u017ebou Kubernetes, pou\u017e\u00edvate zabudovan\u00fa slu\u017ebu objavovania DNS a jednoducho svojim aplik\u00e1ci\u00e1m uvediete meno slu\u017eby. Av\u0161ak m\u00f4\u017eete vytvori\u0165 slu\u017ebu s rovnak\u00fdm menom v r\u00f4znych priestoroch mien, \u010do je nepr\u00edpustn\u00e9. <\/p>\n

\"Najlep\u0161ie
\n
\nNa\u0161\u0165astie to mo\u017eno \u013eahko ob\u00eds\u0165 pou\u017eit\u00edm roz\u0161\u00edrenej formy DNS adresy. Slu\u017eby v Kubernetes vystavuj\u00fa svoje koncov\u00e9 body pomocou spolo\u010dnej \u0161abl\u00f3ny DNS. To vyzer\u00e1 asi takto:<\/p>\n

\"Najlep\u0161ie
\n
\nVo v\u0161eobecnosti potrebujete len meno slu\u017eby a DNS automaticky ur\u010d\u00ed pln\u00fa adresu. <\/p>\n

\"Najlep\u0161ie
\n
\nAk v\u0161ak potrebujete pristupova\u0165 k slu\u017ebe v inom priestore mien, jednoducho pou\u017eite meno slu\u017eby plus n\u00e1zov priestoru mien:<\/p>\n

\"Najlep\u0161ie
\n
\nNapr\u00edklad, ak chcete pripoji\u0165 k datab\u00e1ze slu\u017eby v testovacom priestore mien, m\u00f4\u017eete pou\u017ei\u0165 adresu database.test.<\/p>\n

\"Najlep\u0161ie
\n
\nAk sa v\u0161ak chcete pripoji\u0165 k datab\u00e1ze slu\u017eby v priestore mien prod, pou\u017eijete database.prod.<\/p>\n

\"Najlep\u0161ie
\n
\nAk naozaj chcete izolova\u0165 a obmedzi\u0165 pr\u00edstup k priestoru mien, Kubernetes to umo\u017e\u0148uje prostredn\u00edctvom sie\u0165ov\u00fdch polit\u00edk Kubernetes Network Policies. O tom sa zmienim v nasleduj\u00facej s\u00e9rii. <\/p>\n

\u010casto sa ma p\u00fdtaj\u00fa, ko\u013eko priestorov mien treba vytvori\u0165 a na ak\u00e9 \u00fa\u010dely? \u010co teda predstavuje riaden\u00fd fragment \u00fadajov?<\/p>\n

Ak vytvor\u00edte pr\u00edli\u0161 ve\u013ea priestorov n\u00e1zvov, len v\u00e1m bud\u00fa prek\u00e1\u017ea\u0165. Ak ich bude pr\u00edli\u0161 m\u00e1lo, pr\u00eddete o v\u0161etky v\u00fdhody tak\u00e9hoto rie\u0161enia. Mysl\u00edm, \u017ee existuj\u00fa \u0161tyri z\u00e1kladn\u00e9 etapy, ktor\u00fdmi prech\u00e1dza ka\u017ed\u00e1 spolo\u010dnos\u0165 pri vytv\u00e1ran\u00ed svojej organiza\u010dnej \u0161trukt\u00fary. V z\u00e1vislosti od etapy v\u00fdvoja, na ktorej sa va\u0161e projekty alebo spolo\u010dnosti nach\u00e1dzaj\u00fa, si m\u00f4\u017eete zvoli\u0165 pr\u00edslu\u0161n\u00fa strat\u00e9giu pre vytv\u00e1ranie priestorov n\u00e1zvov.<\/p>\n

Predstavte si, \u017ee ste s\u00fa\u010das\u0165ou malej t\u00edmu, ktor\u00fd pracuje na v\u00fdvoji 5-10 mikroslu\u017eieb a v\u0161etk\u00fdch v\u00fdvoj\u00e1rov m\u00f4\u017eete \u013eahko zhroma\u017edi\u0165 v jednej miestnosti. V tejto situ\u00e1cii m\u00e1 zmysel sp\u00fa\u0161\u0165a\u0165 v\u0161etky produk\u010dn\u00e9 slu\u017eby v priestore n\u00e1zvov default. Samozrejme, pre v\u00e4\u010d\u0161ie mo\u017enosti m\u00f4\u017eete pou\u017ei\u0165 dva priestory n\u00e1zvov \u2014 jeden pre produkciu a druh\u00fd pre v\u00fdvoj. A pravdepodobne testujete svoj v\u00fdvoj na lok\u00e1lnom po\u010d\u00edta\u010di pomocou nie\u010doho ako Minikube. <\/p>\n

Predpokladajme, \u017ee sa podmienky zmenili a teraz m\u00e1te r\u00fdchlo rast\u00faci t\u00edm, ktor\u00fd s\u00fa\u010dasne pracuje na viac ako 10 mikroslu\u017eb\u00e1ch. Nast\u00e1va moment, ke\u010f je potrebn\u00e9 pou\u017ei\u0165 nieko\u013eko klastrov alebo priestorov n\u00e1zvov, samostatne pre produkciu a v\u00fdvoj. M\u00f4\u017eete rozdeli\u0165 t\u00edm na nieko\u013eko podskup\u00edn tak, aby ka\u017ed\u00e1 z nich mala svoje vlastn\u00e9 mikroslu\u017eby a ka\u017ed\u00e1 z t\u00fdchto t\u00edmov si mohla vybra\u0165 svoje vlastn\u00e9 priestory n\u00e1zvov na zjednodu\u0161enie procesu riadenia v\u00fdvoja a vyd\u00e1vania softv\u00e9ru.<\/p>\n

\"Najlep\u0161ie
\n
\nAko ka\u017ed\u00fd \u010dlen t\u00edmu z\u00edskava predstavu o tom, ako syst\u00e9m funguje ako celok, koordinova\u0165 ka\u017ed\u00fa zmenu so v\u0161etk\u00fdmi ostatn\u00fdmi v\u00fdvoj\u00e1rmi sa st\u00e1va \u010doraz \u0165a\u017e\u0161\u00edm. Pokus o rozbehnutie cel\u00e9ho stacku na va\u0161om lok\u00e1lnom po\u010d\u00edta\u010di sa s ka\u017ed\u00fdm d\u0148om st\u00e1va zlo\u017eitej\u0161\u00edm. <\/p>\n

V ve\u013ek\u00fdch spolo\u010dnostiach v\u00fdvoj\u00e1ri \u010dasto ani nevedia, kto konkr\u00e9tne na \u010dom pracuje. T\u00edmy komunikuj\u00fa prostredn\u00edctvom servisn\u00fdch zml\u00fav alebo pou\u017e\u00edvaj\u00fa technol\u00f3giu Service mesh, ktor\u00e1 prid\u00e1va nad sie\u0165ou \u00farove\u0148 abstrakcie, ako n\u00e1stroj na konfigur\u00e1ciu Istio. Pokus spusti\u0165 cel\u00fd stack lok\u00e1lne je jednoducho nemo\u017en\u00fd. D\u00f4razne odpor\u00fa\u010dam pou\u017e\u00edva\u0165 v Kubernetes platformu kontinu\u00e1lneho dod\u00e1vania (CD) ako Spinnaker. Tak prich\u00e1dza okamih, ke\u010f ka\u017ed\u00e9mu t\u00edmu ur\u010dite treba vlastn\u00fd namespace. Ka\u017ed\u00fd t\u00edm si dokonca m\u00f4\u017ee vybra\u0165 nieko\u013eko namespace-ov pre prostredie dev a prostredie prod. <\/p>\n

Nakoniec existuj\u00fa ve\u013ek\u00e9 podnikate\u013esk\u00e9 spolo\u010dnosti, v ktor\u00fdch jedna skupina v\u00fdvoj\u00e1rov ani nevie o existencii in\u00fdch skup\u00edn. Tak\u00e1to spolo\u010dnos\u0165 m\u00f4\u017ee dokonca zamestna\u0165 extern\u00fdch v\u00fdvoj\u00e1rov, ktor\u00ed spolupracuj\u00fa prostredn\u00edctvom dobre zdokumentovan\u00fdch API. V ka\u017edej takejto skupine je nieko\u013eko t\u00edmov a nieko\u013eko mikroslu\u017eieb. V tomto pr\u00edpade je potrebn\u00e9 vyu\u017ei\u0165 v\u0161etky n\u00e1stroje, o ktor\u00fdch som hovoril sk\u00f4r.<\/p>\n

\"Najlep\u0161ie
\n
\nProgram\u00e1tori by nemali nasadzova\u0165 slu\u017eby ru\u010dne a nemali by ma\u0165 pr\u00edstup k namespace-om, ktor\u00e9 sa ich net\u00fdkaj\u00fa. V tejto f\u00e1ze je vhodn\u00e9 ma\u0165 nieko\u013eko klastrov na zn\u00ed\u017eenie \"radii expl\u00f3zie\" zle nastaven\u00fdch aplik\u00e1ci\u00ed, na zjednodu\u0161enie procesov faktur\u00e1cie a spravovania zdrojov.<\/p>\n

Tak\u017ee spr\u00e1vne pou\u017e\u00edvanie namespace-ov vo va\u0161ej organiz\u00e1cii umo\u017e\u0148uje spravi\u0165 Kubernetes viac spravovate\u013en\u00fdm, kontrolovate\u013en\u00fdm, bezpe\u010dn\u00fdm a flexibiln\u00fdm.<\/p>\n

Najlep\u0161ie praktiky Kubernetes. Kontrola \u017eivotaschopnosti Kubernetes pomocou Readiness a Liveness testov<\/a><\/noindex><\/p>\n

\r\n \"Prehrajte\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Trochu reklamy \ud83d\ude42<\/h3>\n

\n\u010eakujeme, \u017ee ost\u00e1vate s nami. P\u00e1\u010dia sa v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vidie\u0165 viac zauj\u00edmav\u00fdch materi\u00e1lov? Podporte n\u00e1s, vytvoren\u00edm objedn\u00e1vky alebo odpor\u00fa\u010dan\u00edm zn\u00e1mym, cloud VPS pre v\u00fdvoj\u00e1rov od 4,99 dol\u00e1rov<\/a><\/noindex>, unik\u00e1tny ekvivalent entry-level serverov, ktor\u00fd sme pre v\u00e1s vytvorili:<\/b> Cel\u00e1 pravda o VPS (KVM) E5-2697 v3 (6 jadier) 10GB DDR4 480GB SSD 1Gbps od 19 dol\u00e1rov alebo ako spr\u00e1vne rozdeli\u0165 server?<\/a><\/noindex> (k dispoz\u00edcii varianty s RAID1 a RAID10, a\u017e 24 jadier a a\u017e 40GB DDR4).<\/p>\n

Dell R730xd je dvakr\u00e1t lacnej\u0161\u00ed v d\u00e1tovom centre Equinix Tier IV v Amsterdame?<\/b> Len u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 dol\u00e1rov<\/a><\/noindex> v Holandsku! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 dol\u00e1rov!<\/b><\/b> Pre\u010d\u00edtajte si o tom Ako vybudova\u0165 infra\u0161trukt\u00faru korpor\u00e1tneho typu s pou\u017eit\u00edm serverov Dell R730xd E5-2650 v4 s cenou 9000 eur za zlomok ceny?<\/a><\/noindex>
\n
Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u0421\u043e\u0437\u0434\u0430\u043d\u0438\u0435 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u041f\u043e \u043c\u0435\u0440\u0435 \u0442\u043e\u0433\u043e \u043a\u0430\u043a \u0432\u044b \u043d\u0430\u0447\u0438\u043d\u0430\u0435\u0442\u0435 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0432\u0441\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 \u0438 \u0431\u043e\u043b\u044c\u0448\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 Kubernetes, \u043f\u0440\u043e\u0441\u0442\u044b\u0435 \u043f\u043e \u043d\u0430\u0447\u0430\u043b\u0443 \u0437\u0430\u0434\u0430\u0447\u0438 \u043d\u0430\u0447\u0438\u043d\u0430\u044e\u0442 \u0443\u0441\u043b\u043e\u0436\u043d\u044f\u0442\u044c\u0441\u044f. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u043e\u0432 \u043d\u0435 \u043c\u043e\u0433\u0443\u0442 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0441\u043b\u0443\u0436\u0431\u044b \u0438\u043b\u0438 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f \u043f\u043e\u0434 \u043e\u0434\u043d\u0438\u043c \u0438 \u0442\u0435\u043c \u0436\u0435 \u0438\u043c\u0435\u043d\u0435\u043c. \u0415\u0441\u043b\u0438 \u0443 \u0432\u0430\u0441 \u0442\u044b\u0441\u044f\u0447\u0438 \u043f\u043e\u0434\u043e\u0432, \u0438\u0445 \u043f\u0440\u043e\u0441\u0442\u043e\u0435 \u043f\u0435\u0440\u0435\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u0435 \u0437\u0430\u0439\u043c\u0435\u0442 \u043a\u0443\u0447\u0443 \u0432\u0440\u0435\u043c\u0435\u043d\u0438, \u043d\u0435 \u0433\u043e\u0432\u043e\u0440\u044f \u043e \u0442\u043e\u043c, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":82224,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-82223","post","type-post","status-publish","format-standard","has-post-thumbnail","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\udd47Najlep\u0161ie praktiky Kubernetes. Organiz\u00e1cia Kubernetes s namespace-om | ProHoster","description":"Najlep\u0161ie praktiky Kubernetes.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","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\udd47\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u041e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f Kubernetes \u0441 \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u043e\u043c \u0438\u043c\u0435\u043d | ProHoster","og:description":"\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","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-20T11:42:34+00:00","article:modified_time":"2020-05-20T11:42:34+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"82223","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 15:41:29","updated":"2022-09-29 19:27:31","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\/82223","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=82223"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/82223\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/82224"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=82223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=82223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=82223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}