{"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\/ro\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-proverka-zhiznesposobnosti-kubernetes-s-pomoshhyu-testov-readiness-i-liveness","title":{"rendered":"Cele mai bune practici Kubernetes. Verificarea livrabilit\u0103\u021bii Kubernetes cu teste de Readiness \u0219i Liveness","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Cele mai bune practici Kubernetes. Crearea de containere mici<\/a><\/noindex>
\nCele mai bune practici Kubernetes. Organizarea Kubernetes cu spa\u021bii de nume<\/a><\/noindex><\/p>\n

\"Cele
\n
\nGestionarea sistemelor distribuite poate fi dificil\u0103 din cauza numeroaselor elemente mobile \u0219i modificabile, toate acestea fiind necesare pentru func\u021bionarea corect\u0103 a sistemului. Dac\u0103 unul dintre elemente se defecteaz\u0103, sistemul trebuie s\u0103-l identifice, s\u0103-l ocoleasc\u0103 \u0219i s\u0103-l repare, \u0219i totul trebuie s\u0103 se fac\u0103 automat. \u00cen aceast\u0103 serie de articole \u201eKubernetes Best Practices\u201d, vom \u00eenv\u0103\u021ba cum s\u0103 configur\u0103m testele de Readiness \u0219i Liveness pentru a verifica viabilitatea cluster-ului Kubernetes.<\/p>\n

Verificarea st\u0103rii (Health Check) este un mod simplu de a permite sistemului s\u0103 \u0219tie dac\u0103 instan\u021ba aplica\u021biei dvs. func\u021bioneaz\u0103 sau nu. Dac\u0103 instan\u021ba aplica\u021biei dvs. nu func\u021bioneaz\u0103, celelalte servicii nu ar trebui s\u0103 se adreseze acesteia sau s\u0103-i trimit\u0103 cereri. \u00cen schimb, cererea ar trebui s\u0103 fie direc\u021bionat\u0103 c\u0103tre o alt\u0103 instan\u021b\u0103 a aplica\u021biei care fie este deja activ\u0103, fie va fi activat\u0103 ulterior. \u00cen plus, sistemul ar trebui s\u0103 returneze aplica\u021biei dvs. func\u021bionalitatea pierdut\u0103.<\/p>\n

\u00cen mod implicit, Kubernetes va \u00eencepe s\u0103 direc\u021bioneze traficul c\u0103tre pod atunci c\u00e2nd toate containerele din interiorul acestuia sunt active, \u0219i va reporni containerele atunci c\u00e2nd acestea se opresc brusc. De\u0219i acest comportament implicit poate fi suficient pentru \u00eenceput, pute\u021bi \u00eembun\u0103t\u0103\u021bi fiabilitatea desf\u0103\u0219ur\u0103rii produsului dvs. folosind verific\u0103ri personalizate de s\u0103n\u0103tate.<\/a><\/noindex><\/p>\n

\"Cele
\n
\nDin fericire, Kubernetes permite realizarea acestora destul de simplu, astfel c\u0103 ignorarea unor astfel de verific\u0103ri nu este justificat\u0103. Kubernetes ofer\u0103 dou\u0103 tipuri de teste de Health Check, \u0219i este important s\u0103 \u00een\u021belege\u021bi diferen\u021bele dintre utiliz\u0103rile fiec\u0103ruia.<\/p>\n

Testul de readiness este destinat s\u0103 informeze Kubernetes despre disponibilitatea aplica\u021biei dvs. de a gestiona traficul. \u00cenainte de a permite serviciului s\u0103 trimit\u0103 trafic c\u0103tre pod, Kubernetes trebuie s\u0103 se asigure c\u0103 testul de readiness a fost finalizat cu succes. Dac\u0103 testul de readiness e\u0219ueaz\u0103, Kubernetes va \u00eenceta s\u0103 trimit\u0103 trafic c\u0103tre pod p\u00e2n\u0103 c\u00e2nd testul nu este realizat cu succes. <\/p>\n

Testul de liveness informeaz\u0103 Kubernetes dac\u0103 aplica\u021bia dvs. este vie sau mort\u0103. \u00cen cazul \u00een care este vie, Kubernetes o va l\u0103sa \u00een pace, iar \u00een cazul \u00een care este moart\u0103, va elimina podul mort \u0219i \u00eel va \u00eenlocui cu unul nou. <\/p>\n

S\u0103 ne imagin\u0103m un scenariu \u00een care aplica\u021bia dumneavoastr\u0103 necesit\u0103 1 minut pentru a fi \"\u00eenc\u0103lzit\u0103\" \u0219i lansat\u0103. Serviciul dumneavoastr\u0103 nu va \u00eencepe s\u0103 func\u021bioneze p\u00e2n\u0103 c\u00e2nd aplica\u021bia nu se va \u00eenc\u0103rca \u0219i lansa complet, chiar dac\u0103 fluxul de lucru a \u00eenceput deja. De asemenea, ve\u021bi avea probleme dac\u0103 dori\u021bi s\u0103 scala\u021bi acest deployment la mai multe copii, deoarece aceste copii nu ar trebui s\u0103 primeasc\u0103 trafic p\u00e2n\u0103 nu sunt complet gata. Totu\u0219i, \u00een mod implicit, Kubernetes va \u00eencepe s\u0103 redirec\u021bioneze traficul imediat dup\u0103 ini\u021bierea proceselor din interiorul containerului.<\/p>\n

Folosind testul de disponibilitate (Readiness), Kubernetes va a\u0219tepta p\u00e2n\u0103 c\u00e2nd aplica\u021bia va fi complet lansat\u0103 \u0219i abia dup\u0103 aceea va permite serviciului s\u0103 redirec\u021bioneze traficul c\u0103tre noua copie.<\/p>\n

\"Cele
\n
\nS\u0103 ne imagin\u0103m un alt scenariu \u00een care aplica\u021bia se blocheaz\u0103 pentru o perioad\u0103 \u00eendelungat\u0103, f\u0103r\u0103 a mai r\u0103spunde la cereri. Deoarece procesul continu\u0103 s\u0103 ruleze, \u00een mod implicit Kubernetes va considera c\u0103 totul este \u00een regul\u0103 \u0219i va continua s\u0103 redirec\u021bioneze cererile c\u0103tre pod-ul nefunc\u021bional. \u00cens\u0103, folosind Liveness, Kubernetes va detecta c\u0103 aplica\u021bia nu mai r\u0103spunde la cereri \u0219i va reporni, \u00een mod implicit, pod-ul nefunc\u021bional.<\/p>\n

\"Cele
\n
\nS\u0103 analiz\u0103m instrumentele folosite pentru a testa disponibilitatea \u0219i viabilitatea. Exist\u0103 trei moduri de testare - HTTP, Command \u0219i TCP. Pute\u021bi folosi oricare dintre acestea pentru verificare. Cel mai utilizat mod de testare de utilizator este HTTP probe.<\/p>\n

Chiar dac\u0103 aplica\u021bia dumneavoastr\u0103 nu este un server HTTP, pute\u021bi crea totu\u0219i un server HTTP u\u0219or \u00een interiorul aplica\u021biei dumneavoastr\u0103 pentru a interac\u021biona cu testul Liveness. Dup\u0103 aceea, Kubernetes va \u00eencepe s\u0103 ping-pongueze pod-ul, iar dac\u0103 r\u0103spunsul HTTP se \u00eencadreaz\u0103 \u00eentre 200 sau 300 ms, aceasta va \u00eensemna c\u0103 pod-ul este \u201es\u0103n\u0103tos\u201d. \u00cen caz contrar, modul va fi marcat ca \u201enes\u0103n\u0103tos\u201d.<\/p>\n

\"Cele
\n
\nPentru testele folosind Command, Kubernetes va executa o comand\u0103 \u00een interiorul containerului dumneavoastr\u0103. Dac\u0103 comanda se \u00eentoarce cu un cod de ie\u0219ire zero, containerul va fi marcat ca s\u0103n\u0103tos; \u00een caz contrar, dac\u0103 se ob\u021bine un cod de ie\u0219ire \u00eentre 1 \u0219i 255, containerul va fi marcat ca \u201ebolnav\u201d. Aceast\u0103 metod\u0103 de testare este util\u0103 dac\u0103 nu pute\u021bi sau nu dori\u021bi s\u0103 rula\u021bi un server HTTP, dar sunte\u021bi capabili s\u0103 rula\u021bi o comand\u0103 care s\u0103 verifice \u201es\u0103n\u0103tatea\u201d aplica\u021biei dumneavoastr\u0103.<\/p>\n

\"Cele
\n
\nUltimul mecanism de verificare este testul TCP. Kubernetes va \u00eencerca s\u0103 stabileasc\u0103 o conexiune TCP pe portul specificat. Dac\u0103 reu\u0219e\u0219te, containerul este considerat s\u0103n\u0103tos, altfel este considerat nes\u0103n\u0103tos. Aceast\u0103 metod\u0103 poate fi util\u0103 dac\u0103 utiliza\u021bi un scenariu \u00een care testarea cu un request HTTP sau executarea unei comenzi nu func\u021bioneaz\u0103 foarte bine. De exemplu, principalele servicii pentru testarea prin TCP vor fi gRPC sau FTP.<\/p>\n

\"Cele
\n
\nTestele pot fi configurate \u00een mai multe moduri cu diferite parametrii. Pute\u021bi specifica c\u00e2t de des ar trebui s\u0103 fie efectuate, care sunt pragurile de succes \u0219i e\u0219ec, c\u00e2t timp s\u0103 a\u0219tepte r\u0103spunsuri. Informa\u021bii mai detaliate sunt prezentate \u00een documenta\u021bia pentru testele Readiness \u0219i Liveness. Totu\u0219i, exist\u0103 un aspect foarte important \u00een configurarea testului Liveness \u2013 \u00eent\u00e2rzirea ini\u021bial\u0103 de testare initialDelaySeconds. A\u0219a cum men\u021bionam, o executare e\u0219uat\u0103 a acestui test va conduce la repornirea modulului. Prin urmare, trebuie s\u0103 v\u0103 asigura\u021bi c\u0103 testarea nu \u00eencepe p\u00e2n\u0103 c\u00e2nd aplica\u021bia nu este preg\u0103tit\u0103 s\u0103 func\u021bioneze, altfel va \u00eencepe s\u0103 reporneasc\u0103 \u00een mod ciclic. Recomand s\u0103 utiliza\u021bi timpul de start P99 sau timpul mediu de lansare a aplica\u021biei din buffer. Nu uita\u021bi s\u0103 ajusta\u021bi aceast\u0103 valoare pe m\u0103sur\u0103 ce timpul de lansare al aplica\u021biei devine tot mai rapid sau mai lent.<\/p>\n

Cei mai mul\u021bi speciali\u0219ti confirm\u0103 c\u0103 Health Check-urile sunt verifi care obligatorii pentru orice sistem distribuit, iar Kubernetes nu face excep\u021bie. Utilizarea verific\u0103rii \"s\u0103n\u0103t\u0103\u021bii\" serviciilor asigur\u0103 o func\u021bionare fiabil\u0103 \u0219i f\u0103r\u0103 probleme a Kubernetes \u0219i nu reprezint\u0103 o problem\u0103 pentru utilizatori. <\/p>\n

Continuarea va veni foarte cur\u00e2nd\u2026<\/p>\n

\r\n \"Reda\u021bi\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Pu\u021bin publicitate \ud83d\ude42<\/h3>\n

\nMul\u021bumim c\u0103 r\u0103m\u00e2ne\u021bi cu noi. V\u0103 plac articolele noastre? Dori\u021bi s\u0103 vede\u021bi mai multe materiale interesante? Sus\u021bine\u021bi-ne, efectu\u00e2nd o comand\u0103 sau recomand\u00e2ndu-ne prietenilor, VPS cloud pentru dezvoltatori de la 4,99 $<\/a><\/noindex>, un echivalent unic pentru serverele entry-level, care a fost creat de noi pentru voi:<\/b> Toat\u0103 adev\u0103rul despre VPS (KVM) E5-2697 v3 (6 nuclee) 10GB DDR4 480GB SSD 1Gbps de la 19 $ sau cum s\u0103 \u00eemp\u0103r\u021bi\u021bi corect un server?<\/a><\/noindex> (sunt disponibile op\u021biuni cu RAID1 \u0219i RAID10, p\u00e2n\u0103 la 24 nuclee \u0219i p\u00e2n\u0103 la 40GB DDR4).<\/p>\n

Dell R730xd la jum\u0103tate de pre\u021b \u00een centrul de date Equinix Tier IV din Amsterdam?<\/b> Numai la noi 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB de la 199 $<\/a><\/noindex> \u00een Olanda! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 de la 99 $!<\/b><\/b> Citi\u021bi despre Cum s\u0103 construi\u021bi o infrastructur\u0103 de clas\u0103 enterprise folosind servere Dell R730xd E5-2650 v4 la pre\u021buri foarte mici de 9000 \u20ac?<\/a><\/noindex>
\n
Sursa: 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\udd47Cele mai bune practici Kubernetes. Verificarea viabilit\u0103\u021bii Kubernetes prin teste Readiness \u0219i Liveness | ProHoster","description":"Cele mai bune practici Kubernetes.","canonical_url":"https:\/\/prohoster.info\/ro\/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":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/82215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=82215"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/82215\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/82216"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=82215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=82215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=82215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}