{"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\/hr\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","title":{"rendered":"Najbolje prakse Kubernetes-a. Provjera \u017eivotne sposobnosti Kubernetes-a pomo\u0107u Readiness i Liveness testova.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Najbolje prakse Kubernetes-a. Kreiranje malih kontejnera.<\/a><\/noindex>
\nNajbolje prakse Kubernetes-a. Organiziranje Kubernetes-a s prostorima imena.<\/a><\/noindex><\/p>\n

\"Najbolje
\n
\nUpravljanje distribuiranim sustavima mo\u017ee biti izazovno zbog brojnih promjenjivih elemenata, koji moraju raditi ispravno kako bi sustav bio funkcionalan. Ako jedan od elemenata prestane raditi, sustav ga mora otkriti, zaobi\u0107i i ispraviti, a sve to treba raditi automatski. U ovoj seriji \u00abKubernetes Best Practices\u00bb saznat \u0107emo kako postaviti Readiness i Liveness testove za provjeru odr\u017eivosti Kubernetes klastera.<\/p>\n

Health Check je jednostavan na\u010din da sustav sazna radi li instanca va\u0161e aplikacije ili ne. Ako instanca va\u0161e aplikacije ne radi, druge usluge ne bi trebale slati zahtjeve ili se povezivati s njom. Umjesto toga, zahtjev bi trebao biti upu\u0107en drugoj instanci aplikacije koja je ve\u0107 pokrenuta ili \u0107e biti pokrenuta kasnije. Osim toga, sustav bi trebao vratiti va\u0161u aplikaciju u funkcionalno stanje.<\/p>\n

Prema zadanim postavkama, Kubernetes \u0107e po\u010deti slati promet u pod kada su svi kontejneri unutar poda pokrenuti, a ponovno \u0107e pokrenuti kontejnere kada se ru\u0161e. Na po\u010detku, takvo pona\u0161anje sustava mo\u017ee biti sasvim zadovoljavaju\u0107e, no mo\u017eete pobolj\u0161ati pouzdanost implementacije svog proizvoda koriste\u0107i prilago\u0111ene provjere zdravlja.<\/a><\/noindex><\/p>\n

\"Najbolje
\n
\nSre\u0107om, Kubernetes omogu\u0107uje da to postignete prili\u010dno jednostavno, pa nema opravdanja za ignoriranje takvih provjera. Kubernetes nudi dvije vrste Health Check testova, a va\u017eno je razumjeti razlike u primjeni svakog od njih.<\/p>\n

Readiness test je osmi\u0161ljen kako bi obavijestio Kubernetes da je va\u0161a aplikacija spremna za obradu prometa. Prije nego \u0161to dopusti servisu da \u0161alje promet u pod, Kubernetes mora osigurati uspje\u0161nost provjere spremnosti. Ako test Readiness ne pro\u0111e, Kubernetes \u0107e prestati slati promet u pod sve dok testiranje ne bude uspje\u0161no. <\/p>\n

Liveness test obavje\u0161tava Kubernetes je li va\u0161a aplikacija \u017eiva ili mrtva. U prvom slu\u010daju, Kubernetes \u0107e je ignorirati, dok \u0107e u drugom slu\u010daju ukloniti mrtvi pod i zamijeniti ga novim. <\/p>\n

Zamislite scenarij u kojem va\u0161em aplikaciji treba 1 minuta da se \"zagrije\" i pokrene. Va\u0161a usluga ne\u0107e po\u010deti funkcionirati sve dok aplikacija potpuno ne zavr\u0161i u\u010ditavanje i ne pokrene se, iako je radni proces ve\u0107 zapo\u010deo. Tako\u0111er \u0107ete imati problema ako \u017eelite pove\u0107ati broj kopija ove implementacije jer te kopije ne bi trebale primati promet dok nisu potpuno spremne. No, po defaultu, Kubernetes \u0107e po\u010deti slati promet odmah nakon pokretanja procesa unutar kontejnera.<\/p>\n

Kada koristite test spremnosti Readiness, Kubernetes \u0107e \u010dekati da se aplikacija potpuno pokrene i tek tada \u0107e dopustiti usluzi da \u0161alje promet na novu kopiju.<\/p>\n

\"Najbolje
\n
\nZamislite drugi scenarij u kojem aplikacija du\u017ee vrijeme ne reagira na zahtjeve. Budu\u0107i da proces nastavlja djelovati, po defaultu \u0107e Kubernetes smatrati da je sve u redu i nastaviti slati zahtjeve na neispravan pod. Me\u0111utim, kori\u0161tenjem Liveness, Kubernetes \u0107e otkriti da aplikacija vi\u0161e ne obra\u0111uje zahtjeve i po defaultu \u0107e ponovno pokrenuti neispravan pod.<\/p>\n

\"Najbolje
\n
\nPogledajmo kako se testira spremnost i vitalnost. Postoje tri na\u010dina testiranja \u2014 HTTP, Command i TCP. Mo\u017eete koristiti bilo koji od njih za provjeru. Naj\u010de\u0161\u0107i na\u010din korisni\u010dkog testiranja je HTTP probe.<\/p>\n

\u010cak i ako va\u0161a aplikacija nije HTTP poslu\u017eitelj, i dalje mo\u017eete stvoriti lagani HTTP poslu\u017eitelj unutar va\u0161e aplikacije za interakciju s testom Liveness. Nakon toga, Kubernetes \u0107e po\u010deti pingati pod, a ako HTTP odgovor bude unutar raspona od 200 ili 300 ms, to \u0107e zna\u010diti da je pod \"zdrav\". U suprotnom, modul \u0107e biti ozna\u010den kao \"bolestan\".<\/p>\n

\"Najbolje
\n
\nZa testove koriste\u0107i Command, Kubernetes izvr\u0161ava komandu unutar va\u0161eg kontejnera. Ako se komanda vrati s nulom kao exit kod, kontejner \u0107e biti ozna\u010den kao zdrav, u suprotnom, ako dobije status izlaza od 1 do 255, kontejner \u0107e biti ozna\u010den kao \"bolestan\". Ova metoda testiranja je korisna ako ne mo\u017eete ili ne \u017eelite pokretati HTTP poslu\u017eitelj, ali mo\u017eete pokrenuti komandu koja \u0107e provjeriti \"zdravlje\" va\u0161e aplikacije.<\/p>\n

\"Najbolje
\n
\nPosljednji mehanizam provjere je TCP test. Kubernetes \u0107e poku\u0161ati uspostaviti TCP vezu na navedenoj portu. Ako to uspije, kontejner se smatra zdravim, u suprotnom neupotrebljivim. Ova metoda mo\u017ee biti korisna ako koristite scenarij u kojem provjera putem HTTP zahtjeva ili izvr\u0161avanje komande ne radi dobro. Na primjer, glavni servisi za provjeru putem TCP-a bit \u0107e gRPC ili FTP.<\/p>\n

\"Najbolje
\n
\nTestove mo\u017eete postaviti na nekoliko na\u010dina s razli\u010ditim parametrima. Mo\u017eete odrediti koliko \u010desto se trebaju izvoditi, koji su pragovi uspjeha i neuspjeha, koliko dugo \u010dekati na odgovore. Detaljnije informacije navedene su u dokumentaciji za Readiness i Liveness testove. Me\u0111utim, postoji jedan vrlo va\u017ean aspekt u postavljanju Liveness testa \u2013 po\u010detna postavka ka\u0161njenja testa initialDelaySeconds. Kao \u0161to sam spomenuo, neuspje\u0161no izvr\u0161enje ovog testa rezultirat \u0107e ponovnim pokretanjem modula. Stoga trebate osigurati da testiranje ne zapo\u010dne dok aplikacija ne bude spremna za rad, ina\u010de \u0107e se po\u010deti cikli\u010dki ponovo pokretati. Preporu\u010dujem kori\u0161tenje P99 vremena pokretanja ili prosje\u010dnog vremena pokretanja aplikacije iz bafera. Ne zaboravite prilagoditi tu vrijednost dok vrijeme pokretanja va\u0161e aplikacije postaje sve br\u017ee ili sporije.<\/p>\n

Ve\u0107ina stru\u010dnjaka \u0107e potvrditi da su Health Check obavezna provjera za svaki distribuirani sustav, a Kubernetes nije iznimka. Kori\u0161tenje provjere 'zdravlja' servisa osigurava pouzdan i besprijekoran rad Kubernetesa i ne predstavlja nikakvu pote\u0161ko\u0107u za korisnike. <\/p>\n

Nastavak slijedi vrlo brzo...<\/p>\n

\r\n \"Pogledajte\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Malo reklame \ud83d\ude42<\/h3>\n

\nHvala \u0161to ostajete s nama. Svi\u0111a li vam se na\u0161e \u010dlanke? \u017delite li vidjeti vi\u0161e zanimljivih materijala? Podr\u017eite nas narud\u017ebom ili preporu\u010dite prijateljima, obla\u010dni VPS za developere od 4,99 $<\/a><\/noindex>, jedinstveni analog entry-level servera koji smo razvili za vas:<\/b> Sva istina o VPS-u (KVM) E5-2697 v3 (6 jezgri) 10GB DDR4 480GB SSD 1Gbps od 19 $ ili kako pravilno dijeliti server?<\/a><\/noindex> (dostupne opcije s RAID1 i RAID10, do 24 jezgre i do 40GB DDR4).<\/p>\n

Dell R730xd je 2 puta jeftiniji u data centaru Equinix Tier IV u Amsterdamu?<\/b> Samo kod nas 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 $<\/a><\/noindex> u Nizozemskoj! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 $!<\/b><\/b> Pro\u010ditajte o tome Kako izgraditi infrastrukturu korporacijske klase koriste\u0107i Dell R730xd E5-2650 v4 servere po cijeni od 9000 eura za sitni\u0161?<\/a><\/noindex>
\n
Izvor: 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\udd47Najbolje prakse Kubernetes. Provjera ispravnosti Kubernetes-a putem Readiness i Liveness testova | ProHoster","description":"Najbolje prakse Kubernetes.","canonical_url":"https:\/\/prohoster.info\/hr\/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":"hr_HR","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\/hr\/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\/hr\/wp-json\/wp\/v2\/posts\/82215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=82215"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/82215\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/82216"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=82215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=82215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=82215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}