{"id":75425,"date":"2020-03-26T07:42:30","date_gmt":"2020-03-26T05:42:30","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes"},"modified":"2020-03-26T07:42:30","modified_gmt":"2020-03-26T05:42:30","slug":"luchshie-10-hitrostej-i-sovetov-po-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","title":{"rendered":"Nejlep\u0161\u00ed tipy a triky pro Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Nejlep\u0161\u00ed
\n
\nNa internetu je mnoho referen\u010dn\u00ed literatury, ale n\u011bkdy se uk\u00e1\u017e\u00ed b\u00fdt nejcenn\u011bj\u0161\u00edmi nejjednodu\u0161\u0161\u00ed rady. T\u00fdm Kubernetes aaS od Mail.ru<\/a><\/noindex> p\u0159elo\u017eil v\u00fdb\u011br deseti trik\u016f a rad<\/a><\/noindex>, kter\u00e9 autorka \u010dl\u00e1nku shrom\u00e1\u017edila po roce pr\u00e1ce s Kubernetes. Rady nejsou se\u0159azeny podle d\u016fle\u017eitosti, ale mysl\u00edme si, \u017ee si ka\u017ed\u00fd najde n\u011bco u\u017eite\u010dn\u00e9ho pro sebe.
\n<\/a><\/noindex><\/p>\n

Nejjednodu\u0161\u0161\u00ed p\u0159\u00edkaz pro pr\u00e1ci s Kubernetes<\/h2>\n

\nNejd\u0159\u00edve si asi uk\u00e1\u017eeme nejjednodu\u0161\u0161\u00ed a neju\u017eite\u010dn\u011bj\u0161\u00ed akci p\u0159i pr\u00e1ci s Kubernetes. N\u00e1sleduj\u00edc\u00ed p\u0159\u00edkaz aktivuje automatick\u00e9 dopl\u0148ov\u00e1n\u00ed p\u0159\u00edkaz\u016f kubectl<\/code> v shellu bash:<\/p>\n

echo \"source > ~\/.bashrc\n<\/code><\/pre>\n
\nAutomatick\u00e9 dopl\u0148ov\u00e1n\u00ed kubectl<\/code> bude zaps\u00e1no do souboru .bashrc a bude se automaticky aktivovat poka\u017ed\u00e9 p\u0159i spu\u0161t\u011bn\u00ed shellu. To urychluje zad\u00e1v\u00e1n\u00ed dlouh\u00fdch p\u0159\u00edkaz\u016f a parametr\u016f, jako je all-namespaces<\/code>. V\u00edce informac\u00ed naleznete v dokumentaci Kubernetes pro bash<\/a><\/noindex>.<\/p>\n
V\u00fdchoz\u00ed limity pro pam\u011b\u0165 a CPU v prostoru jmen<\/h2>\n
\nPokud je aplikace naps\u00e1na \u0161patn\u011b, nap\u0159\u00edklad ka\u017ed\u00fd sekundu otev\u00edr\u00e1 nov\u00e9 spojen\u00ed s datab\u00e1z\u00ed, ale nikdy nezav\u00edr\u00e1, vznik\u00e1 v clusteru \u00fanik pam\u011bti. A pokud nebyl pro aplikaci p\u0159i nasazen\u00ed nastaven limit na pam\u011b\u0165, m\u016f\u017ee to v\u00e9st k selh\u00e1n\u00ed uzlu.<\/p>\n
Aby se tomu zabr\u00e1nilo, Kubernetes umo\u017e\u0148uje nastavovat v\u00fdchoz\u00ed limity pro ka\u017ed\u00fd prostor jmen. Ty se zapisuj\u00ed do souboru yaml pro konkr\u00e9tn\u00ed prostor jmen. Zde je p\u0159\u00edklad takov\u00e9ho souboru:<\/p>\n
apiVersion: v1\nkind: LimitRange\nmetadata:\n  name: mem-limit-range\nspec:\n  limits:\n  - default:\n      memory: 512Mi\n    defaultRequest:\n      memory: 256Mi\n    type: Container\n<\/code><\/pre>\n
\nVytvo\u0159te takov\u00fd yaml a aplikujte jej na jak\u00fdkoli prostor jmen. Nap\u0159\u00edklad na prostor jmen limit-example<\/code>. Nyn\u00ed bude pro ka\u017ed\u00fd kontejner nasazen\u00fd v tomto prostoru jmen platit limit 512Mi, pokud pro tento kontejner nebyl dodate\u010dn\u011b nastaven jin\u00fd individu\u00e1ln\u00ed limit.<\/p>\n
\u00dadr\u017eba star\u00fdch verz\u00ed Kubernetes<\/h2>\n
\nKubelet za\u010d\u00edn\u00e1 automaticky \u00fadr\u017ebu, kdy\u017e \/var\/lib\/docker<\/i> zab\u00edr\u00e1 90 % dostupn\u00e9ho diskov\u00e9ho prostoru. To je skv\u011bl\u00e9, av\u0161ak do verze Kubernetes 1.7 neexistoval v\u00fdchoz\u00ed limit na po\u010det pou\u017e\u00edvan\u00fdch indexov\u00fdch deskriptor\u016f inode (inod\u016f), kter\u00e9 odpov\u00eddaj\u00ed po\u010dtu soubor\u016f v souborov\u00e9m syst\u00e9mu.<\/p>\n
Potenci\u00e1ln\u011b v\u00e1\u0161 kontejner \/var\/lib\/docker<\/i> m\u016f\u017ee vyu\u017e\u00edt pouze 50 % diskov\u00e9ho prostoru, ale inody mohou doj\u00edt, co\u017e by zp\u016fsobilo probl\u00e9my v pr\u00e1ci pracovn\u00edk\u016f.<\/p>\n
Ve star\u0161\u00edch verz\u00edch kubelet od 1.4 do 1.6 je t\u0159eba p\u0159idat tento p\u0159\u00edznak:<\/p>\n
--eviction-hard\n=memory.available<100Mi,nodefs.available<10%,nodefs.inodesFree<5%\n<\/code><\/pre>\n
\nVe verz\u00edch 1.7 a nov\u011bj\u0161\u00edch je tento p\u0159\u00edznak nastaven ve v\u00fdchoz\u00edm nastaven\u00ed. Star\u0161\u00ed verze v\u0161ak nesleduj\u00ed limit inod\u016f.<\/p>\n
Minikube\u2026 mal\u00fd, ale v\u00fdkonn\u00fd m\u00edstn\u00ed Kubernetes<\/h2>\n
\nMinikube je nejjednodu\u0161\u0161\u00ed zp\u016fsob, jak spustit m\u00edstn\u00ed cluster Kubernetes. Spust\u00ed se jednoduch\u00fdm p\u0159\u00edkazem:<\/p>\n
minikube start\n<\/code><\/pre>\n
\nPo proveden\u00ed tohoto p\u0159\u00edkazu m\u00e1te na sv\u00e9m po\u010d\u00edta\u010di skute\u010dn\u00fd cluster Kubernetes.<\/p>\n
\"Nejlep\u0161\u00ed
\nZdroj ilustrace<\/i><\/a><\/noindex><\/p>\n
Hlavn\u00ed my\u0161lenka spo\u010d\u00edv\u00e1 v tom, jak sestavit aplikaci a spustit ji m\u00edstn\u011b v tomto clusteru. Pokud neud\u011bl\u00edte speci\u00e1ln\u00ed pokyny, Docker obraz se bude sestavovat na va\u0161em po\u010d\u00edta\u010di, nikoli v clusteru.<\/p>\n
Abychom p\u0159im\u011bli Docker odeslat obraz do m\u00edstn\u00edho clusteru Kubernetes, pou\u017eije se n\u00e1sleduj\u00edc\u00ed p\u0159\u00edkaz:<\/p>\n
eval $(minikube docker-env)\n<\/code><\/pre>\n
\nNyn\u00ed m\u016f\u017eeme sestavovat aplikace na m\u00edstn\u00edm clusteru Kubernetes.<\/p>\n
Ned\u00e1vejte p\u0159\u00edstup kubectl ka\u017ed\u00e9mu bez omezen\u00ed<\/h2>\n
\nA\u010dkoli to m\u016f\u017ee b\u00fdt z\u0159ejm\u00e9, pokud n\u011bkolik t\u00fdm\u016f pou\u017e\u00edv\u00e1 jeden cluster pro sv\u00e9 aplikace (co\u017e byl \u00fa\u010del vytvo\u0159en\u00ed Kubernetes), nem\u011bli byste ho jen tak d\u00e1vat v\u0161em. kubectl<\/code>Lep\u0161\u00ed je odd\u011blit t\u00fdmy a ka\u017ed\u00e9mu z nich p\u0159id\u011blit vlastn\u00ed prostor jmen a omezit p\u0159\u00edstup pomoc\u00ed politik RBAC.<\/p>\n
M\u016f\u017eete si d\u00e1t pr\u00e1ci s definov\u00e1n\u00edm pr\u00e1v p\u0159\u00edstupu pro ka\u017ed\u00fd pod, v\u010detn\u011b \u010dten\u00ed, vytv\u00e1\u0159en\u00ed, maz\u00e1n\u00ed a dal\u0161\u00edch operac\u00ed. Hlavn\u00ed je v\u0161ak omezit p\u0159\u00edstup k tajemstv\u00edm, co\u017e by m\u011bl umo\u017enit pouze administr\u00e1tor\u016fm. T\u00edm odd\u011bl\u00edme ty, kte\u0159\u00ed mohou spravovat cluster, od t\u011bch, kte\u0159\u00ed se v n\u011bm mohou jen nasazovat.<\/p>\n
Spravujte rozpo\u010dty pod\u016f<\/h2>\n
\nJak zajistit, aby aplikace v clusteru Kubernetes nem\u011bla prostoje? PodDisruptionBudget a je\u0161t\u011b jednou PodDisruptionBudget.<\/p>\n
Clustery se pravideln\u011b aktualizuj\u00ed a uzly jsou vypr\u00e1zdn\u011bny. Nic nestoj\u00ed na m\u00edst\u011b, takov\u00e1 je realita. Do ka\u017ed\u00e9ho nasazen\u00ed s v\u00edce ne\u017e jedn\u00edm instanc\u00ed by m\u011bl b\u00fdt v\u017edy zahrnut PDB (PodDisruptionBudget). Vytv\u00e1\u0159\u00ed se v jednoduch\u00e9m souboru yaml, kter\u00fd se aplikuje na cluster. Oblast pokryt\u00ed konkr\u00e9tn\u00edho PDB je ur\u010dena selektory \u0161t\u00edtk\u016f.<\/p>\n
Pozn\u00e1mka:<\/strong> Rozpo\u010det PDB se bere v \u00favahu pouze p\u0159i reverzibiln\u00edm poru\u0161en\u00ed rozpo\u010dtu (voluntary disruption<\/a><\/noindex>). P\u0159i situac\u00edch, jako jsou hardwarov\u00e9 poruchy, PDB nefunguje.<\/p>\n
P\u0159\u00edklad PDB:<\/strong><\/p>\n
apiVersion: policy\/v1beta1\nkind: PodDisruptionBudget\nmetadata:\n  name: app-a-pdb\nspec:\n  minAvailable: 2\n  selector:\n      matchLabels:\n        app: app-a\n<\/code><\/pre>\n
\nDva z\u00e1kladn\u00ed parametry jsou matchLabels<\/code> a minAvailable<\/code>. V prvn\u00edm parametru se uv\u00e1d\u00ed, pro jak\u00e9 aplikace plat\u00ed rozpo\u010det. Nap\u0159\u00edklad, pokud m\u00e1m nasazen\u00ed se \u0161t\u00edtky app: app-a<\/code> a app: app-b<\/code>, pak se tento PDB pou\u017eije pouze na prvn\u00ed.<\/p>\n
Parameter minAvailable<\/code> zohled\u0148uje se p\u0159i vypr\u00e1zdn\u011bn\u00ed (\u010di\u0161t\u011bn\u00ed) uzlu. Nap\u0159\u00edklad v na\u0161em p\u0159\u00edkladu b\u011bhem vypr\u00e1zdn\u011bn\u00ed jsou vy\u0159azeny v\u0161echny instance app: app-a<\/code>, krom\u011b dvou.<\/p>\n
To umo\u017e\u0148uje kontrolovat, kolik instanc\u00ed aplikace by m\u011blo b\u00fdt spu\u0161t\u011bno v ka\u017ed\u00e9m okam\u017eiku.<\/p>\n
Monitorov\u00e1n\u00ed zdrav\u00ed aplikace<\/h2>\n
\nToto monitorov\u00e1n\u00ed je mo\u017en\u00e9 dv\u011bma zp\u016fsoby: pomoc\u00ed sond Readiness nebo Liveness.<\/p>\n
Prvn\u00ed sonda (readiness) ur\u010duje, zda je kontejner p\u0159ipraven p\u0159ij\u00edmat provoz.<\/p>\n
Druh\u00e1 (liveness) ukazuje, zda je kontejner funk\u010dn\u00ed, nebo zda je t\u0159eba jej restartovat.<\/p>\n
P\u0159\u00edslu\u0161n\u00e9 konfigurace se jednodu\u0161e p\u0159id\u00e1vaj\u00ed do yaml pro nasazen\u00ed. Zde lze uv\u00e9st \u010dasov\u00e9 limity, doby zpo\u017ed\u011bn\u00ed a po\u010det opakovan\u00fdch pokus\u016f. Podrobn\u011bji o nich se do\u010dtete v dokumentaci Kubernetes<\/a><\/noindex>.<\/p>\n
\u0160t\u00edtky v\u0161ude<\/h2>\n
\n\u0160t\u00edtky jsou jedn\u00edm ze z\u00e1kladn\u00edch pojm\u016f v Kubernetes. Umo\u017e\u0148uj\u00ed objekt\u016fm svobodn\u011b se spojovat, a tak\u00e9 vytv\u00e1\u0159et dotazy na z\u00e1klad\u011b \u0161t\u00edtk\u016f. V Kubernetes lze dokonce p\u0159ej\u00edt k klientovi a sledovat ud\u00e1losti podle konkr\u00e9tn\u00edch \u0161t\u00edtk\u016f.<\/p>\n
Pomoc\u00ed \u0161t\u00edtk\u016f lze ud\u011blat prakticky cokoliv, ale dobr\u00fdm p\u0159\u00edkladem by bylo vytvo\u0159en\u00ed n\u011bkolika prost\u0159ed\u00ed pro prov\u00e1d\u011bn\u00ed program\u016f v jednom klastru.<\/p>\n
P\u0159edstavme si, \u017ee pou\u017e\u00edv\u00e1te stejn\u00fd klastr pro dev<\/code> a qa<\/code>. To znamen\u00e1, \u017ee m\u016f\u017eete m\u00edt aplikaci app-a<\/code>, kter\u00e1 sou\u010dasn\u011b b\u011b\u017e\u00ed v obou prost\u0159ed\u00edch qa<\/code> a dev<\/code>. V tomto p\u0159\u00edpad\u011b m\u016f\u017eeme oslovit samostatnou instanci aplikace v konkr\u00e9tn\u00edm prost\u0159ed\u00ed, uveden\u00edm p\u0159\u00edslu\u0161n\u00e9ho parametru environment<\/code>. Nap\u0159\u00edklad, app: app-a<\/code> a environment: dev<\/code> pro jedno prost\u0159ed\u00ed, a app: app-a<\/code> a environment: qa<\/code> pro druh\u00e9.<\/p>\n
To umo\u017e\u0148uje p\u0159\u00edstup k ob\u011bma instanc\u00edm aplikace, nap\u0159\u00edklad k prov\u00e1d\u011bn\u00ed testov\u00e1n\u00ed sou\u010dasn\u011b.<\/p>\n
Ud\u011blejte po\u0159\u00e1dek<\/h2>\n
\nKubernetes je velmi mocn\u00fd syst\u00e9m, ale jak\u00fdkoliv syst\u00e9m se nakonec m\u016f\u017ee dostat do probl\u00e9m\u016f s velk\u00fdm mno\u017estv\u00edm proces\u016f. Kubelet spou\u0161t\u00ed v\u0161echny procesy a kontroly, kter\u00e9 jste uvedli, spolu s t\u011bmi sv\u00fdmi.<\/p>\n
Samoz\u0159ejm\u011b, jeden bez dozoru z\u016fst\u00e1vaj\u00edc\u00ed slu\u017eba syst\u00e9m nezpomal\u00ed, a Kubernetes je od za\u010d\u00e1tku navr\u017een pro \u0161k\u00e1lov\u00e1n\u00ed. Ale pokud m\u00edsto jedn\u00e9 slu\u017eby vznikne milion, kubelet za\u010d\u00edn\u00e1 kolabovat.<\/p>\n
Pokud z n\u011bjak\u00e9ho d\u016fvodu odstran\u00edte nasazen\u00ed (kontejner, obraz, cokoliv jin\u00e9ho), ujist\u011bte se, \u017ee je v\u0161e \u00fapln\u011b vy\u010di\u0161t\u011bno.<\/p>\n
Seznamte se s Go<\/h2>\n
\nNejd\u016fle\u017eit\u011bj\u0161\u00ed doporu\u010den\u00ed jsme si nechali na konec. Nau\u010dte se programovac\u00ed jazyk Go.<\/p>\n
Kubernetes je naps\u00e1n v Go, v\u0161echna roz\u0161\u00ed\u0159en\u00ed jsou naps\u00e1na v Go a nav\u00edc je ofici\u00e1ln\u011b podporov\u00e1na klientsk\u00e1 knihovna client-go.<\/p>\n
M\u016f\u017eete ho pou\u017e\u00edt k r\u016fzn\u00fdm a zaj\u00edmav\u00fdm v\u011bcem. Nap\u0159\u00edklad k \u00faprav\u011b syst\u00e9mu Kubernetes podle sv\u00fdch pot\u0159eb. M\u016f\u017eete tak vyu\u017e\u00edt vlastn\u00ed programy ke sb\u011bru dat, nasazen\u00ed aplikac\u00ed nebo prost\u00e9mu \u010di\u0161t\u011bn\u00ed kontejner\u016f.<\/p>\n
Nau\u010dit se programovac\u00ed jazyk Go a ovl\u00e1dnout client-go je pravd\u011bpodobn\u011b nejd\u016fle\u017eit\u011bj\u0161\u00ed rada, kterou m\u016f\u017eeme d\u00e1t za\u010d\u00ednaj\u00edc\u00edm u\u017eivatel\u016fm Kubernetes.<\/p>\n
P\u0159elo\u017eeno s podporou Mail.ru Cloud Solutions<\/i><\/a><\/noindex><\/p>\n
Co si je\u0161t\u011b p\u0159e\u010d\u00edst<\/strong>:<\/p>\n
    \n
  1. T\u0159i \u00farovn\u011b automatick\u00e9ho \u0161k\u00e1lov\u00e1n\u00ed v Kubernetes a jak je efektivn\u011b vyu\u017e\u00edvat<\/a><\/noindex>.<\/li>\n
  2. Pracovn\u00ed uzly Kubernetes: mnoho mal\u00fdch nebo m\u00e1lo velk\u00fdch<\/a><\/noindex>?<\/li>\n
  3. 25 u\u017eite\u010dn\u00fdch n\u00e1stroj\u016f pro nasazen\u00ed a spr\u00e1vu Kubernetes<\/a><\/noindex>.<\/li>\n<\/ol>\n
    Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
    \u0412 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435 \u043c\u043d\u043e\u0433\u043e \u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u043e\u0439 \u043b\u0438\u0442\u0435\u0440\u0430\u0442\u0443\u0440\u044b, \u043d\u043e \u0438\u043d\u043e\u0433\u0434\u0430 \u0441\u0430\u043c\u044b\u043c\u0438 \u0446\u0435\u043d\u043d\u044b\u043c\u0438 \u0441\u0442\u0430\u043d\u043e\u0432\u044f\u0442\u0441\u044f \u0441\u0430\u043c\u044b\u0435 \u043f\u0440\u043e\u0441\u0442\u044b\u0435 \u0441\u043e\u0432\u0435\u0442\u044b. \u041a\u043e\u043c\u0430\u043d\u0434\u0430 Kubernetes aaS \u043e\u0442 Mail.ru \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u0430 \u043f\u043e\u0434\u0431\u043e\u0440\u043a\u0443 \u0438\u0437 \u0434\u0435\u0441\u044f\u0442\u0438 \u0445\u0438\u0442\u0440\u043e\u0441\u0442\u0435\u0439 \u0438 \u0441\u043e\u0432\u0435\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0430\u0432\u0442\u043e\u0440 \u0441\u0442\u0430\u0442\u044c\u0438 \u0441\u043e\u0431\u0440\u0430\u043b\u0430 \u043f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0431\u043e\u0442\u044b \u0441 Kubernetes. \u0421\u043e\u0432\u0435\u0442\u044b \u043d\u0435 \u043e\u0442\u0441\u043e\u0440\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u044b \u043f\u043e \u0432\u0430\u0436\u043d\u043e\u0441\u0442\u0438, \u043d\u043e \u0434\u0443\u043c\u0430\u0435\u043c, \u0447\u0442\u043e \u043a\u0430\u0436\u0434\u044b\u0439 \u043d\u0430\u0439\u0434\u0435\u0442 \u0447\u0442\u043e-\u0442\u043e \u043f\u043e\u043b\u0435\u0437\u043d\u043e\u0435 \u0434\u043b\u044f \u0441\u0435\u0431\u044f. \u0421\u0430\u043c\u0430\u044f \u043f\u0440\u043e\u0441\u0442\u0430\u044f \u043a\u043e\u043c\u0430\u043d\u0434\u0430 \u0432 \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 Kubernetes […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":75426,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-75425","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\udd47Top 10 tip\u016f a trik\u016f pro Kubernetes | ProHoster","description":"Na internetu je mnoho referen\u010dn\u00edch materi\u00e1l\u016f, ale.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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 10 \u0445\u0438\u0442\u0440\u043e\u0441\u0442\u0435\u0439 \u0438 \u0441\u043e\u0432\u0435\u0442\u043e\u0432 \u043f\u043e Kubernetes | ProHoster","og:description":"\u0412 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435 \u043c\u043d\u043e\u0433\u043e \u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u043e\u0439 \u043b\u0438\u0442\u0435\u0440\u0430\u0442\u0443\u0440\u044b, \u043d\u043e.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","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-03-26T05:42:30+00:00","article:modified_time":"2020-03-26T05:42:30+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"75425","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 17:56:30","updated":"2022-10-01 20:34:03","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/75425","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=75425"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/75425\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/75426"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=75425"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=75425"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=75425"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}