{"id":70831,"date":"2020-02-21T14:42:15","date_gmt":"2020-02-21T11:42:15","guid":{"rendered":"https:\/\/prohoster.info\/blog\/obnovlenie-kubernetes-klastera-bez-prostoya"},"modified":"2020-03-03T16:14:45","modified_gmt":"2020-03-03T13:14:45","slug":"obnovlenie-kubernetes-klastera-bez-prostoya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/obnovlenie-kubernetes-klastera-bez-prostoya","title":{"rendered":"Oppdatering av Kubernetes-klyngen uten nedetid","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Oppdatering av Kubernetes-klyngen uten nedetid\" src=\"\/wp-content\/uploads\/2020\/02\/53cdba726a58c16679c6443191f28321.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><em>Oppdateringsprosessen for Kubernetes-klyngen din<\/em><\/p>\n<p><\/p>\n<p>N\u00e5r du bruker en Kubernetes-klynge, kan det bli n\u00f8dvendig \u00e5 oppdatere de aktive nodene p\u00e5 et senere tidspunkt. Dette kan inkludere oppdateringer av pakker, kjerneoppdateringer eller distribusjon av nye bildeservere. I Kubernetes-termer kalles dette <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/workloads\/pods\/disruptions\/#voluntary-and-involuntary-disruptions\">\u00abFrivillig avbrudd\u00bb<\/a><\/noindex>.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Dette innlegget er en del av en serie p\u00e5 4 innlegg:<\/p>\n<p><\/p>\n<ol>\n<li>Dette innlegget.<\/li>\n<li>Korrekt nedstenging av pods i en Kubernetes-klynge<\/li>\n<li>Utsatt avslutning av pod'en ved fjerning<\/li>\n<li>Hvordan unng\u00e5 nedetid i Kubernetes-klyngen ved hjelp av PodDisruptionBudgets<\/li>\n<\/ol>\n<p><\/p>\n<p><em>(merk. overs. oversettelser av de andre artiklene i serien kan forventes snart)<\/em><\/p>\n<p><\/p>\n<p>I denne artikkelen vil vi beskrive alle verkt\u00f8yene som Kubernetes tilbyr for \u00e5 oppn\u00e5 null nedetid for nodene som kj\u00f8rer i klyngen din.<\/p>\n<p><\/p>\n<h2 id=\"opredelenie-problemy\">Definere problemet<\/h2>\n<p><\/p>\n<p>I begynnelsen vil vi bruke en naiv tiln\u00e6rming for \u00e5 identifisere problemer og vurdere potensielle risikoer ved denne tiln\u00e6rmingen, og samle kunnskap for \u00e5 l\u00f8se hvert av problemene vi m\u00f8ter gjennom hele serien. Som et resultat vil vi f\u00e5 en konfigurasjon som bruker livssyklus-hooks, readiness probes og Pod disruption budgets for \u00e5 oppn\u00e5 v\u00e5r null nedetid. <\/p>\n<p><\/p>\n<p>For \u00e5 starte reisen v\u00e5r, la oss ta et konkret eksempel. Anta at vi har et Kubernetes-klynge med to noder, der en applikasjon kj\u00f8rer med to pod'er, som er bak <code>Service<\/code>:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Oppdatering av Kubernetes-klyngen uten nedetid\" src=\"\/wp-content\/uploads\/2020\/02\/f1eb999a0a088d7ed5b54c71e9b9ed1e.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><em>La oss starte med to pods med Nginx og en tjeneste som kj\u00f8rer p\u00e5 de to nodene i Kubernetes-klyngen v\u00e5r.<\/em><\/p>\n<p><\/p>\n<p>Vi \u00f8nsker \u00e5 oppdatere kjernen p\u00e5 de to arbeidsnodene i klyngen v\u00e5r. Hvordan skal vi gj\u00f8re dette? En enkel l\u00f8sning ville v\u00e6rt \u00e5 laste opp nye noder med oppdatert konfigurasjon, og s\u00e5 sl\u00e5 av de gamle nodene samtidig som de nye startes opp. Selv om dette vil fungere, vil det v\u00e6re flere problemer med en slik tiln\u00e6rming:<\/p>\n<p><\/p>\n<ul>\n<li>N\u00e5r du sl\u00e5r av de gamle nodene, vil de kj\u00f8rende pods ogs\u00e5 bli sl\u00e5tt av. Hva om pods m\u00e5 ryddes for \u00e5 kunne ta en korrekt frakobling? Virtuell maskinvare kan hende ikke venter p\u00e5 at ryddeprosessen skal fullf\u00f8res.<\/li>\n<li>Hva om du sl\u00e5r av alle nodene samtidig? Du vil oppleve betydelig nedetid mens pods flyttes til de nye nodene.<\/li>\n<\/ul>\n<p><\/p>\n<p>Vi trenger en korrekt m\u00e5te \u00e5 migrere pod-er fra gamle noder, samtidig som vi m\u00e5 v\u00e6re sikre p\u00e5 at ingen av arbeidsprosessene v\u00e5re kj\u00f8rer mens vi gj\u00f8r endringer for noden. Eller n\u00e5r vi gj\u00f8r en full erstatning av klyngen, som i eksemplet (dvs. vi erstatter VM-bilder), \u00f8nsker vi \u00e5 flytte aktive applikasjoner fra gamle noder til nye. I begge tilfeller \u00f8nsker vi \u00e5 forhindre planlegging av nye pod-er p\u00e5 gamle noder, og deretter fjerne alle aktive pod-er fra dem. For \u00e5 oppn\u00e5 disse m\u00e5lene kan vi bruke kommandoen <code>kubectl drain<\/code>.<\/p>\n<p><\/p>\n<h2 id=\"pereraspredelenie-vseh-podov-s-nody\">Omlokalisering av alle pod-er fra noden<\/h2>\n<p><\/p>\n<p>Drain-operasjonen tillater omskifting av alle pod-er fra noden. I l\u00f8pet av drain-prosessen blir noden merket som unschedulable (flagg <code>i kubectl. Spesifiser n\u00f8kkelen og verdien, og bruk deretter en taint som<\/code>). Dette forhindrer forekomsten av nye pod-er p\u00e5 den. Deretter begynner drain \u00e5 fjerne pod-er fra noden, og avslutter kj\u00f8rende containere som for tiden er aktive p\u00e5 noden ved \u00e5 sende signal <code>TERM<\/code> til containerne i pod-en.<\/p>\n<p><\/p>\n<p>Selv om <code>kubectl drain<\/code> det takler fjerningen av pod-er godt, er det to andre faktorer som kan f\u00f8re til at drain-operasjonen mislykkes:<\/p>\n<p><\/p>\n<ul>\n<li>Applikasjonen din m\u00e5 kunne avslutte korrekt ved signal <code>TERM<\/code> sending. N\u00e5r pod-er fjernes, sender Kubernetes et signal <code>TERM<\/code> til containerne og venter p\u00e5 at de skal stoppe i en angitt tidsperiode, hvoretter, hvis de ikke stopper, avsluttes de tvangsvis. Uansett, hvis containeren din ikke reagerer p\u00e5 signalet som den skal, kan du fortsatt sl\u00e5 av pod-ene usystematisk hvis de for \u00f8yeblikket er aktive (f.eks. en transaksjon i DB p\u00e5g\u00e5r).<\/li>\n<li>Du mister alle pod-er som inneholder applikasjonen din. Den kan v\u00e6re utilgjengelig p\u00e5 tidspunktet for oppstart av nye containere p\u00e5 de nye nodene, eller hvis pod-ene dine er rullet ut uten controllere, kan de kanskje ikke restarte i det hele tatt. <\/li>\n<\/ul>\n<p><\/p>\n<h2 id=\"izbegaem-prostoya\">Unng\u00e5 driftsstans<\/h2>\n<p><\/p>\n<p>For \u00e5 minimere nedetid fra frivillig forstyrrelse, som for eksempel fra drain-operasjonen for noden, gir Kubernetes f\u00f8lgende alternativer for feilbehandling:<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/workloads\/pods\/pod\/#termination-of-pods\">Graceful termination<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/containers\/container-lifecycle-hooks\/\">Livssyklus-hooks<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/workloads\/pods\/disruptions\/#how-disruption-budgets-work\">PodDisruptionBudgets<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<p>I de andre delene av syklusen vil vi bruke disse Kubernetes-funksjonene for \u00e5 dempe konsekvensene av pod-flytting. For \u00e5 gj\u00f8re hovedpoenget lettere \u00e5 f\u00f8lge, vil vi bruke v\u00e5rt ovenst\u00e5ende eksempel med f\u00f8lgende ressurskonfigurasjon:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">---\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n name: nginx-deployment\n labels:\n   app: nginx\nspec:\n replicas: 2\n selector:\n   matchLabels:\n     app: nginx\n template:\n   metadata:\n     labels:\n       app: nginx\n   spec:\n     containers:\n     - name: nginx\n       image: nginx:1.15\n       ports:\n       - containerPort: 80\n---\nkind: Service\napiVersion: v1\nmetadata:\n name: nginx-service\nspec:\n selector:\n   app: nginx\n ports:\n - protocol: TCP\n   targetPort: 80\n   port: 80<\/code><\/pre>\n<p><\/p>\n<p>Denne konfigurasjonen er et minimumseksempel <code>Deployment<\/code>, som styrer nginx-poder i klyngen. I tillegg beskriver konfigurasjonen ressursen <code>Service<\/code>, som kan brukes til \u00e5 f\u00e5 tilgang til nginx-poder i klyngen.<\/p>\n<p><\/p>\n<p>Gjennom hele syklusen vil vi iterativt utvide denne konfigurasjonen, slik at den til slutt inkluderer alle mulighetene Kubernetes gir for \u00e5 redusere nedetid.<\/p>\n<p><\/p>\n<p><em>For \u00e5 f\u00e5 en fullt implementert og testet versjon av oppdateringer for Kubernetes-klyngen for null nedetid p\u00e5 AWS og andre ressurser, bes\u00f8k <noindex><a rel=\"nofollow\" href=\"https:\/\/gruntwork.io\/\">Gruntwork.io<\/a><\/noindex>.<\/em><\/p>\n<p><\/p>\n<h2 id=\"takzhe-chitayte-drugie-stati-v-nashem-bloge\">Les ogs\u00e5 andre artikler i bloggen v\u00e5r:<\/h2>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/481932\/\">Null Nedetid Distribusjon og databaser<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/480072\/\">Kubernetes: hvorfor er det s\u00e5 viktig \u00e5 sette opp ressursstyringen i systemet?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/481992\/\">Tekton Pipeline \u2013 Kubernetes-natvie pipelines<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473578\/\">Bygging av dynamiske moduler for Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473014\/\">Introduksjon til Hashicorp Consul\u2019s Kubernetes Autorisasjon<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/468779\/\">Hva f\u00f8rte migrasjonen fra ClickHouse uten autentisering til ClickHouse med autentisering<\/a><\/noindex><\/li>\n<\/ul>\n<p>Kilde: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/489164\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u043e\u0446\u0435\u0441\u0441 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e Kubernetes-\u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0412 \u043a\u0430\u043a\u043e\u0439-\u0442\u043e \u043c\u043e\u043c\u0435\u043d\u0442 \u043f\u0440\u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0438 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0435\u0442 \u043f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u044c \u0432 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0438 \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0445 \u043d\u043e\u0434. \u041e\u043d\u043e \u043c\u043e\u0436\u0435\u0442 \u0432\u043a\u043b\u044e\u0447\u0430\u0442\u044c \u0432 \u0441\u0435\u0431\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043f\u0430\u043a\u0435\u0442\u043e\u0432, \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u044f\u0434\u0440\u0430 \u0438\u043b\u0438 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u0435 \u043d\u043e\u0432\u044b\u0445 \u043e\u0431\u0440\u0430\u0437\u043e\u0432 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d. \u0412 \u0442\u0435\u0440\u043c\u0438\u043d\u043e\u043b\u043e\u0433\u0438\u0438 Kubernetes \u044d\u0442\u043e \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f &quot;Voluntary Disruption&quot;. \u042d\u0442\u043e\u0442 \u043f\u043e\u0441\u0442 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0447\u0430\u0441\u0442\u044c\u044e \u0446\u0438\u043a\u043b\u0430 \u0438\u0437 4 \u043f\u043e\u0441\u0442\u043e\u0432: \u042d\u0442\u043e\u0442 \u043f\u043e\u0441\u0442. \u041a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u043e\u0435 \u0437\u0430\u0432\u0435\u0440\u0448\u0435\u043d\u0438\u0435 \u0440\u0430\u0431\u043e\u0442\u044b pod\u2019\u043e\u0432 \u0432 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":70832,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-70831","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u043e\u0446\u0435\u0441\u0441 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/obnovlenie-kubernetes-klastera-bez-prostoya\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"nn_NO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 Kubernetes-\u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0431\u0435\u0437 \u043f\u0440\u043e\u0441\u0442\u043e\u044f | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u043e\u0446\u0435\u0441\u0441 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/obnovlenie-kubernetes-klastera-bez-prostoya\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-02-21T11:42:15+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-03-03T13:14:45+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Oppdatering av Kubernetes-klyngen uten nedetid | ProHoster","description":"Oppdateringsprosessen for din.","canonical_url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/obnovlenie-kubernetes-klastera-bez-prostoya","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"nn_NO","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\u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 Kubernetes-\u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0431\u0435\u0437 \u043f\u0440\u043e\u0441\u0442\u043e\u044f | ProHoster","og:description":"\u041f\u0440\u043e\u0446\u0435\u0441\u0441 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e.","og:url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/obnovlenie-kubernetes-klastera-bez-prostoya","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-02-21T11:42:15+00:00","article:modified_time":"2020-03-03T13:14:45+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"70831","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 19:13:22","updated":"2022-09-29 13:06:50","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/70831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/comments?post=70831"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/70831\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media\/70832"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media?parent=70831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/categories?post=70831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/tags?post=70831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}