{"id":82913,"date":"2020-05-26T13:42:32","date_gmt":"2020-05-26T11:42:32","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate"},"modified":"2020-05-26T13:42:32","modified_gmt":"2020-05-26T11:42:32","slug":"luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","title":{"rendered":"Cele mai bune practici Kubernetes. Oprirea corect\u0103 Terminate","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>
\nCele mai bune practici Kubernetes. Verificarea livrabilit\u0103\u021bii Kubernetes cu teste de Readiness \u0219i Liveness<\/a><\/noindex>
\nCele mai bune practici Kubernetes. Configurarea cererilor \u0219i limitelor de resurse<\/a><\/noindex><\/p>\n

\"Cele
\n
\nUn aspect important \u00een func\u021bionarea sistemelor distribuite este gestionarea defectelor. Kubernetes ajut\u0103 \u00een acest sens, utiliz\u00e2nd controloare care monitorizeaz\u0103 starea sistemului dvs. \u0219i reporne\u0219te serviciile care nu mai func\u021bioneaz\u0103. Cu toate acestea, Kubernetes poate opri for\u021bat func\u021bionarea aplica\u021biilor dvs. pentru a asigura viabilitatea general\u0103 a sistemului. \u00cen aceast\u0103 serie, vom examina cum putem ajuta Kubernetes s\u0103 \u00ee\u0219i \u00eendeplineasc\u0103 sarcinile mai eficient \u0219i s\u0103 reduc\u0103 timpul de nefunc\u021bionare al aplica\u021biilor. <\/a><\/noindex><\/p>\n

\u00cenainte de a \u00eencepe utilizarea containerelor, majoritatea aplica\u021biilor func\u021bionau pe ma\u0219ini virtuale sau fizice. Dac\u0103 o aplica\u021bie se blocase sau d\u0103dea o eroare, era necesar mult timp pentru a opri sarcina \u00een execu\u021bie \u0219i pentru a relansa programul. \u00cen cel mai r\u0103u caz, cineva trebuia s\u0103 rezolve aceast\u0103 problem\u0103 manual noaptea, la ore necorespunz\u0103toare. Dac\u0103 o sarcin\u0103 important\u0103 era efectuat\u0103 de doar 1-2 ma\u0219ini de lucru, o astfel de defec\u021biune era complet inacceptabil\u0103.
\nDe aceea, \u00een loc de o repornire manual\u0103, s-a \u00eenceput utilizarea monitoriz\u0103rii la nivel de procese pentru a reporni automat aplica\u021bia \u00een caz de \u00eenchidere nea\u0219teptat\u0103. Dac\u0103 programul s-a defectat, procesul de monitorizare capteaz\u0103 codul de ie\u0219ire \u0219i reporne\u0219te serverul. Odat\u0103 cu apari\u021bia unor sisteme precum Kubernetes, acest tip de reac\u021bie la defectele sistemului a fost pur \u0219i simplu integrat \u00een infrastructur\u0103.<\/p>\n

Kubernetes folose\u0219te un ciclu de evenimente de tip \u201eobservare \u2013 \u00eenregistrare a diferen\u021belor \u2013 ac\u021biune\u201d pentru a se asigura c\u0103 resursele r\u0103m\u00e2n func\u021bionale pe parcursul tranzi\u021biei din containere c\u0103tre nodurile propriu-zise.<\/p>\n

\"Cele
\n
\nAceasta \u00eenseamn\u0103 c\u0103 nu mai trebuie s\u0103 rula\u021bi manual monitorizarea proceselor. Dac\u0103 un resource nu trece testul de s\u0103n\u0103tate, Kubernetes \u00eei va oferi pur \u0219i simplu un \u00eenlocuitor automat. \u00cen plus, Kubernetes face mult mai mult dec\u00e2t s\u0103 monitorizeze defec\u021biunile aplica\u021biilor dvs. El poate crea mai multe copii ale aplica\u021biei pentru a func\u021biona pe mai multe ma\u0219ini, poate actualiza aplica\u021bia sau poate rula simultan mai multe versiuni ale aplica\u021biei dvs.
\nExist\u0103 multe motive pentru care Kubernetes poate \u00eentrerupe func\u021bionarea unui container s\u0103n\u0103tos. De exemplu, dac\u0103 actualiza\u021bi desf\u0103\u0219urarea, Kubernetes va opri treptat podurile vechi, \u00een timp ce porne\u0219te noi. Dac\u0103 dezactiva\u021bi un nod, Kubernetes va opri toate podurile de pe acel nod. \u00cen cele din urm\u0103, dac\u0103 un nod r\u0103m\u00e2ne f\u0103r\u0103 resurse, Kubernetes va opri toate podurile pentru a elibera aceste resurse.<\/p>\n

De aceea, este foarte important ca aplica\u021bia dumneavoastr\u0103 s\u0103 se opreasc\u0103 cu un impact minim asupra utilizatorului final \u0219i cu un timp de recuperare c\u00e2t mai mic. Aceasta \u00eenseamn\u0103 c\u0103, \u00eenainte de a se opri, trebuie s\u0103 salveze toate datele necesare, s\u0103 \u00eenchid\u0103 toate conexiunile de re\u021bea, s\u0103 finalizeze toate sarcinile restante \u0219i s\u0103 reu\u0219easc\u0103 s\u0103 efectueze alte sarcini urgente.<\/p>\n

\u00cen practic\u0103, aceasta \u00eenseamn\u0103 c\u0103 aplica\u021bia dumneavoastr\u0103 trebuie s\u0103 fie capabil\u0103 s\u0103 gestioneze mesajul SIGTERM \u2013 semnalul de terminare a procesului, care este semnalul implicit pentru utilitarul kill \u00een sistemele de operare din familia Unix. La primirea acestui mesaj, aplica\u021bia ar trebui s\u0103 se opreasc\u0103.<\/p>\n

Dup\u0103 ce Kubernetes a decis s\u0103 finalizeze un pod, are loc o serie de evenimente. S\u0103 examin\u0103m fiecare pas pe care \u00eel face Kubernetes atunci c\u00e2nd opre\u0219te un container sau un pod.<\/p>\n

S\u0103 presupunem c\u0103 dorim s\u0103 finaliz\u0103m unul dintre poduri. \u00cen acest moment, acesta va \u00eenceta s\u0103 primeasc\u0103 trafic nou \u2013 containerele func\u021bionale din pod nu vor fi afectate, dar tot traficul nou va fi blocat.<\/p>\n

\"Cele
\n
\nS\u0103 analiz\u0103m hook-ul preStop \u2013 acesta este un comand\u0103 special\u0103 sau o solicitare HTTP trimis\u0103 containerelor din pod. Dac\u0103 aplica\u021bia dumneavoastr\u0103 nu se \u00eenchide corect la primirea SIGTERM, pute\u021bi folosi preStop pentru a finaliza corect func\u021bionarea. <\/p>\n

\"Cele
\n
\nCele mai multe programe se \u00eenchid corect la primirea semnalului SIGTERM, dar dac\u0103 utiliza\u021bi cod ter\u021b sau un sistem pe care nu-l pute\u021bi controla complet, hook-ul preStop ofer\u0103 o modalitate excelent\u0103 de a apela o oprire elegant\u0103 f\u0103r\u0103 a modifica aplica\u021bia.<\/p>\n

Dup\u0103 executarea acestui hook, Kubernetes va trimite containerelor din pod un semnal SIGTERM, care le va informa c\u0103 vor fi deconectate \u00een cur\u00e2nd. La primirea acestui semnal, codul dumneavoastr\u0103 va trece la procesul de deconectare. Acest proces poate include oprirea oric\u0103ror conexiuni de lung\u0103 durat\u0103, cum ar fi leg\u0103tura cu baza de date sau fluxurile WebSocket, salvarea st\u0103rii curente \u0219i altele.<\/p>\n

Chiar dac\u0103 utiliza\u021bi hook-ul preStop, este foarte important s\u0103 verifica\u021bi ce se \u00eent\u00e2mpl\u0103 cu aplica\u021bia dumneavoastr\u0103 atunci c\u00e2nd \u00eei trimite\u021bi semnalul SIGTERM, cum se comport\u0103, pentru a evita evenimentele sau modific\u0103rile \u00een func\u021bionarea sistemului cauzate de oprirea podului.<\/p>\n

\u00cen acest moment, \u00eenainte de a lua m\u0103suri ulterioare, Kubernetes va a\u0219tepta o perioad\u0103 specificat\u0103, denumit\u0103 terminationGracePeriodSecond, sau perioada pentru deconectare corect\u0103 la primirea semnalului SIGTERM.<\/p>\n

\"Cele
\n
\n\u00cen mod implicit, aceast\u0103 perioad\u0103 este de 30 de secunde. Este important de subliniat c\u0103 aceasta se desf\u0103\u0219oar\u0103 \u00een paralel cu hook-ul preStop \u0219i semnalul SIGTERM. Kubernetes nu va a\u0219tepta finalizarea hook-ului preStop \u0219i a SIGTERM \u2014 dac\u0103 aplica\u021bia dumneavoastr\u0103 se \u00eencheie \u00eenainte de expirarea perioadei de TerminationGracePeriod, Kubernetes va trece imediat la pasul urm\u0103tor. De aceea, verifica\u021bi ca valoarea acestei perioade \u00een secunde s\u0103 nu fie mai mic\u0103 dec\u00e2t timpul necesar pentru deconectarea corect\u0103 a podului, iar dac\u0103 dep\u0103\u0219e\u0219te 30s, cre\u0219te\u021bi perioada la dimensiunea necesar\u0103 \u00een YAML. \u00cen exemplul dat, acesta este de 60s.<\/p>\n

\u0218i \u00een cele din urm\u0103, ultimul pas \u2014 dac\u0103 containerele continu\u0103 s\u0103 func\u021bioneze dup\u0103 expirarea terminationGracePeriod, acestea vor trimite semnalul SIGKILL \u0219i vor fi eliminate for\u021bat. \u00cen acest moment, Kubernetes va cur\u0103\u021ba de asemenea toate celelalte obiecte ale podului.<\/p>\n

\"Cele
\n
\nKubernetes opre\u0219te podurile din mai multe motive, de aceea asigura\u021bi-v\u0103 c\u0103 aplica\u021bia dumneavoastr\u0103 se va \u00eenchide corect \u00een orice situa\u021bie, pentru a asigura func\u021bionarea stabil\u0103 a serviciului. <\/p>\n

Cele mai bune practici Kubernetes. Maparea serviciilor externe <\/a><\/noindex><\/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 \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 \u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0438 \u043b\u0438\u043c\u0438\u0442\u043e\u0432 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0412\u0430\u0436\u043d\u044b\u043c \u043c\u043e\u043c\u0435\u043d\u0442\u043e\u043c \u0432 \u0440\u0430\u0431\u043e\u0442\u0435 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0430 \u0441\u0431\u043e\u0435\u0432. Kubernetes \u043f\u043e\u043c\u043e\u0433\u0430\u0435\u0442 \u0432 \u044d\u0442\u043e\u043c, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0441\u043b\u0435\u0434\u044f\u0442 \u0437\u0430 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435\u043c \u0432\u0430\u0448\u0435\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":82914,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-82913","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. Deconectare corect\u0103 Terminate | ProHoster","description":"Cele mai bune practici Kubernetes.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","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. \u041a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u043e\u0435 \u043e\u0442\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 Terminate | 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-korrektnoe-otklyuchenie-terminate","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-26T11:42:32+00:00","article:modified_time":"2020-05-26T11:42:32+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"82913","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:28:37","updated":"2022-09-29 17:02:01","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\/82913","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=82913"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/82913\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/82914"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=82913"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=82913"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=82913"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}