{"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\/et\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","title":{"rendered":"Kubernetes parimad praktikad. \u00d5ige katkestamine Terminate","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>
\nKubernetes'i parimad praktikad. Kubernetes'i eluj\u00f5u kontrollimine Readiness ja Liveness testide abil<\/a><\/noindex>
\nParimad praktikad Kuberneteses. Ressursside p\u00e4ringute ja piirangute seadistamine<\/a><\/noindex><\/p>\n

\"Kubernetes
\n
\nOluline aspekt jaotatud s\u00fcsteemide t\u00f6\u00f6s on t\u00f5rgete k\u00e4sitlemine. Kubernetes aitab selle kaudu, kasutades kontrollereid, mis j\u00e4lgivad teie s\u00fcsteemi olekut ja taask\u00e4ivitavad mittefunksioneerivad teenused. Siiski v\u00f5ib Kubernetes sundida teie rakenduste t\u00f6\u00f6 l\u00f5petamist, et tagada kogu s\u00fcsteemi eluj\u00f5ud. Selles seerias uurime, kuidas aidata Kubernetesel oma t\u00f6\u00f6d t\u00f5husamalt teha ja rakenduste seisakuaega v\u00e4hendada. <\/a><\/noindex><\/p>\n

Enne konteinerite kasutuselev\u00f5ttu t\u00f6\u00f6tasid enamik rakendusi virtuaalsetel v\u00f5i f\u00fc\u00fcsilistel masinatel. Kui rakendus andis t\u00f5rke v\u00f5i hangus, kulus palju aega jooksva \u00fclesande peatamiseks ja programmi uuesti laadimiseks. Halvimal juhul pidi keegi selle probleemi k\u00e4sitlema k\u00e4sitsi \u00f6\u00f6sel, k\u00f5ige ebamugavamal ajal. Kui olulist \u00fclesannet t\u00e4itsid vaid 1-2 t\u00f6\u00f6machiini, oli selline t\u00f5rge t\u00e4iesti vastuv\u00f5etamatu.
\nSeet\u00f5ttu hakati k\u00e4sitsi taask\u00e4ivitamise asemel kasutama protsessitasandi j\u00e4lgimist, et automaatselt taask\u00e4ivitada rakendust selle eba\u00f5nnestumise korral. Kui programm eba\u00f5nnestus, haarab j\u00e4lgimisprotsess v\u00e4ljumiskoodi ja taask\u00e4ivitab serveri. Selliste s\u00fcsteemide, nagu Kubernetes, saabumisega integreeriti see t\u00f5rke reageerimise viis lihtsalt infrastruktuuri.<\/p>\n

Kubernetes kasutab s\u00fcndmuste silmuste \u201ej\u00e4lgimine \u2013 erinevuste fikseerimine \u2013 tegevuse tegemine\u201d, et veenduda, et ressursid s\u00e4ilitavad t\u00f6\u00f6korras oleku konteineritest s\u00f5lmedeni.<\/p>\n

\"Kubernetes
\n
\nSee t\u00e4hendab, et te ei pea enam k\u00e4sitsi protsesside j\u00e4lgimist k\u00e4ivitama. Kui resurss ei l\u00e4binud tervisekontrolli Health Check, annab Kubernetes sellele lihtsalt automaatselt asenduse. Samuti teeb Kubernetes palju rohkem, kui lihtsalt j\u00e4lgib teie rakenduste t\u00f5rkeid. Ta v\u00f5ib luua rakenduse rohkem koopiaid, et need t\u00f6\u00f6taksid erinevates masinates, uuendada rakendust v\u00f5i samaaegselt k\u00e4ivitada mitu versiooni teie rakendusest.
\nSeet\u00f5ttu on palju p\u00f5hjuseid, miks Kubernetes v\u00f5ib katkestada t\u00e4iesti terve konteineri t\u00f6\u00f6. N\u00e4iteks kui uuendate oma juurutust, peatab Kubernetes aeglaselt vanad podid, samal ajal kui uued k\u00e4ivituvad. Kui l\u00fclitate v\u00e4lja s\u00f5lm, l\u00f5petab Kubernetes selle s\u00f5lme k\u00f5ikide podide t\u00f6\u00f6. L\u00f5puks, kui s\u00f5lmel saavad ressursid otsa, peatab Kubernetes k\u00f5ik podid, et neid ressursse vabastada.<\/p>\n

Seet\u00f5ttu on v\u00e4ga oluline, et teie rakendus l\u00f5petaks t\u00f6\u00f6 minimaalsete m\u00f5jude ja minimaalse taastumisaega l\u00f5ppkasutajale. See t\u00e4hendab, et enne v\u00e4ljal\u00fclitamist peab see salvestama k\u00f5ik vajalikud andmed, sulgema k\u00f5ik v\u00f5rgu\u00fchendused, l\u00f5petama \u00fclej\u00e4\u00e4nud t\u00f6\u00f6d ja j\u00f5udma teha muid h\u00e4davajalikke \u00fclesandeid.<\/p>\n

Praktikas t\u00e4hendab see, et teie rakendus peab suutma t\u00f6\u00f6delda SIGTERM s\u00f5numit \u2013 protsesside l\u00f5petamise signaali, mis on vaikimisi signaal Unix-p\u00f5histes operatsioonis\u00fcsteemides kill utiliidile. Saades seda s\u00f5numit, peab rakendus enda t\u00f6\u00f6 l\u00f5petama.<\/p>\n

P\u00e4rast seda, kui Kubernetes otsustab podi l\u00f5petada, toimub mitmeid s\u00fcndmusi. Vaatame \u00fcle iga sammu, mida Kubernetes teeb konteineri v\u00f5i podi sulgemisel.<\/p>\n

Oletame, et soovime l\u00f5petada \u00fche podi. Sel hetkel l\u00f5petab ta uue liikluse vastuv\u00f5tmise \u2013 podis t\u00f6\u00f6tavad konteinerid ei ole m\u00f5jutatud, kuid kogu uus liiklus blokeeritakse.<\/p>\n

\"Kubernetes
\n
\nVaatame preStop konksu \u2013 see on spetsiaalne k\u00e4sk v\u00f5i HTTP-p\u00e4ring, mis saadetakse podi konteineritele. Kui teie rakendus ei sulgu \u00f5igesti SIGTERM saamisel, saate kasutada preStop konksu, et l\u00f5petada t\u00f6\u00f6 \u00f5igesti. <\/p>\n

\"Kubernetes
\n
\nEnamik programme l\u00f5petab oma t\u00f6\u00f6 \u00f5igesti SIGTERM signaali saamisel, kuid kui kasutate kolmanda osapoole koodi v\u00f5i mingit s\u00fcsteemi, mida ei saa t\u00e4ielikult kontrollida, on preStop konks suurep\u00e4rane viis elegantse sulgemise kutsumiseks ilma rakendust muutmata.<\/p>\n

P\u00e4rast selle hooki t\u00e4itmist saadab Kubernetes konteineritele podi sees SIGTERM signaali, mis annab neile teada, et nad peavad varsti sulgema. Kui nad selle signaali saavad, l\u00e4heb teie kood sulgemisprotsessi. See protsess v\u00f5ib h\u00f5lmata pikaajaliste \u00fchenduste, n\u00e4iteks andmebaasi\u00fchenduste v\u00f5i WebSocketi voogude sulgemist, praeguse oleku salvestamist jne.<\/p>\n

Isegi kui kasutate preStop hooki, on \u00e4\u00e4rmiselt oluline kontrollida, mis t\u00e4pselt teie rakendusega juhtub, kui saadate sellele SIGTERM signaali, kuidas see k\u00e4itub, et s\u00fcndmused v\u00f5i muud s\u00fcsteemi t\u00f6\u00f6 muutused, mis on p\u00f5hjustatud podi sulgemisest, teid \u00fcllatuseks ei tooks.<\/p>\n

Sel hetkel, enne edasiste meetmete v\u00f5tmist, ootab Kubernetes kindlaksm\u00e4\u00e4ratud aja, mida nimetatakse terminationGracePeriodSeconds, v\u00f5i aeg, mis on ette n\u00e4htud korrektseks sulgemiseks p\u00e4rast SIGTERM signaali saamist.<\/p>\n

\"Kubernetes
\n
\nVaikimisi on see periood 30 sekundit. On oluline m\u00e4rkida, et see kestab samal ajal koos preStop hooki ja SIGTERM signaaliga. Kubernetes ei oota, kuni preStop hook ja SIGTERM on l\u00f5petatud \u2014 kui teie rakendus l\u00f5petab t\u00f6\u00f6 enne terminationGracePeriodi l\u00f5ppu, l\u00e4heb Kubernetes kohe j\u00e4rgmise sammu juurde. Seega veenduge, et selle perioodi v\u00e4\u00e4rtus sekundites poleks v\u00e4iksem kui aeg, mis on vajalik podi korrektseks sulgemiseks, ja kui see \u00fcletab 30s, suurendage perioodi vajalikule v\u00e4\u00e4rtusele YAML-is. Antud n\u00e4ites on see 60s.<\/p>\n

Ja l\u00f5puks, viimane samm \u2014 kui konteinerid j\u00e4tkavad t\u00f6\u00f6 tegemist p\u00e4rast terminationGracePeriodi l\u00f5ppu, saadavad nad SIGKILL signaali ja eemaldatakse sundkorras. Sel hetkel puhastab Kubernetes ka k\u00f5ik muud podi objektid.<\/p>\n

\"Kubernetes
\n
\nKubernetes l\u00f5petab podide t\u00f6\u00f6 mitmel p\u00f5hjusel, seet\u00f5ttu veenduge, et teie rakendus suletakse igal juhul \u00f5igesti, et tagada teenuse stabiilne toimimine. <\/p>\n

Parimad Kubernetes`e praktikad. V\u00e4liste teenuste kaardistamine <\/a><\/noindex><\/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 \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\udd47Parimad praktikud Kubernetes. Korrektsed sulgemised Terminate | ProHoster","description":"Kubernetes'e parimad praktikud.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-korrektnoe-otklyuchenie-terminate","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. \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\/et\/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\/et\/wp-json\/wp\/v2\/posts\/82913","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=82913"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/82913\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/82914"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=82913"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=82913"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=82913"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}