{"id":82215,"date":"2020-05-20T13:42:25","date_gmt":"2020-05-20T11:42:25","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness"},"modified":"2020-05-20T13:42:25","modified_gmt":"2020-05-20T11:42:25","slug":"luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","title":{"rendered":"Nejlep\u0161\u00ed praktiky Kubernetes. Kontrola \u017eivotaschopnosti Kubernetes pomoc\u00ed test\u016f Readiness a Liveness","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Nejlep\u0161\u00ed praktiky Kubernetes. Vytv\u00e1\u0159en\u00ed mal\u00fdch kontejner\u016f<\/a><\/noindex>
\nNejlep\u0161\u00ed praktiky Kubernetes. Organizace Kubernetes pomoc\u00ed jmenn\u00e9ho prostoru<\/a><\/noindex><\/p>\n

\"Nejlep\u0161\u00ed
\n
\nS distribuovan\u00fdmi syst\u00e9my m\u016f\u017ee b\u00fdt obt\u00ed\u017en\u00e9 spravovat, proto\u017ee obsahuj\u00ed mnoho pohybliv\u00fdch, m\u011bniteln\u00fdch prvk\u016f, kter\u00e9 mus\u00ed spr\u00e1vn\u011b fungovat, aby byla zaji\u0161t\u011bna funk\u010dnost syst\u00e9mu. Pokud n\u011bkter\u00fd z prvk\u016f sel\u017ee, syst\u00e9m ho mus\u00ed detekovat, obej\u00edt a opravit, p\u0159i\u010dem\u017e to v\u0161e mus\u00ed prob\u00edhat automaticky. V t\u00e9to s\u00e9rii \u201eNejlep\u0161\u00ed praktiky Kubernetes\u201c se dozv\u00edme, jak nastavit testy Readiness a Liveness pro kontrolu \u017eivotaschopnosti klastru Kubernetes.<\/p>\n

Kontrola zdrav\u00ed Health Check je jednoduch\u00fd zp\u016fsob, jak nechat syst\u00e9m v\u011bd\u011bt, zda v\u00e1\u0161 instance aplikace funguje, nebo ne. Pokud instance va\u0161\u00ed aplikace nepracuje, jin\u00e9 slu\u017eby by se k n\u00ed nem\u011bly p\u0159ipojovat ani j\u00ed pos\u00edlat \u017e\u00e1dosti. M\u00edsto toho by m\u011bl b\u00fdt po\u017eadavek zasl\u00e1n jin\u00e9 instanci aplikace, kter\u00e1 je ji\u017e spu\u0161t\u011bna nebo bude spu\u0161t\u011bna pozd\u011bji. Krom\u011b toho by syst\u00e9m m\u011bl vr\u00e1tit va\u0161\u00ed aplikaci ztracenou funk\u010dnost.<\/p>\n

Ve v\u00fdchoz\u00edm nastaven\u00ed za\u010dne Kubernetes sm\u011brovat provoz do podu, kdy\u017e jsou v\u0161echny kontejnery uvnit\u0159 pod\u016f spu\u0161t\u011bny, a restartovat kontejnery, kdy\u017e se sel\u017eou. Pro za\u010d\u00e1tek m\u016f\u017ee b\u00fdt toto chov\u00e1n\u00ed syst\u00e9mu v po\u0159\u00e1dku, ale m\u016f\u017eete zv\u00fd\u0161it spolehlivost nasazen\u00ed sv\u00e9ho produktu pomoc\u00ed vlastn\u00edch kontrol \u017eivotaschopnosti.<\/a><\/noindex><\/p>\n

\"Nejlep\u0161\u00ed
\n
\nNa\u0161t\u011bst\u00ed Kubernetes umo\u017e\u0148uje to prov\u00e9st docela jednodu\u0161e, tak\u017ee neexistuj\u00ed \u017e\u00e1dn\u00e9 v\u00fdmluvy pro ignorov\u00e1n\u00ed takov\u00fdch kontrol. Kubernetes poskytuje dva typy test\u016f Health Check, p\u0159i\u010dem\u017e je d\u016fle\u017eit\u00e9 pochopit rozd\u00edly v pou\u017eit\u00ed ka\u017ed\u00e9ho z nich.<\/p>\n

Test p\u0159ipravenosti Readiness slou\u017e\u00ed k informov\u00e1n\u00ed Kubernetes o p\u0159ipravenosti va\u0161\u00ed aplikace obsluhovat provoz. Ne\u017e povol\u00ed slu\u017eb\u011b pos\u00edlat provoz do podu, mus\u00ed se Kubernetes ujistit, \u017ee test p\u0159ipravenosti prob\u011bhl \u00fasp\u011b\u0161n\u011b. Pokud test Readiness sel\u017ee, Kubernetes p\u0159estane sm\u011brovat provoz do podu, dokud testov\u00e1n\u00ed nebude \u00fasp\u011b\u0161n\u00e9. <\/p>\n

Test \u017eivotaschopnosti Liveness informuje Kubernetes, zda je va\u0161e aplikace \u017eiv\u00e1 nebo mrtv\u00e1. V prvn\u00edm p\u0159\u00edpad\u011b ji Kubernetes ponech\u00e1 na pokoji, v druh\u00e9m odstran\u00ed mrtv\u00fd pod a nahrad\u00ed ho nov\u00fdm. <\/p>\n

P\u0159edstavme si sc\u00e9n\u00e1\u0159, kde va\u0161\u00ed aplikaci trv\u00e1 1 minutu, ne\u017e se zah\u0159eje a spust\u00ed. Va\u0161e slu\u017eba nebude fungovat, dokud se aplikace \u00fapln\u011b nena\u010dte a nespust\u00ed, a\u010dkoli pracovn\u00ed proces u\u017e za\u010dal. Nav\u00edc budete m\u00edt tak\u00e9 probl\u00e9my, pokud se rozhodnete \u0161k\u00e1lovat toto nasazen\u00ed na n\u011bkolik kopi\u00ed, proto\u017ee tyto kopie by nem\u011bly dost\u00e1vat provoz, dokud nebudou \u00fapln\u011b p\u0159ipraven\u00e9. Nicm\u00e9n\u011b, v\u00fdchoz\u00ed nastaven\u00ed Kubernetes za\u010dne pos\u00edlat provoz ihned po zah\u00e1jen\u00ed proces\u016f uvnit\u0159 kontejneru.<\/p>\n

P\u0159i pou\u017eit\u00ed readiness testu bude Kubernetes \u010dekat, dokud aplikace nebude zcela spu\u0161t\u011bna, a teprve pot\u00e9 povol\u00ed slu\u017eb\u011b pos\u00edlat provoz na novou kopii.<\/p>\n

\"Nejlep\u0161\u00ed
\n
\nP\u0159edstavme si jin\u00fd sc\u00e9n\u00e1\u0159, kdy aplikace zamrzne na dlouhou dobu a p\u0159estane obsluhovat po\u017eadavky. Proto\u017ee proces pokra\u010duje v b\u011bhu, Kubernetes ve v\u00fdchoz\u00edm nastaven\u00ed p\u0159edpokl\u00e1d\u00e1, \u017ee je v\u0161e v po\u0159\u00e1dku, a bude nad\u00e1le pos\u00edlat po\u017eadavky na nefunk\u010dn\u00ed pod. P\u0159i pou\u017eit\u00ed liveness testu v\u0161ak Kubernetes zjist\u00ed, \u017ee aplikace ji\u017e neobsluhuje po\u017eadavky, a ve v\u00fdchoz\u00edm nastaven\u00ed restartuje nefunk\u010dn\u00ed pod.<\/p>\n

\"Nejlep\u0161\u00ed
\n
\nPod\u00edvejme se, jak se testuje p\u0159ipravenost a \u017eivotaschopnost. Existuj\u00ed t\u0159i zp\u016fsoby testov\u00e1n\u00ed \u2013 HTTP, Command a TCP. Pro kontrolu m\u016f\u017eete pou\u017e\u00edt kter\u00fdkoli z nich. Nej\u010dast\u011bj\u0161\u00edm zp\u016fsobem u\u017eivatelsk\u00e9ho testov\u00e1n\u00ed je HTTP probe.<\/p>\n

I kdy\u017e va\u0161e aplikace nen\u00ed HTTP server, m\u016f\u017eete si uvnit\u0159 aplikace vytvo\u0159it lehk\u00fd HTTP server pro interakci s liveness testem. Pot\u00e9 Kubernetes za\u010dne pingovat pod, a pokud bude HTTP odpov\u011b\u010f v rozmez\u00ed 200 nebo 300 ms, bude to znamenat, \u017ee pod je \"zdrav\u00fd\". V opa\u010dn\u00e9m p\u0159\u00edpad\u011b bude modul ozna\u010den jako \"nezdrav\u00fd\".<\/p>\n

\"Nejlep\u0161\u00ed
\n
\nPro testy pomoc\u00ed Command Kubernetes vykon\u00e1 p\u0159\u00edkaz uvnit\u0159 va\u0161eho kontejneru. Pokud p\u0159\u00edkaz vr\u00e1t\u00ed nulu jako exit code, pak bude kontejner ozna\u010den jako zdrav\u00fd, jinak, pokud se vr\u00e1t\u00ed \u010d\u00edslo exit status od 1 do 255, bude kontejner ozna\u010den jako \"nemocn\u00fd\". Tento zp\u016fsob testov\u00e1n\u00ed je u\u017eite\u010dn\u00fd, pokud nem\u016f\u017eete nebo nechcete spou\u0161t\u011bt HTTP server, ale m\u016f\u017eete spustit p\u0159\u00edkaz, kter\u00fd zkontroluje \"zdrav\u00ed\" va\u0161\u00ed aplikace.<\/p>\n

\"Nejlep\u0161\u00ed
\n
\nPosledn\u00ed kontroln\u00ed mechanismus je TCP test. Kubernetes se pokus\u00ed nav\u00e1zat TCP spojen\u00ed na ur\u010den\u00e9m portu. Pokud se to poda\u0159\u00ed, kontejner je pova\u017eov\u00e1n za zdrav\u00fd; pokud ne, je pova\u017eov\u00e1n za nefunk\u010dn\u00ed. Tato metoda m\u016f\u017ee b\u00fdt u\u017eite\u010dn\u00e1, pokud pou\u017e\u00edv\u00e1te sc\u00e9n\u00e1\u0159, ve kter\u00e9m testov\u00e1n\u00ed pomoc\u00ed HTTP po\u017eadavku nebo prov\u00e1d\u011bn\u00ed p\u0159\u00edkazu nefunguje p\u0159\u00edli\u0161 dob\u0159e. Nap\u0159\u00edklad hlavn\u00edmi slu\u017ebami pro kontrolu pomoc\u00ed TCP budou gRPC nebo FTP.<\/p>\n

\"Nejlep\u0161\u00ed
\n
\nTesty lze nakonfigurovat n\u011bkolika zp\u016fsoby s r\u016fzn\u00fdmi parametry. M\u016f\u017eete ur\u010dit, jak \u010dasto by se m\u011bly prov\u00e1d\u011bt, jak\u00e9 jsou prahov\u00e9 hodnoty \u00fasp\u011bchu a ne\u00fasp\u011bchu, jak dlouho \u010dekat na odpov\u011bdi. Podrobn\u011bj\u0161\u00ed informace jsou uvedeny v dokumentaci k test\u016fm Readiness a Liveness. Existuje v\u0161ak jeden velmi d\u016fle\u017eit\u00fd aspekt p\u0159i nastaven\u00ed Liveness testu \u2013 po\u010d\u00e1te\u010dn\u00ed zpo\u017ed\u011bn\u00ed testov\u00e1n\u00ed initialDelaySeconds. Jak jsem ji\u017e zm\u00ednil, ne\u00fasp\u011b\u0161n\u00e9 proveden\u00ed tohoto testu povede k restartov\u00e1n\u00ed modulu. Proto se mus\u00edte ujistit, \u017ee testov\u00e1n\u00ed neza\u010dne, dokud aplikace nebude p\u0159ipravena k pr\u00e1ci; jinak za\u010dne neust\u00e1le restartovat. Doporu\u010duji pou\u017e\u00edt pr\u016fm\u011brn\u00fd \u010das spu\u0161t\u011bn\u00ed aplikace nebo P99 \u010das spu\u0161t\u011bn\u00ed z vyrovn\u00e1vac\u00ed pam\u011bti. Nezapome\u0148te upravit tuto hodnotu, jak se \u010das spu\u0161t\u011bn\u00ed va\u0161\u00ed aplikace zrychluje nebo zpomaluje.<\/p>\n

V\u011bt\u0161ina odborn\u00edk\u016f potvrd\u00ed, \u017ee Health Check je povinnou kontrolou pro jak\u00fdkoli rozlo\u017een\u00fd syst\u00e9m, a Kubernetes nen\u00ed v\u00fdjimkou. Pou\u017eit\u00ed kontroly 'zdrav\u00ed' slu\u017eeb zaji\u0161\u0165uje spolehliv\u00fd a bezporuchov\u00fd provoz Kubernetes a pro u\u017eivatele to neznamen\u00e1 \u017e\u00e1dnou n\u00e1mahu. <\/p>\n

Pokra\u010dov\u00e1n\u00ed bude brzy\u2026<\/p>\n

\r\n \"P\u0159ehr\u00e1t\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Mal\u00e1 reklama \ud83d\ude42<\/h3>\n

\nD\u011bkujeme, \u017ee s n\u00e1mi z\u016fst\u00e1v\u00e1te. L\u00edb\u00ed se v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vid\u011bt v\u00edce zaj\u00edmav\u00fdch materi\u00e1l\u016f? Podpo\u0159te n\u00e1s objedn\u00e1vkou nebo doporu\u010den\u00edm zn\u00e1m\u00fdm, cloudov\u00e9 VPS pro v\u00fdvoj\u00e1\u0159e od 4,99 $<\/a><\/noindex>, unik\u00e1tn\u00ed alternativa entry-level server\u016f, kterou jsme pro v\u00e1s vymysleli:<\/b> V\u0161echny pravdy o VPS (KVM) E5-2697 v3 (6 jader) 10GB DDR4 480GB SSD 1Gbps od 19 $ nebo jak spr\u00e1vn\u011b rozd\u011blit server?<\/a><\/noindex> (k dispozici varianty s RAID1 a RAID10, a\u017e 24 jader a a\u017e 40GB DDR4).<\/p>\n

Dell R730xd je dvakr\u00e1t levn\u011bj\u0161\u00ed v datov\u00e9m centru Equinix Tier IV v Amsterdamu?<\/b> Jen u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 $<\/a><\/noindex> v Nizozemsku! Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 $!<\/b><\/b> \u010ct\u011bte o tom Jak postavit infrastrukturu podnikov\u00e9 t\u0159\u00eddy s pou\u017eit\u00edm server\u016f Dell R730xd E5-2650 v4 v hodnot\u011b 9000 eur za pakatel?<\/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 \u0420\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u043c\u0438 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c\u0438 \u0431\u044b\u0432\u0430\u0435\u0442 \u0442\u0440\u0443\u0434\u043d\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u043f\u043e \u043f\u0440\u0438\u0447\u0438\u043d\u0435 \u0442\u043e\u0433\u043e, \u0447\u0442\u043e \u0432 \u043d\u0438\u0445 \u0438\u043c\u0435\u0435\u0442\u0441\u044f \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e \u043f\u043e\u0434\u0432\u0438\u0436\u043d\u044b\u0445 \u0438\u0437\u043c\u0435\u043d\u044f\u0435\u043c\u044b\u0445 \u044d\u043b\u0435\u043c\u0435\u043d\u0442\u043e\u0432, \u0438 \u0432\u0441\u0435 \u043e\u043d\u0438 \u0434\u043e\u043b\u0436\u043d\u044b \u043d\u043e\u0440\u043c\u0430\u043b\u044c\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u0434\u043b\u044f \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0441\u0438\u0441\u0442\u0435\u043c\u044b. \u0415\u0441\u043b\u0438 \u043e\u0434\u0438\u043d \u0438\u0437 \u044d\u043b\u0435\u043c\u0435\u043d\u0442\u043e\u0432 \u0432\u044b\u0439\u0434\u0435\u0442 \u0438\u0437 \u0441\u0442\u0440\u043e\u044f, \u0442\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0434\u043e\u043b\u0436\u043d\u0430 \u0435\u0433\u043e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u0442\u044c, \u043e\u0431\u043e\u0439\u0442\u0438 \u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":82216,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-82215","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\udd47Nejlep\u0161\u00ed praktiky Kubernetes. Kontrola \u017eivotaschopnosti Kubernetes pomoc\u00ed test\u016f Readiness a Liveness | ProHoster","description":"Nejlep\u0161\u00ed praktiky Kubernetes.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","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 \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 | ProHoster","og:description":"\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","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:25+00:00","article:modified_time":"2020-05-20T11:42:25+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"82215","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:42:27","updated":"2022-09-29 19:26:23","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\/82215","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=82215"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/82215\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/82216"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=82215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=82215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=82215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}