{"id":54987,"date":"2020-01-09T00:00:00","date_gmt":"2020-01-08T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery"},"modified":"2020-02-18T14:03:03","modified_gmt":"2020-02-18T11:03:03","slug":"istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","title":{"rendered":"Istio Circuit Breaker: l\u00fclitame v\u00e4lja rikki l\u00e4inud konteinerid","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00fchad on l\u00e4bi, ja me naaseme oma teise postitusega Istio Service Meshi seerias.<\/p>\n

\"Istio
\n
\nT\u00e4na r\u00e4\u00e4gime Circuit Breaker'ist, mis t\u00e4hendab eesti keeles 'automaatkaitse', slangikeeles - 'kaitseautomaat'. Ainult et Istios see automaat ei katkesta katkenud v\u00f5i \u00fclekoormatud voolu, vaid riknenud konteinerid.
\n<\/a><\/noindex><\/p>\n

Nii peaks see ideaalis toimima<\/h3>\n

\nKui mikroteenuseid haldab Kubernetes, n\u00e4iteks platvormi OpenShift raames, siis need skaleeruvad automaatselt \u00fcles- ja allapoole vastavalt koormusele. Kuna mikroteenused t\u00f6\u00f6tavad pod'ides, v\u00f5ib \u00fchel l\u00f5pp-punktil olla korraga mitu konteinerit, ning Kubernetes suunab p\u00e4ringud nende vahel ja tasakaalustab koormuse. Ja - ideaalis - peaks see k\u00f5ik suurep\u00e4raselt toimima.<\/p>\n

Meeles peate, et mikroteenused on v\u00e4ikesed ja m\u00f6\u00f6duvad. M\u00f6\u00f6duvus, mis siin t\u00e4hendab lihtsust tekkida ja kaduda, on sageli alahinnatud. Mikroteenuse s\u00fcnd ja surm pod'is on t\u00e4iesti ootusp\u00e4rased, OpenShift ja Kubernetes saavad selle v\u00e4ga h\u00e4sti hakkama ning k\u00f5ik toimib suurep\u00e4raselt \u2013 kuid j\u00e4lle teoorias.<\/p>\n

Kuidas see tegelikult t\u00f6\u00f6tab<\/h3>\n

\nN\u00fc\u00fcd kujutage ette, et mingi konkreetne mikroteenuse instants, ehk konteiner, on rikki l\u00e4inud: kas ei vasta (vea 503) v\u00f5i \u2013 mis on veel hullem \u2013 reageerib, kuid liiga aeglaselt. Teisis\u00f5nu, ta k\u00e4itub aeglaselt v\u00f5i ei vasta p\u00e4ringutele, kuid samas ei eemaldata teda automaatselt reservi. Mida sel juhul ette v\u00f5tta? Korduskatse? Eemaldada see marsruudist? Ja mis t\u00e4hendab \u201eliiga aeglaselt\u201d \u2013 kui palju see numbrites on ja kes m\u00e4\u00e4rab need? Kas v\u00f5ib-olla tuleks talle lihtsalt paus anda ja proovida hiljem? Kui jah, siis kui kaua hiljem?<\/p>\n

Mis on Pool Ejection Istios<\/h3>\n

\nJa siin tuleb appi Istio oma Circuit Breaker automaatidega, mis ajutiselt eemaldavad vigased konteinerid marsruutimise ja koormuse tasakaalustamise ressursside kassist, rakendades protseduuri Pool Ejection.<\/p>\n

Kasutades k\u00f5rvalekallete tuvastamise strateegiat (outlier detection), tuvastab Istio eba\u00f5iged pod\u2019id, mis eristuvad tavalisest, ja eemaldab nad m\u00e4\u00e4ratud ajaks ressursside kassist, mida nimetatakse 'unere\u017eiimiks' (sleep window). <\/p>\n

K\u00fcsimiseks, kuidas see Kuberneteses platvormil OpenShift t\u00f6\u00f6tab, alustame ekraanipildist normaalselt toimivatest mikroteenustest n\u00e4ites hoidlast. Red Hat Developer Demos<\/a><\/noindex>. Siin on meil kaks pod\u2019i, v1 ja v2, millest igas t\u00f6\u00f6tab \u00fcks konteiner. Kui Istio marsruutimise reegleid ei kasutata, rakendab Kubernetes vaikimisi \u00fchtlaselt tasakaalustatud ts\u00fcklilist marsruuti:<\/p>\n

\"Istio<\/p>\n

Valmistume rikke jaoks<\/h3>\n

\nEnne Pool Ejection\u2019it tuleb luua Istio marsruutimise reegel. Oletame, et soovime jaotada p\u00e4ringud pod\u2019ide vahel suhtega 50\/50. Lisaks suurendame konteinerite arvu v2-l \u00fchest kahele, nagu siin:<\/p>\n

oc scale deployment recommendation-v2 --replicas=2 -n tutorial\n<\/code><\/pre>\n
\nSeame reeglid suunamiseks, et liiklus jaguneks-pod'ide vahel 50\/50.<\/p>\n
\"Istio
\nNii n\u00e4eb selle reegli t\u00f6\u00f6 tulemus v\u00e4lja:<\/p>\n
\"Istio
\nV\u00f5ib \u00f6elda, et sellel ekraanil ei ole 50\/50, vaid 14:9, kuid aja jooksul olukord stabiliseerub.<\/p>\n
Teeme rikke<\/h3>\n
\nN\u00fc\u00fcd viime \u00fche kahest konteinerist v2 rikki, et meil oleks \u00fcks t\u00f6\u00f6tav konteiner v1, \u00fcks t\u00f6\u00f6tav konteiner v2 ja \u00fcks rikki minna konteiner v2: <\/p>\n
\"Istio<\/p>\n
Parandame rikke<\/h3>\n
\nNii, meil on rikki l\u00e4inud konteiner ja aeg on Pool Ejectiooni jaoks. V\u00e4ga lihtsa konfiguraatori abil v\u00e4listame selle rikki l\u00e4inud konteineri mis tahes suunamisest 15 sekundiks, lootuses, et see taastub (kas ta taask\u00e4ivitub v\u00f5i taastab oma j\u00f5udluse). Nii n\u00e4eb see konfiguratsioon v\u00e4lja ja millised on selle tulemused:<\/p>\n
\"Istio
\n\"Istio
\nNagu n\u00e4ha, ei kasutata rikki l\u00e4inud konteinerit v2 enam p\u00e4ringute suunamiseks, kuna see on puul v\u00e4lja toodud. Kuid 15 sekundi m\u00f6\u00f6dumisega naaseb see automaatselt puusse. Tegelikult just n\u00e4itasime, kuidas Pool Ejectioon t\u00f6\u00f6tab.<\/p>\n
Alustame arhitektuuri loomist<\/h3>\n
\nPool Ejection koos Istio j\u00e4lgimisv\u00f5imalustega v\u00f5imaldab luua automaatse rikke p\u00f5hjustanud konteinerite asendamise raamistikku, et v\u00e4hendada v\u00f5i isegi t\u00e4ielikult k\u00f5rvaldada seiskumisi ja t\u00f5rkeid.
\n\u2003
\nNASA-l on \u00fcks tuntud moto \u2013 Failure Is Not an Option, mille autor on lennujuht. Gene Kranz<\/a><\/noindex>. Selle t\u00f5lge eesti keelde on \u201eEba\u00f5nnestumine ei ole variant\u201c, ja m\u00f5te on selles, et k\u00f5ik on v\u00f5imalik t\u00f6\u00f6le panna, kui on piisavalt tahet. Kuid tegelikus elus ei juhtu t\u00f5rked lihtsalt, need on v\u00e4ltimid, k\u00f5ikjal ja igal pool. Kuidas nendega siis toime tulla mikroteenustes? Meie arvates on parem toetuda mitte tahtej\u00f5ule, vaid konteinerite v\u00f5imalustele. Kubernetes<\/a><\/noindex>, Red Hat OpenShift<\/a><\/noindex>, ja Istio<\/a><\/noindex>.<\/p>\n
Istio rakendab nagu eelpool nimetatud automaatse kaitsel\u00fcliti kontseptsioon, mis on end f\u00fc\u00fcsilises maailmas t\u00f5estanud. Nii nagu elektriline kaitsel\u00fcliti katkestab probleemse ahela osa, katkestab programmi Circuit Breaker Istios \u00fchenduse p\u00e4ringute voo ja probleemse konteineri vahel, kui l\u00f5pp-punktiga on midagi valesti, n\u00e4iteks kui server on maha kukkunud v\u00f5i hakkab rahmeldama.<\/p>\n
Teises olukorras on probleeme veelgi rohkem, kuna \u00fche konteineri pidurid mitte ainult ei p\u00f5hjusta kaskaadset viivitust sellele juurdep\u00e4\u00e4suga teenustes, v\u00e4hendades seel\u00e4bi s\u00fcsteemi \u00fcldist j\u00f5udlust, vaid tekitavad ka korduvaid p\u00e4ringuid juba niigi aeglases teenuses, mis vaid s\u00fcvendab olukorda.<\/p>\n
Circuit Breaker teoorias<\/h3>\n
\nCircuit Breaker \u2013 see proxy, which controls the flow of requests to an endpoint. When this endpoint stops working or, depending on the configured settings, starts lagging, the proxy breaks the connection with the container. Traffic is then redirected to other containers simply due to load balancing. The connection remains open for a specified sleep window, say two minutes, after which it is considered half-open. An attempt to send the next request determines the further state of the connection. If everything is fine with the service, the connection returns to operational state and becomes closed again. If, however, there is still an issue with the service, the connection opens again and the sleep window is reactivated. Here\u2019s a simplified state change diagram of the Circuit Breaker:<\/p>\n
\"Istio
\nSiin on oluline m\u00e4rkida, et kogu see toimub s\u00fcsteemi arhitektuuri tasemel. Seet\u00f5ttu peate mingi hetk \u00f5petama oma rakendusi t\u00f6\u00f6tama Circuit Breakeriga, n\u00e4iteks andma vastuseks vaikimisi v\u00e4\u00e4rtuse v\u00f5i, kui see on v\u00f5imalik, ignoreerima teenuse olemasolu. Selleks kasutatakse bulkhead pattern'i, kuid see j\u00e4\u00e4b v\u00e4lja selle artikli raamist.<\/p>\n
Circuit Breaker praktikas<\/h3>\n
\nN\u00e4iteks k\u00e4ivitame OpenShiftis kaks versiooni meie soovituste mikroteenusest. Versioon 1 t\u00f6\u00f6tab normaalselt, kuid v2-s lisame viivituse, et simuleerida serveri aeglustusi. Tulemuste vaatamiseks kasutatakse t\u00f6\u00f6riista siege<\/a><\/noindex>:<\/p>\n
siege -r 2 -c 20 -v customer-tutorial.$(minishift ip).nip.io\n<\/code><\/pre>\n
\n\"Istio
\nK\u00f5ik tundub t\u00f6\u00f6tavat, aga mis hinnaga? Esmapilgul on meil 100% k\u00e4ttesaadavus, kuid vaadake l\u00e4hemalt \u2013 maksimumm aega tehingu jaoks on tervelt 12 sekundit. See on selgelt kitsaskohaks ja seda tuleb avardada.<\/p>\n
Selleks v\u00e4listame Istio abil \u00fchendused aeglaste konteineritega. Niisiis, selline on vastav konfigureerimine, kasutades Circuit Breakerit:<\/p>\n
\"Istio
\nViimane rida parameetriga httpMaxRequestsPerConnection n\u00e4itab, et \u00fchendus tuleb katkestada, kui \u00fcritatakse luua veel \u00fcks \u2013 teine \u2013 \u00fchendus olemasoleva k\u00f5rval. Kuna meie konteiner simuleerib aeglustavat teenust, esinevad sellised olukorrad perioodiliselt ja siis tagastab Istio vea 503, aga mida n\u00e4itab siege:<\/p>\n
\"Istio<\/p>\n
Okei, meil on Circuit Breaker, mis edasi?<\/h3>\n
\nNii et oleme rakendanud automaatse katkestamise, puutumatult muutmata teenuste algkoodi. Kasutades Circuit Breakerit ja eespool kirjeldatud protseduuri Pool Ejection, saame eemaldada aeglustavad konteinerid ressursi reservuaarist, kuni nad normaliseeruvad, ning kontrollida nende staatust m\u00e4\u00e4ratud ajavahemiku j\u00e4rel \u2013 meie n\u00e4ites on see kaks minutit (parameeter sleepWindow).<\/p>\n
Pange t\u00e4hele, et rakenduse v\u00f5ime reageerida veale 503 m\u00e4\u00e4ratakse endiselt selle algkoodi tasemel. On mitmeid Circuit Breakeri t\u00f6\u00f6strateegiaid, mida rakendatakse s\u00f5ltuvalt olukorrast.<\/p>\n
J\u00e4rgmises postituses:<\/b> r\u00e4\u00e4gime j\u00e4lgimisest ja monitooringust, mis on juba sisseehitatud v\u00f5i kergesti lisatavad Istiosse, ning sellest, kuidas s\u00fcsteemi vigu teadlikult sisestada.
\n
Allikas: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041f\u0440\u0430\u0437\u0434\u043d\u0438\u043a\u0438 \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u043b\u0438\u0441\u044c, \u0438 \u043c\u044b \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u0435\u043c\u0441\u044f \u0441 \u043d\u0430\u0448\u0438\u043c \u0432\u0442\u043e\u0440\u044b\u043c \u043f\u043e\u0441\u0442\u043e\u043c \u0438\u0437 \u0441\u0435\u0440\u0438\u0438 \u043f\u043e Istio Service Mesh. \u0421\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u044f\u044f \u0442\u0435\u043c\u0430 \u2013 Circuit Breaker, \u0447\u0442\u043e \u0432 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0435 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0437\u043d\u0430\u0447\u0430\u0435\u0442 \u00ab\u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u0432\u044b\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c\u00bb, \u0432 \u043f\u0440\u043e\u0441\u0442\u043e\u0440\u0435\u0447\u0438\u0438 \u2013 \u00ab\u0430\u0432\u0442\u043e\u043c\u0430\u0442 \u0437\u0430\u0449\u0438\u0442\u044b\u00bb. \u0422\u043e\u043b\u044c\u043a\u043e \u0432 Istio \u044d\u0442\u043e\u0442 \u0430\u0432\u0442\u043e\u043c\u0430\u0442 \u043e\u0442\u043a\u043b\u044e\u0447\u0430\u0435\u0442 \u043d\u0435 \u043a\u043e\u0440\u043e\u0442\u043d\u0443\u0432\u0448\u0443\u044e \u0438\u043b\u0438 \u043f\u0435\u0440\u0435\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u0443\u044e \u0446\u0435\u043f\u044c, \u0430 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u044b\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b. \u041a\u0430\u043a \u044d\u0442\u043e \u0434\u043e\u043b\u0436\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u0432 \u0438\u0434\u0435\u0430\u043b\u0435 \u041a\u043e\u0433\u0434\u0430 […]<\/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-54987","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\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\udd47Istio Circuit Breaker: l\u00fclitame v\u00e4lja riknenud konteinerid | ProHoster","description":"P\u00fchad on l\u00e4bi ja naaseme oma teise postitusega Istio Service Meshi seeriast. T\u00e4na k\u00e4sitleme teemat \u2013 Circuit Breaker, mis elektrotehnikas t\u00e4hendab automaatset v\u00e4ljal\u00fclitust, rahvap\u00e4raselt tuntud kui kaitseautomaat. Ainult et Istios see automaat ei l\u00fclita v\u00e4lja l\u00fchist ega \u00fclekoormatud ahelat, vaid riknenud konteinerid. Kuidas see peaks ideaalis toimima?","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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\udd47Istio Circuit Breaker: \u043e\u0442\u043a\u043b\u044e\u0447\u0430\u0435\u043c \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u044b\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b | ProHoster","og:description":"\u041f\u0440\u0430\u0437\u0434\u043d\u0438\u043a\u0438 \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u043b\u0438\u0441\u044c, \u0438 \u043c\u044b \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u0435\u043c\u0441\u044f \u0441 \u043d\u0430\u0448\u0438\u043c \u0432\u0442\u043e\u0440\u044b\u043c \u043f\u043e\u0441\u0442\u043e\u043c \u0438\u0437 \u0441\u0435\u0440\u0438\u0438 \u043f\u043e Istio Service Mesh. \u0421\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u044f\u044f \u0442\u0435\u043c\u0430 \u2013 Circuit Breaker, \u0447\u0442\u043e \u0432 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0435 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0437\u043d\u0430\u0447\u0430\u0435\u0442 \u00ab\u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u0432\u044b\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c\u00bb, \u0432 \u043f\u0440\u043e\u0441\u0442\u043e\u0440\u0435\u0447\u0438\u0438 \u2013 \u00ab\u0430\u0432\u0442\u043e\u043c\u0430\u0442 \u0437\u0430\u0449\u0438\u0442\u044b\u00bb. \u0422\u043e\u043b\u044c\u043a\u043e \u0432 Istio \u044d\u0442\u043e\u0442 \u0430\u0432\u0442\u043e\u043c\u0430\u0442 \u043e\u0442\u043a\u043b\u044e\u0447\u0430\u0435\u0442 \u043d\u0435 \u043a\u043e\u0440\u043e\u0442\u043d\u0443\u0432\u0448\u0443\u044e \u0438\u043b\u0438 \u043f\u0435\u0440\u0435\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u0443\u044e \u0446\u0435\u043f\u044c, \u0430 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u044b\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b. \u041a\u0430\u043a \u044d\u0442\u043e \u0434\u043e\u043b\u0436\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u0432 \u0438\u0434\u0435\u0430\u043b\u0435 \u041a\u043e\u0433\u0434\u0430","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","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-01-08T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:03+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"54987","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-01-24 13:26:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:54:34","updated":"2026-01-24 13:26:19"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/54987","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=54987"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/54987\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=54987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=54987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=54987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}