{"id":82913,"date":"2020-05-26T13:42:32","date_gmt":"2020-05-26T11:42:32","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate"},"modified":"2020-05-26T13:42:32","modified_gmt":"2020-05-26T11:42:32","slug":"luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","title":{"rendered":"Najlep\u0161ie praktiky Kubernetes. Spr\u00e1vne vyp\u00ednanie Terminate","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Najlep\u0161ie praktiky Kubernetes. Vytvorenie mal\u00fdch kontajnerov<\/a><\/noindex>
\nNajlep\u0161ie praktiky Kubernetes. Organiz\u00e1cia Kubernetes s men\u0161\u00edm priestorom<\/a><\/noindex>
\nNajlep\u0161ie praktiky Kubernetes. Kontrola \u017eivotaschopnosti Kubernetes pomocou Readiness a Liveness testov<\/a><\/noindex>
\nNajlep\u0161ie praktiky Kubernetes. Nastavenie po\u017eiadaviek a limitov zdrojov<\/a><\/noindex><\/p>\n

\"Najlep\u0161ie
\n
\nD\u00f4le\u017eit\u00fdm aspektom fungovania distribuovan\u00fdch syst\u00e9mov je spracovanie por\u00fach. Kubernetes s t\u00fdm pom\u00e1ha pomocou ovl\u00e1da\u010dov, ktor\u00e9 sleduj\u00fa stav v\u00e1\u0161ho syst\u00e9mu a re\u0161tartuj\u00fa nepracuj\u00face slu\u017eby. Av\u0161ak Kubernetes m\u00f4\u017ee n\u00fatene zastavi\u0165 fungovanie aplik\u00e1ci\u00ed, aby zabezpe\u010dil celkov\u00fa \u017eivotaschopnos\u0165 syst\u00e9mu. V tejto s\u00e9rii sa pozrieme na to, ako m\u00f4\u017eete pom\u00f4c\u0165 Kubernetes vykon\u00e1va\u0165 svoju pr\u00e1cu efekt\u00edvnej\u0161ie a skr\u00e1ti\u0165 \u010das v\u00fdpadku aplik\u00e1ci\u00ed. <\/a><\/noindex><\/p>\n

Predt\u00fdm, ne\u017e sa za\u010dalo pou\u017e\u00edva\u0165 kontajnerov\u00e9 technol\u00f3gie, v\u00e4\u010d\u0161ina aplik\u00e1ci\u00ed fungovala na virtu\u00e1lnych alebo fyzick\u00fdch strojoch. Ak aplik\u00e1cia zlyhala alebo zamrzla, trvalo ve\u013ea \u010dasu, k\u00fdm sa \u00faloha zastavila a program znova na\u010d\u00edtal. V najhor\u0161om pr\u00edpade sa niekto musel s touto probl\u00e9movou situ\u00e1ciou vysporiada\u0165 manu\u00e1lne v noci, v \u00faplne nevhodnom \u010dase. Ak sa d\u00f4le\u017eit\u00e1 \u00faloha vykon\u00e1vala iba na 1-2 pracovn\u00fdch strojoch, tak\u00e9to zlyhanie bolo \u00faplne neprijate\u013en\u00e9.
\nPreto sa namiesto ru\u010dn\u00e9ho re\u0161tartu za\u010dalo pou\u017e\u00edva\u0165 monitorovanie na \u00farovni procesov na automatick\u00e9 re\u0161tartovanie aplik\u00e1cie v pr\u00edpade jej hav\u00e1rie. Ak program zlyh\u00e1, monitorovac\u00ed proces zachyt\u00ed exit-k\u00f3d a re\u0161tartuje server. S pr\u00edchodom tak\u00fdch syst\u00e9mov, ak\u00fdm je Kubernetes, bol tento sp\u00f4sob reakcie na poruchy jednoducho integrovan\u00fd do infra\u0161trukt\u00fary.<\/p>\n

Kubernetes vyu\u017e\u00edva slu\u010dku udalost\u00ed \"sledovanie \u2013 zaznamen\u00e1vanie rozdielov \u2013 vykonanie akcie\", aby sa ubezpe\u010dil, \u017ee zdroje zost\u00e1vaj\u00fa funk\u010dn\u00e9 na ceste z kontajnerov k samotn\u00fdm uzlom.<\/p>\n

\"Najlep\u0161ie
\n
\nTo znamen\u00e1, \u017ee u\u017e nemus\u00edte ru\u010dne sp\u00fa\u0161\u0165a\u0165 monitorovanie procesov. Ak zdroj neprejde testom zdravotnej kontroly Health Check, Kubernetes mu jednoducho automaticky poskytne n\u00e1hradu. Pri tom Kubernetes rob\u00ed ove\u013ea viac, ne\u017e len sleduje poruchy va\u0161ich aplik\u00e1ci\u00ed. M\u00f4\u017ee vytv\u00e1ra\u0165 viac k\u00f3pi\u00ed aplik\u00e1cie pre viacer\u00e9 stroje, aktualizova\u0165 aplik\u00e1ciu alebo s\u00fa\u010dasne sp\u00fa\u0161\u0165a\u0165 viac verzi\u00ed va\u0161ej aplik\u00e1cie.
\nExistuje mnoho d\u00f4vodov, pre\u010do m\u00f4\u017ee Kubernetes preru\u0161i\u0165 pr\u00e1cu \u00faplne zdrav\u00e9ho kontajnera. Napr\u00edklad, ak aktualizujete svoje nasadenie, Kubernetes pomaly zastav\u00ed star\u00e9 pody a z\u00e1rove\u0148 sp\u00fa\u0161\u0165a nov\u00e9. Ak odpoj\u00edte uzol, Kubernetes zastav\u00ed v\u0161etky pody na tomto uzle. Nakoniec, ak uzlu d\u00f4jdu zdroje, Kubernetes vypne v\u0161etky pody, aby uvo\u013enil tieto zdroje.<\/p>\n

Je preto ve\u013emi d\u00f4le\u017eit\u00e9, aby va\u0161a aplik\u00e1cia prestala fungova\u0165 s minim\u00e1lnym dopadom na koncov\u00e9ho pou\u017e\u00edvate\u013ea a minim\u00e1lnym \u010dasom obnovy. To znamen\u00e1, \u017ee pred odpojen\u00edm by mala ulo\u017ei\u0165 v\u0161etky \u00fadaje, ktor\u00e9 je potrebn\u00e9 zachr\u00e1ni\u0165, uzavrie\u0165 v\u0161etky sie\u0165ov\u00e9 pripojenia, dokon\u010di\u0165 zvy\u0161n\u00fa pr\u00e1cu a stihn\u00fa\u0165 vykona\u0165 \u010fal\u0161ie naliehav\u00e9 \u00falohy.<\/p>\n

V praxi to znamen\u00e1, \u017ee va\u0161a aplik\u00e1cia by mala vedie\u0165 spracova\u0165 sign\u00e1l SIGTERM \u2013 sign\u00e1l na ukon\u010denie procesu, ktor\u00fd je predvolen\u00fdm sign\u00e1lom pre utilitu kill v opera\u010dn\u00fdch syst\u00e9moch rodiny Unix. Po prijat\u00ed tohto sign\u00e1lu by sa aplik\u00e1cia mala vypn\u00fa\u0165.<\/p>\n

Po tom, \u010do sa Kubernetes rozhodne ukon\u010di\u0165 pod, sa odohr\u00e1 s\u00e9ria udalost\u00ed. Po\u010fme sa pozrie\u0165 na ka\u017ed\u00fd krok, ktor\u00fd Kubernetes vykon\u00e1va pri vypnut\u00ed kontajnera alebo podu.<\/p>\n

Predpokladajme, \u017ee chceme ukon\u010di\u0165 jeden z podov. V tomto momente prestane prij\u00edma\u0165 nov\u00fd traffic \u2013 be\u017eiace kontajnery v pode nebud\u00fa ovplyvnen\u00e9, ale cel\u00fd nov\u00fd traffic bude zablokovan\u00fd.<\/p>\n

\"Najlep\u0161ie
\n
\nPozrime sa na hook preStop \u2013 to je \u0161peci\u00e1lny pr\u00edkaz alebo HTTP po\u017eiadavka, ktor\u00e1 sa odosiela kontajnerom v pode. Ak sa va\u0161a aplik\u00e1cia pri prijat\u00ed SIGTERM nezavrie spr\u00e1vne, m\u00f4\u017eete pou\u017ei\u0165 preStop na spr\u00e1vne ukon\u010denie pr\u00e1ci. <\/p>\n

\"Najlep\u0161ie
\n
\nV\u00e4\u010d\u0161ina programov pri prijat\u00ed sign\u00e1lu SIGTERM spr\u00e1vne ukon\u010d\u00ed svoju pr\u00e1cu, ale ak pou\u017e\u00edvate cudz\u00ed k\u00f3d alebo nejak\u00fd syst\u00e9m, ktor\u00fd nem\u00f4\u017eete \u00faplne kontrolova\u0165, hook preStop je skvel\u00fd sp\u00f4sob, ako dosiahnu\u0165 elegantn\u00e9 vypnutie bez zmeny aplik\u00e1cie.<\/p>\n

Po vykonan\u00ed tohto hooku Kubernetes po\u0161le kontajnerom v pode sign\u00e1l SIGTERM, ktor\u00fd im d\u00e1 vedie\u0165, \u017ee \u010doskoro bud\u00fa vypnut\u00e9. Po prijat\u00ed tohto sign\u00e1lu sa v\u00e1\u0161 k\u00f3d presunie do procesu vyp\u00ednania. Tento proces m\u00f4\u017ee zah\u0155\u0148a\u0165 zastavenie ak\u00fdchko\u013evek dlhodob\u00fdch spojen\u00ed, ako je pripojenie k datab\u00e1ze alebo WebSocket pr\u00fad, ulo\u017eenie aktu\u00e1lneho stavu a podobne.<\/p>\n

Aj ke\u010f pou\u017e\u00edvate hook preStop, je ve\u013emi d\u00f4le\u017eit\u00e9 skontrolova\u0165, \u010do sa s va\u0161ou aplik\u00e1ciou deje, ke\u010f jej po\u0161lete sign\u00e1l SIGTERM, ako sa spr\u00e1va, aby ste predi\u0161li neo\u010dak\u00e1van\u00fdm udalostiam alebo zmen\u00e1m v prev\u00e1dzke syst\u00e9mu sp\u00f4soben\u00fdm vypnut\u00edm poda.<\/p>\n

V tomto momente, predt\u00fdm ne\u017e podniknete \u010fal\u0161ie kroky, Kubernetes \u010dak\u00e1 po\u010das stanoven\u00e9ho \u010dasu, naz\u00fdvan\u00e9ho terminationGracePeriodSecond, alebo obdob\u00edm pre riadne vyp\u00ednanie po prijat\u00ed sign\u00e1lu SIGTERM.<\/p>\n

\"Najlep\u0161ie
\n
\nPredvolene je toto obdobie 30 sek\u00fand. Je d\u00f4le\u017eit\u00e9 poznamena\u0165, \u017ee prebieha s\u00fa\u010dasne s preStop hook a sign\u00e1lom SIGTERM. Kubernetes nebude \u010daka\u0165, k\u00fdm sa dokon\u010d\u00ed preStop hook a SIGTERM \u2014 ak va\u0161a aplik\u00e1cia ukon\u010d\u00ed pr\u00e1cu pred skon\u010den\u00edm obdobia TerminationGracePeriod, Kubernetes okam\u017eite prejde na \u010fal\u0161\u00ed krok. Skontrolujte, aby hodnota tohto obdobia v sekund\u00e1ch nebola men\u0161ia ne\u017e \u010das potrebn\u00fd na riadne vyp\u00ednanie poda, a ak presahuje 30 sek\u00fand, pred\u013a\u017ete obdobie na potrebn\u00fa hodnotu v YAML. V uvedenom pr\u00edklade je to 60 sek\u00fand.<\/p>\n

A nakoniec, posledn\u00fd krok \u2014 ak kontajnery st\u00e1le pracuj\u00fa po uplynut\u00ed terminationGracePeriod, po\u0161l\u00fa sign\u00e1l SIGKILL a bud\u00fa n\u00fatene odstr\u00e1nen\u00e9. V tomto momente Kubernetes tie\u017e vy\u010dist\u00ed v\u0161etky ostatn\u00e9 objekty poda.<\/p>\n

\"Najlep\u0161ie
\n
\nKubernetes ukon\u010duje pod-y z mnoh\u00fdch d\u00f4vodov, a preto sa uistite, \u017ee va\u0161a aplik\u00e1cia bude v\u017edy ukon\u010den\u00e1 spr\u00e1vne, aby sa zabezpe\u010dila stabiln\u00e1 prev\u00e1dzka slu\u017eby. <\/p>\n

Najlep\u0161ie praktiky Kubernetes. Mapovanie vonkaj\u0161\u00edch slu\u017eieb <\/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 \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 \u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u041f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u0436\u0438\u0437\u043d\u0435\u0441\u043f\u043e\u0441\u043e\u0431\u043d\u043e\u0441\u0442\u0438 Kubernetes \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0435\u0441\u0442\u043e\u0432 Readiness \u0438 Liveness \u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0438 \u043b\u0438\u043c\u0438\u0442\u043e\u0432 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0412\u0430\u0436\u043d\u044b\u043c \u043c\u043e\u043c\u0435\u043d\u0442\u043e\u043c \u0432 \u0440\u0430\u0431\u043e\u0442\u0435 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0430 \u0441\u0431\u043e\u0435\u0432. Kubernetes \u043f\u043e\u043c\u043e\u0433\u0430\u0435\u0442 \u0432 \u044d\u0442\u043e\u043c, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0441\u043b\u0435\u0434\u044f\u0442 \u0437\u0430 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435\u043c \u0432\u0430\u0448\u0435\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":82914,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-82913","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. Riadne vyp\u00ednanie Terminate | ProHoster","description":"Najlep\u0161ie praktiky Kubernetes.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","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. \u041a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u043e\u0435 \u043e\u0442\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 Terminate | 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-korrektnoe-otklyuchenie-terminate","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-26T11:42:32+00:00","article:modified_time":"2020-05-26T11:42:32+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"82913","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:28:37","updated":"2022-09-29 17:02:01","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\/82913","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=82913"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/82913\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/82914"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=82913"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=82913"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=82913"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}