{"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\/et\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","title":{"rendered":"Kubernetes'i parimad praktikad. Kubernetes'i eluj\u00f5u kontrollimine Readiness ja Liveness testide abil","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Parimad Kubernetes'i praktikad. V\u00e4ikeste konteinerite loomine<\/a><\/noindex>
\nKubernetes'i parimad tavad. Kubernetes'i korraldamine nimede ruumi abil<\/a><\/noindex><\/p>\n

\"Kubernetes'i
\n
\nJagatud s\u00fcsteemide haldamine v\u00f5ib olla keeruline, kuna neis on palju liikuvaid muutujaid, mis k\u00f5ik peavad korralikult t\u00f6\u00f6tama, et tagada s\u00fcsteemi funktsionaalsus. Kui \u00fcksk\u00f5ik milline elemendist eba\u00f5nnestub, peab s\u00fcsteem selle avastama, \u00fcletama ja parandama, ning seda peavad olema automaatsed toimingud. K\u00e4esolevas 'Kubernetes'i parimad praktikad' seerias uurime, kuidas seadistada Readiness ja Liveness teste Kubernetes'i kasti eluj\u00f5u kontrollimiseks.<\/p>\n

Tervisekontroll (Health Check) on lihtne viis v\u00f5imaldada s\u00fcsteemile teada, kas teie rakenduse eksemplar t\u00f6\u00f6tab v\u00f5i mitte. Kui teie rakenduse eksemplar ei t\u00f6\u00f6ta, ei tohiks teised teenused selle poole p\u00f6\u00f6rduda ega sellele p\u00e4ringut saata. Selle asemel peaks p\u00e4ring minema teise rakenduse eksemplarile, mis juba t\u00f6\u00f6tab v\u00f5i k\u00e4ivitatakse hiljem. Lisaks peab s\u00fcsteem teie rakendusele tagastama kadumise t\u00f5ttu t\u00f6\u00f6v\u00f5ime.<\/p>\n

Vaikimisi alustab Kubernetes liikluse suunamist pod'i, kui k\u00f5ik konteinerid pod'ides on k\u00e4ivitatud, ja taask\u00e4ivitab konteinerid, kui need kokku kukuvad. Alguses v\u00f5ib selline vaikimisi k\u00e4itumine olla piisav, kuid v\u00f5ite oma toote juurutamise usaldusv\u00e4\u00e4rsust suurendada, kasutades kohandatud t\u00f6\u00f6v\u00f5ime kontrollimisi.<\/a><\/noindex><\/p>\n

\"Kubernetes'i
\n
\n\u00d5nneks v\u00f5imaldab Kubernetes seda \u00fcsna lihtsalt teha, seega ei ole selliste kontrollide ignoreerimiseks mingit vabandust. Kubernetes pakub kahte t\u00fc\u00fcpi tervisekontrolle, kusjuures on oluline m\u00f5ista iga\u00fche rakenduse erinevusi.<\/p>\n

Valmidustest (Readiness Test) kasutatakse Kubernetes'ile teatamiseks, et teie rakendus on valmis liiklust teenindama. Enne kui teenus saadab liiklust pod'i, peab Kubernetes veenduma, et valmiduse kontrollimine on edukas. Kui valmidustest eba\u00f5nnestub, l\u00f5petab Kubernetes liikluse suunamise pod'i, kuni test on edukalt l\u00e4bitud. <\/p>\n

Eluj\u00f5utest (Liveness Test) teatab Kubernetes'ile, kas teie rakendus on elus v\u00f5i surnud. Esimesel juhul j\u00e4tab Kubernetes selle rahule, teisel juhul eemaldab see surnud pod'i ning asendab selle uuega. <\/p>\n

Kujutame ette stsenaariumi, kus teie rakenduse soojendamiseks ja k\u00e4ivitamiseks kulub 1 minut. Teie teenus ei hakka t\u00f6\u00f6le, kuni rakendus ei ole t\u00e4ielikult laaditud ja k\u00e4ivitatud, kuigi t\u00f6\u00f6protsess on juba alanud. Lisaks tekivad teil probleemid, kui soovite suurendada selle juurutamise kopeerimist, kuna need kopeerimised ei tohiks liiklust saada, kuni nad pole t\u00e4ielikult valmis. Kuid vaikimisi alustab Kubernetes liikluse suunamist kohe p\u00e4rast konteineris protsesside algust.<\/p>\n

K\u00e4ideldavuse testi Readiness kasutamisel ootab Kubernetes, kuni rakendus on t\u00e4ielikult k\u00e4ivitatud, ja alles seej\u00e4rel lubab teenusel suunata liiklust uuele koopia.<\/p>\n

\"Kubernetes'i
\n
\nKujutame ette teist stsenaariumi, kus rakendus hangub pikaks ajaks, l\u00f5petades p\u00e4ringute t\u00f6\u00f6tlemise. Kuna protsess j\u00e4tkab t\u00f6\u00f6tamist, peab Kubernetes vaikimisi olema k\u00f5ik korras ja j\u00e4tkab p\u00e4ringute suunamist mitte t\u00f6\u00f6tavale pod'ile. Kuid kasutades Liveness'i, avastab Kubernetes, et rakendus ei t\u00f6\u00f6tle enam p\u00e4ringuid, ja alustab vaikimisi mitte t\u00f6\u00f6tava pod'i taask\u00e4ivitamist.<\/p>\n

\"Kubernetes'i
\n
\nVaatame, kuidas testitakse valmisolekut ja eluj\u00f5ulisust. On kolm testimise meetodit - HTTP, Command ja TCP. Kontrollimiseks v\u00f5ite kasutada m\u00f5nd neist. K\u00f5ige levinum meetod kasutajatestiks on HTTP probe.<\/p>\n

Isegi kui teie rakendus ei ole HTTP-server, saate siiski luua rakenduse sees kergkaalu HTTP-serveri, et suhelda Liveness testiga. P\u00e4rast seda hakkab Kubernetes pod'i pinger\u00f5ngastama ning kui HTTP vastus j\u00e4\u00e4b vahemikku 200 v\u00f5i 300 ms, t\u00e4hendab see, et pod on 'terve'. Muul juhul m\u00e4rgitakse moodul 'haigeks'.<\/p>\n

\"Kubernetes'i
\n
\nK\u00fcsimus Command'i testides k\u00e4ivitab Kubernetes k\u00e4su teie konteineris. Kui k\u00e4sk naaseb nulliga exit code'iga, m\u00e4rgitakse konteiner tervena, vastasel juhul, kui saab exit status'i, mis on vahemikus 1 kuni 255, m\u00e4rgitakse konteiner 'haigeks'. See testimismeetod on kasulik, kui te ei saa v\u00f5i ei soovi k\u00e4ivitada HTTP-serverit, aga teil on v\u00f5imalik k\u00e4ivitada k\u00e4sk, mis kontrollib teie rakenduse ' tervislikkust.<\/p>\n

\"Kubernetes'i
\n
\nViimane kontrollimehhanism on TCP-test. Kubernetes p\u00fc\u00fcab luua TCP-\u00fchendust m\u00e4\u00e4ratud pordil. Kui see \u00f5nnestub, loetakse konteiner terveks, kui ei \u2013 siis mitteeluj\u00f5uliseks. See meetod v\u00f5ib osutuda kasulikuks, kui kasutate stsenaariumi, kus testimine HTTP-p\u00e4ringute v\u00f5i k\u00e4su t\u00e4itmisega pole v\u00e4ga efektiivne. N\u00e4iteks on peamisteks teenusteks TCP-testimiseks gRPC v\u00f5i FTP.<\/p>\n

\"Kubernetes'i
\n
\nTestid saab seadistada mitmel erineval viisil, koos erinevate parameetritega. Saate m\u00e4\u00e4rata, kui tihti neid tuleks k\u00e4ivitada, millised on eduka ja eba\u00f5nnestumise piirv\u00e4\u00e4rtused ning kui kaua oodata vastuseid. \u00dcksikasjalikku teavet leiate Readiness ja Liveness testide dokumentatsioonist. Siiski on \u00fcks v\u00e4ga oluline aspekt Liveness testi seadistamisel \u2013 esialgse viivituse v\u00e4\u00e4rtus initialDelaySeconds. Kuidas ma mainisin, eba\u00f5nnestumine selle testi puhul toob kaasa mooduli taask\u00e4ivitamise. Seet\u00f5ttu peate veenduma, et testimine ei alga enne, kui rakendus on t\u00f6\u00f6tamiseks valmis, vastasel juhul hakkab see pidevalt taask\u00e4ivituma. Soovitan kasutada rakenduse k\u00e4ivitamise P99 v\u00f5i keskmist k\u00e4ivitamise aega puhvri p\u00f5hjal. \u00c4rge unustage seda v\u00e4\u00e4rtust kohandada, kui teie rakenduse k\u00e4ivitamise aeg muutub kiiremaks v\u00f5i aeglasemaks.<\/p>\n

Enamik spetsialiste kinnitab, et Health Check on kohustuslik kontroll igas jaotatud s\u00fcsteemis, ja Kubernetes ei ole erand. Teenuste 'tervishoiu' kontrollimine tagab Kubernetes'e usaldusv\u00e4\u00e4rse ja t\u00f5rgeteta toimimise ning ei p\u00f5hjusta kasutajatele mingeid raskusi. <\/p>\n

J\u00e4tkub peagi...<\/p>\n

\r\n \"M\u00e4ngi\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Veidi reklaami \ud83d\ude42<\/h3>\n

\nAit\u00e4h, et olete meiega. Kas teile meeldivad meie artiklid? Kas soovite n\u00e4ha rohkem huvitavat sisu? Toetage meid, tellides teenuse v\u00f5i soovitades meid tuttavatele. Pilve VPS arendajatele alates $4.99<\/a><\/noindex>, ainulaadne entry-level serverite analoog, mille oleme teie jaoks v\u00e4lja m\u00f5elnud:<\/b> Kogu t\u00f5de VPS (KVM) E5-2697 v3 (6 Cores) 10GB DDR4 480GB SSD 1Gbps alates $19 v\u00f5i kuidas jagada serverit \u00f5igesti?<\/a><\/noindex> (saadaval RAID1 ja RAID10 variandid, kuni 24 tuuma ja kuni 40GB DDR4).<\/p>\n

Dell R730xd on Equinixi Tier IV andmekeskuses Amsterdamis kaks korda odavam?<\/b> Ainult meie juures 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB alates $199<\/a><\/noindex> Hollandis! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 alates $99!<\/b><\/b> Lugege sellest Kuidas luua ettev\u00f5tte tasemel infrastruktuuri, kasutades Dell R730xd E5-2650 v4 servereid, mille hind on 9000 eurot, taskukohase hinna eest?<\/a><\/noindex>
\n
Allikas: 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\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\udd47Kubernetes'e parimad praktikud. Kubernetes'e eluj\u00f5udluse kontrollamine Readiness ja Liveness testide abil | ProHoster","description":"Kubernetes'e parimad praktikud.","canonical_url":"https:\/\/prohoster.info\/et\/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":"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\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\/et\/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\/et\/wp-json\/wp\/v2\/posts\/82215","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=82215"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/82215\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/82216"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=82215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=82215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=82215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}