{"id":80076,"date":"2020-05-03T01:42:34","date_gmt":"2020-05-02T23:42:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt"},"modified":"2020-05-03T01:42:34","modified_gmt":"2020-05-02T23:42:34","slug":"proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt","title":{"rendered":"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>M\u00e4rk. t\u00f5lge.<\/b>: see this material from the educational project <noindex><a rel=\"nofollow\" href=\"https:\/\/learnk8s.io\/\">learnk8s<\/a><\/noindex> \u2014 the answer to a popular question when designing infrastructure based on Kubernetes. We hope that the sufficiently detailed descriptions of the pros and cons of each option will help you make the best choice for your project.<\/i><\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/d3cc3b7e686e39032b1f02f3e8b6c46c.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>TL;DR<\/b>: sama koormuskomplekt saab t\u00f6\u00f6tada mitmes suures klastris (iga klastri jaoks on palju koormusi) v\u00f5i paljusid v\u00e4ikseid (igal klastri puhul on v\u00e4he koormusi).<\/p>\n<p>Below is a table evaluating the pros and cons of each approach:<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/ab5b5fefc97c3befddbaeb0791f8a90d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nWhen using Kubernetes as a platform for application operations, several fundamental questions about cluster configuration often arise:<\/p>\n<ul>\n<li> <i>How many clusters to use?<\/i><\/li>\n<li> <i>How large should they be?<\/i><\/li>\n<li> <i>What should each cluster include?<\/i><\/li>\n<\/ul>\n<p>\nIn this article, I will try to answer all these questions by analyzing the pros and cons of each approach.<\/p>\n<h2>The question posed<\/h2>\n<p>\nAs a software creator, you are likely developing and operating multiple applications simultaneously.<\/p>\n<p>Lisaks sellele t\u00f6\u00f6tab kindlasti palju nende rakenduste koopiaid erinevates keskkondades \u2014 n\u00e4iteks v\u00f5ivad need olla <i>dev<\/i>, <i>test<\/i> ja <i>prod<\/i>.<\/p>\n<p>Tulemusena saame terviku rakenduste ja keskkondade maatriksi:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/f2a811fa82e1e433463ba25d29f837e6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Rakendused ja keskkonnad<\/i><\/p>\n<p>\u00dclaltoodud n\u00e4ites on esitatud 3 rakendust ja 3 keskkonda, mis kokku annab 9 v\u00f5imalikku varianti.<\/p>\n<p>Iga rakenduse eksemplar on iseseisev deployment-\u00fcksus, millega saab t\u00f6\u00f6tada s\u00f5ltumatult teistest.<\/p>\n<p><i>Pange t\u00e4hele, et <b>rakenduse eksemplar<\/b> v\u00f5ib koosneda paljusid <b>komponente<\/b>, nagu frontend, backend, andmebaas jne. Mikroteenuste rakenduse korral sisaldab eksemplar k\u00f5iki mikroteenuseid.<\/i><\/p>\n<p>Seet\u00f5ttu t\u00f5statavad Kubernetes'e kasutajad mitmeid k\u00fcsimusi:<\/p>\n<ul>\n<li> Kas tuleks k\u00f5ik rakenduse eksemplarid paigutada \u00fchte klastrisse?<\/li>\n<li> Kas tuleks iga rakenduse eksemplari jaoks luua eraldi klaster?<\/li>\n<li> V\u00f5i v\u00f5ib-olla tuleks kasutada kombinatsiooni eespool mainitud l\u00e4henemistest?<\/li>\n<\/ul>\n<p>\nK\u00f5ik need variandid on t\u00e4iesti eluj\u00f5ulised, kuna Kubernetes on paindlik s\u00fcsteem, mis ei piira kasutaja v\u00f5imalusi.<\/p>\n<p>Siin on m\u00f5ned v\u00f5imalused:<\/p>\n<ul>\n<li> \u00fcks suur \u00fchine klastri;<\/li>\n<li> mitu v\u00e4ikest kitsalt spetsialiseerunud klastrit;<\/li>\n<li> \u00fcks klaster iga rakenduse jaoks;<\/li>\n<li> \u00fcks klaster iga keskkonna jaoks.<\/li>\n<\/ul>\n<p>\nNagu allpool n\u00e4idatud, on kaks esimest l\u00e4henemist skaalal vastassuunal:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/99b8fd0d1e4173705e7996cf8ccb6eec.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>M\u00f5nest suurest klastrist (vasakul) kuni paljude v\u00e4ikesteni (paremal)<\/i><\/p>\n<p><i>\u00dcldiselt peetakse \u00fcht klastrit teistest \"suuremaks\", kui tal on rohkem s\u00f5lmi ja pod'e summas. N\u00e4iteks klastri, millel on 10 s\u00f5lme ja 100 pod'i, m\u00e4\u00e4ratletakse suuremana kui klastri, millel on 1 s\u00f5lm ja 10 pod'i.<\/i><\/p>\n<p>Nojah, alustame!<\/p>\n<h2>1. \u00dcks suur \u00fchine klaster<\/h2>\n<p>\nEsimene variant on paigutada k\u00f5ik t\u00f6\u00f6koormused \u00fchte klastrisse:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/283fc3c3f5ccb40a157ccff600628114.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>\u00dcks suur klaster<\/i><\/p>\n<p>Selle l\u00e4henemise raames kasutatakse klastrit universaalse <b>infrastruktuuri platvormina<\/b> \u2014 k\u00f5ik, mis vajalik, on lihtsalt olemasolevas Kubernetes klastris paigutatud.<\/p>\n<p><i><noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/overview\/working-with-objects\/namespaces\/\">Nimede ruumid<\/a><\/noindex> Kubernetes v\u00f5imaldab klastris osi \u00fcksteisest loogiliselt eraldada, mist\u00f5ttu iga rakenduse eksemplarile saab kasutada oma nimeala.<\/i><\/p>\n<p><i>Vaatame selle l\u00e4henemise plusse ja miinuseid.<\/i><\/p>\n<h3>+ T\u00f5hus resursside kasutamine<\/h3>\n<p>\nAinult \u00fche klastriga on vajalik ainult \u00fcks koopia k\u00f5ikidest ressurssidest, mis on vajalikud Kubernetesi klastri k\u00e4ivitamiseks ja haldamiseks.<\/p>\n<p>N\u00e4iteks kehtib see master-s\u00f5lmede kohta. \u00dche Kubernetesi klastri kohta on tavaliselt 3 master-s\u00f5lme, seega j\u00e4\u00e4b nende arv \u00fchele klastrile samaks (v\u00f5rdluseks, 10 klastrile on vaja 30 master-s\u00f5lme).<\/p>\n<p>\u00dclaltoodud n\u00fcanss kehtib ka teiste teenuste kohta, mis toimivad klastris laiemalt, nagu koormuse tasakaalustajad, Ingressi kontrollerid, autentimise, logimise ja j\u00e4lgimise s\u00fcsteemid.<\/p>\n<p>\u00dches klastri k\u00f5ik neid teenuseid saab kasutada kohe k\u00f5igi t\u00f6\u00f6koormuste jaoks (pole vaja luua nende koopiaid, nagu mitme klastriga).<\/p>\n<h3>+ Odavus<\/h3>\n<p>\nSeet\u00f5ttu maksab v\u00e4iksem arv klastreid tavaliselt v\u00e4hem, kuna puuduvad kulutused \u00fcleliigsetele ressurssidele.<\/p>\n<p>See kehtib eriti master-s\u00f5lmede kohta, millel v\u00f5ivad olla m\u00e4rkimisv\u00e4\u00e4rsed kulud, s\u00f5ltumata majutamisviisist (kas kohapeal v\u00f5i pilves).<\/p>\n<p>M\u00f5ned hallatud Kubernetes teenused, nagu <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/kubernetes-engine\">Google Kubernetes Engine (GKE)<\/a><\/noindex> v\u00f5i <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/aks\/\">Azure Kubernetes Service (AKS)<\/a><\/noindex>, pakuvad tasuta haldustaseme. Sellisel juhul on kuluk\u00fcsimus v\u00e4hem terav.<\/p>\n<p>Samuti on olemas hallatud teenused, mis k\u00fcsivad fikseeritud tasu iga Kubernetes'i klastrite t\u00f6\u00f6 eest (n\u00e4iteks, <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/eks\/\">Amazon Elastic Kubernetes Service, EKS<\/a><\/noindex>).<\/p>\n<h3>+ T\u00f5hus haldus<\/h3>\n<p>\n\u00dcht klastrit on lihtsam hallata kui mitut.<\/p>\n<p>Haldus v\u00f5ib h\u00f5lmata j\u00e4rgmisi \u00fclesandeid:<\/p>\n<ul>\n<li> Kubernetes'e versiooni v\u00e4rskendamine;<\/li>\n<li> CI\/CD torujuhtme seadistamine;<\/li>\n<li> CNI pistiku installimine;<\/li>\n<li> Kasutaja autentimiss\u00fcsteemi seadistamine;<\/li>\n<li> Luba kontrolleri installimine;<\/li>\n<\/ul>\n<p>\nja palju muud\u2026<\/p>\n<p>\u00dche klastriga on vaja seda k\u00f5ike teha ainult \u00fcks kord.<\/p>\n<p>Mitme klastri puhul tuleb operatsioone korduvalt korrata, mis t\u00f5en\u00e4oliselt vajab protsesside ja t\u00f6\u00f6riistade automatiseerimist, et tagada j\u00e4rjepidevus ja \u00fchtsus.<\/p>\n<p><i>Ja n\u00fc\u00fcd paar s\u00f5na puudustest.<\/i><\/p>\n<h3>\u2212 \u00dcksik rikkepunkt<\/h3>\n<p>\n\u00dcksiku <i>klastri rikke korral lakka<\/i> vahetult t\u00f6\u00f6tama <i>k\u00f5ik<\/i> koormused!<\/p>\n<p>On tohutult v\u00f5imalusi, kus midagi v\u00f5iks valesti minna:<\/p>\n<ul>\n<li> Kubernetes'e v\u00e4rskendamine toob ootamatud k\u00f5rvaltoimed;<\/li>\n<li> \u00fcldklastrikomponent (n\u00e4iteks CNI pistikprogramm) k\u00e4ivitub ootamatult;<\/li>\n<li> \u00fcks grupi komponentidest on valesti seadistatud;<\/li>\n<li> aluseks oleva infrastruktuuri rike.<\/li>\n<\/ul>\n<p>\n\u00dcks selline juhtum v\u00f5ib t\u00f5siselt kahjustada k\u00f5iki t\u00f6\u00f6koormusi, mis on paigutatud \u00fcldklastrisse.<\/p>\n<h3>\u2212 Rangete isoleerimise puudumine<\/h3>\n<p>\nT\u00f6\u00f6tamine \u00fcldklastris t\u00e4hendab, et rakendused jagavad riistvara, v\u00f5rguv\u00f5imalusi ja operatsioonis\u00fcsteemi klastris\u00f5lmede vahel.<\/p>\n<p>M\u00f5nes m\u00f5ttes on kaks konteinerit, kus t\u00f6\u00f6tab kaks erinevat rakendust samas s\u00f5lmes, sarnased kahele protsessile, mis t\u00f6\u00f6tavad \u00fchel ja samal masinal sama operatsioonis\u00fcsteemi tuuma all.<\/p>\n<p><i>Linuxi konteinerid pakuvad mingit vormi isoleerimisest, kuid see ei ole sugugi nii tugev, kui n\u00e4iteks virtuaalmasinate korral. P\u00f5him\u00f5tteliselt on konteineris olev protsess sama protsess, mis k\u00e4ivitatakse hostoperatsioonis\u00fcsteemis.<\/i><\/p>\n<p>See v\u00f5ib olla turvalisuse seisukohalt probleem: selline korraldus v\u00f5imaldab teoreetiliselt omavahel seotud rakendustel \u00fcksteisega suhelda (kas teadlikult v\u00f5i kogemata).<\/p>\n<p>Lisaks kasutavad k\u00f5ik Kubernetes klastri t\u00f6\u00f6koormused \u00fchiselt m\u00f5ningaid klastriteenuseid, nagu <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/services-networking\/dns-pod-service\/\">DNS<\/a><\/noindex> \u2013 see v\u00f5imaldab rakendustel leida teiste rakenduste teenuseid klastris.<\/p>\n<p><i>K\u00f5igil \u00fclaltoodud punktidel v\u00f5ib olla erinev t\u00e4hendus s\u00f5ltuvalt rakenduste turvan\u00f5uetest.<\/i><\/p>\n<p>Kubernetes pakub erinevaid t\u00f6\u00f6riistu turvaprobleemide v\u00e4ltimiseks, nagu <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/policy\/pod-security-policy\/\">PodSecurityPolicies<\/a><\/noindex> ja <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/services-networking\/network-policies\/\">NetworkPolicies<\/a><\/noindex>. Kuid nende \u00f5ige seadistamine n\u00f5uab teatud kogemust, pealegi ei ole nad v\u00f5imelised sulgema absoluutselt k\u00f5iki turvaauke.<\/p>\n<p>Oluline on alati meeles pidada, et Kubernetes on algselt loodud <i>koost\u00f6\u00f6ks<\/i>, mitte <i>isolatsiooni ja turvalisuse<\/i>.<\/p>\n<h3>\u2212 J\u00f5hkralt puudub multi-tenancy.<\/h3>\n<p>\nArvestades Kubernetes klastri hulka \u00fchiseid ressursse, on palju viise, kuidas erinevad rakendused v\u00f5ivad \u00fcksteisele \u201cpeale astuda\u201d.<\/p>\n<p>N\u00e4iteks v\u00f5ib rakendus monopoliseerida m\u00f5ne \u00fchise ressursi (nagu protsessor v\u00f5i m\u00e4lu) ja j\u00e4tta teised rakendused, mis t\u00f6\u00f6tavad samas s\u00f5lmes, sellest ilma.<\/p>\n<p>Kubernetes tagab erinevad mehhanismid sellise k\u00e4itumise kontrollimiseks, nagu <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/configuration\/manage-compute-resources-container\/\">ressursside p\u00e4ringud ja piirangud<\/a><\/noindex> <i>vt ka artiklit \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/489668\/\"> CPU piirangud ja agressiivne trottling Kuberneteses <\/a><\/noindex>\u00bb \u2014 t\u00f5lk. m\u00e4rkus)<\/i>, <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/policy\/resource-quotas\/\">ResourceQuotas<\/a><\/noindex> ja <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/policy\/limit-range\/\">LimitRanges<\/a><\/noindex>. Siiski, nagu ka turvalisuse puhul, on nende seadistamine piisavalt keeruline ja need ei suuda v\u00e4ltida k\u00f5iki etten\u00e4gematuid k\u00f5rvalm\u00f5jusid.<\/p>\n<h3>\u2212 Suur hulk kasutajaid<\/h3>\n<p>\n\u00dche klastriga peab juurdep\u00e4\u00e4su avama paljudele inimestele. Ja mida rohkem neid on, seda suurem on risk, et nad midagi \"katkestavad\".<\/p>\n<p>Klastri sees saab hallata, kes ja mida teha saab, kasutades <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/reference\/access-authn-authz\/rbac\/\">rollip\u00f5hist juurdep\u00e4\u00e4su haldust (RBAC)<\/a><\/noindex> <i>vt artiklit \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/470503\/\"> Kasutajad ja autoriseerimine RBAC Kuberneteses <\/a><\/noindex>\u00bb \u2014 t\u00f5lk. m\u00e4rkus)<\/i>. Siiski ei takista see kasutajaid \"katkestamast\" midagi oma vastutusala piires.<\/p>\n<h3>\u2212 Klastrid ei saa kasvama kuni l\u00f5pmatuseni<\/h3>\n<p>\nKlastrit, mida kasutatakse k\u00f5igi t\u00f6\u00f6koormuste jaoks, peetakse t\u00f5en\u00e4oliselt v\u00e4ga suureks (s\u00f5lmede ja pod'ide arvu poolest).<\/p>\n<p>Kuid siin tekib teine probleem: Kuberneteses ei saa klastrid kasvada l\u00f5pmatuseni.<\/p>\n<p>Klastri suuruse teoreetiline piir on olemas. Kuberneteses on see ligikaudu <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/setup\/best-practices\/cluster-large\/\">5000 s\u00f5lme, 150 tuhat pod'i ja 300 tuhat konteinerit<\/a><\/noindex>.<\/p>\n<p>Kuid tegelikus elus v\u00f5ivad probleemid alata palju varem \u2013 n\u00e4iteks juba 500 node'iga. <noindex><a rel=\"nofollow\" href=\"https:\/\/events19.lfasiallc.com\/wp-content\/uploads\/2017\/11\/BoF_-Not-One-Size-Fits-All-How-to-Size-Kubernetes-Clusters_Guang-Ya-Liu-_-Sahdev-Zala.pdf\">Asi on selles, et suured klastrid koormavad Kubernetes'i juhtimistaset tugevalt. Teisis\u00f5nu, et hoida klastrit t\u00f6\u00f6korras ja kasutada ressursse efektiivselt, on vajalik hoolikas konfigureerimine.<\/a><\/noindex>.<\/p>\n<p>Seda probleemi uuritakse vastavas artiklis algses p\u00e4evas, pealkirjaga \u00ab<\/p>\n<p><i>Architecting Kubernetes clusters \u2014 choosing a worker node size<noindex><a rel=\"nofollow\" href=\"https:\/\/learnk8s.io\/kubernetes-node-size\">Aga vaatame vastupidist l\u00e4henemist: palju v\u00e4ikseid klastreid.<\/a><\/noindex>\u00bb.<\/i><\/p>\n<p><i>2. Palju v\u00e4ikeseid, spetsialiseeritud klastreid.<\/i><\/p>\n<h2>Selle l\u00e4henemise korral kasutate iga paigaldatava elemendi jaoks eraldi klastrit:<\/h2>\n<p>\nPalju v\u00e4ikeseid klustreid.<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/2320f62d945944f2e26f07252e9b8440.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>K\u00e4esoleva artikli eesm\u00e4rkidel peame<\/i><\/p>\n<p>paigaldatavaks elemendiks <i>juurutatud element<\/i> rakendusinstance m\u00f5istetakse - n\u00e4iteks, arenduse versioon eraldiseisvast rakendusest.<\/p>\n<p>Selles strateegias kasutatakse Kubernetes't kui spetsialiseeritud <b>k\u00e4ituskeskkonda<\/b> erakordsete rakenduste jaoks.<\/p>\n<p><i>Vaatame selle l\u00e4henemise plusse ja miinuseid.<\/i><\/p>\n<h3>+ Piiratud \"plahvatuse ring\"<\/h3>\n<p>\nKui klaster \"rikub\", piirnevad negatiivsed tagaj\u00e4rjed ainult nende t\u00f6\u00f6koormustega, mis olid sellel klastril. K\u00f5ik teised koormused j\u00e4\u00e4vad puutumatuks.<\/p>\n<h3>+ Isolatsioon<\/h3>\n<p>\nEraldatud klastrites paigutatud t\u00f6\u00f6koormustel ei ole \u00fchiseid ressursse, nagu protsessor, m\u00e4lu, ops\u00fcsteem, v\u00f5rk v\u00f5i muud teenused.<\/p>\n<p>Tulemuseks on range isolatsioon omavahel seotud rakenduste vahel, mis v\u00f5ib soodsalt m\u00f5jutada nende turvalisust.<\/p>\n<h3>+ V\u00e4ike kasutajate arv<\/h3>\n<p>\nKuna igas klastris on vaid piiratud arv t\u00f6\u00f6koormusi, v\u00e4heneb sellele juurdep\u00e4\u00e4su saavate kasutajate arv.<\/p>\n<p>Mida v\u00e4hem inimesi p\u00e4\u00e4seb klastrile ligi, seda madalam on risk, et midagi \"katki l\u00e4heb\".<\/p>\n<p><i>Vaatame miinuseid.<\/i><\/p>\n<h3>\u2212 Ressursside ebaefektiivne kasutamine<\/h3>\n<p>\nNagu varem mainitud, vajab iga Kubernetes'i klaster teatud haldusressursse: master-s\u00f5lmed, kontrollitasandi komponendid, j\u00e4lgimis- ja logimislahendused.<\/p>\n<p>Kui on palju v\u00e4ikse v\u00e4ikseid klastreid, tuleb rohkem ressursse eraldada halduseks.<\/p>\n<h3>\u2212 Kulukus<\/h3>\n<p>\nEbat\u00f5hus ressursikasutus toob automaatselt kaasa k\u00f5rged kulud.<\/p>\n<p>N\u00e4iteks 30 master-s\u00f5lme hoidmine kolme asemel sama arvutusv\u00f5imsuse juures m\u00f5jutab kindlasti kulusid.<\/p>\n<h3>\u2212 Halduse keerukus<\/h3>\n<p>\nPaljude Kubernetes'i klastrite haldamine on palju keerulisem kui \u00fchega t\u00f6\u00f6tamine.<\/p>\n<p>N\u00e4iteks tuleb iga klastrite jaoks seadistada autentimine ja autoriseerimine. Kubernetes'i versiooniuuendust tuleb samuti teha mitu korda.<\/p>\n<p>T\u00f5en\u00e4oliselt tuleb rakendada automatiseerimist, et suurendada nende \u00fclesannete t\u00f5husust.<\/p>\n<p><i>N\u00fc\u00fcd vaatame v\u00e4hem \u00e4\u00e4rmuslikke stsenaariume.<\/i><\/p>\n<h2>3. \u00dcks klaster iga rakenduse jaoks<\/h2>\n<p>\nSelle l\u00e4henemise raames loote eraldi klastri k\u00f5igi konkreetse rakenduse eksemplaride jaoks:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/238ee74d4e4dc42b7daeadc1ce484905.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Rakenduse klaster<\/i><\/p>\n<p>Seda teed v\u00f5ib pidada p\u00f5him\u00f5tte \u00ab<b>erinev klaster meeskonna jaoks<\/b>\u00bb \u00fcldistamiseks, kuna tavaliselt tegeleb inseneride meeskond \u00fche v\u00f5i mitme rakenduse arendamisega.<\/p>\n<p><i>Vaatame selle l\u00e4henemise plusse ja miinuseid.<\/i><\/p>\n<h3>+ Klastrit saab rakendusele kohandada<\/h3>\n<p>\nKui rakendusel on erilised vajadused, saab neid klastri sees ellu viia, m\u00f5jutamata teisi klastreid.<\/p>\n<p>Sellised vajadused v\u00f5ivad h\u00f5lmata GPU-dega t\u00f6\u00f6tajaid, teatud CNI pluginaid, teenuste mesh'i v\u00f5i m\u00f5nda muud teenust.<\/p>\n<p>Iga klaster saab kohandada t\u00f6\u00f6tavale rakendusele, et see sisaldaks ainult vajalikke elemente.<\/p>\n<h3>\u2212 Erinevad keskkonnad \u00fches klastris<\/h3>\n<p>\nSelle l\u00e4henemise miinuseks on see, et erinevate keskkondade rakenduse eksemplarid eksisteerivad \u00fches klastris.<\/p>\n<p>N\u00e4iteks t\u00f6\u00f6tab rakenduse prod-version samas klastris nagu dev-version. See t\u00e4hendab ka, et arendajad tegutsevad samas klastris, kus toodang on rakenduse versioon.<\/p>\n<p>Kui arendajate tegevuse v\u00f5i dev-versiooni vead p\u00f5hjustavad klastris rikke, v\u00f5ib potentsiaalselt kannatada ka prod-version \u2014 selle l\u00e4henemise suur puudus.<\/p>\n<p><i>Ja l\u00f5puks, viimane stsenaarium meie nimekirjas.<\/i><\/p>\n<h2>4. \u00dcks klaster igas keskkonnas<\/h2>\n<p>\nSee stsenaarium n\u00e4eb ette igas keskkonnas eraldi klastri eraldamist:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes-klastrite projekteerimine: kui palju neid peaks olema?\" src=\"\/wp-content\/uploads\/2020\/05\/157da599edf178832b1b15459786fbc8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>\u00dcks klaster iga keskkonna jaoks<\/i><\/p>\n<p>N\u00e4iteks v\u00f5ivad teil olla klastrid, <i>dev<\/i>, <i>test<\/i> ja <i>prod<\/i>, kus k\u00e4itate k\u00f5iki rakenduse eksemplare, mis on m\u00f5eldud kindlale keskkonnale.<\/p>\n<p><i>Siin on selle l\u00e4henemise plussid ja miinused.<\/i><\/p>\n<h3>+ Produktiivsete keskkondade isoleerimine<\/h3>\n<p>\nSelle l\u00e4henemise raames on k\u00f5ik keskkonnad teineteisest isoleeritud. Kuid praktikas on see eriti oluline tootmiskeskkonna jaoks.<\/p>\n<p>Rakenduse tootmisversioonid ei s\u00f5ltu enam muudest klastritest ja keskkondadest.<\/p>\n<p>Nii et kui dev-klastris tekib \u00e4kki probleem, j\u00e4tkavad tootmisversioonid t\u00f6\u00f6tamist nagu midagi ei juhtunud.<\/p>\n<h3>+ Klastrit saab kohandada keskkonna j\u00e4rgi<\/h3>\n<p>\nIga klastrit saab kohandada oma keskkonna jaoks. N\u00e4iteks v\u00f5ib:<\/p>\n<ul>\n<li> paigaldada dev-klastrisse arendamise ja t\u00f5rkeotsingu t\u00f6\u00f6riistad;<\/li>\n<li> paigaldada testimisraamistikke ja t\u00f6\u00f6riistu klastrisse <i>test<\/i>;<\/li>\n<li> kasutada klastris v\u00f5imsamat riistvara ja v\u00f5rgu\u00fchendusi. <i>prod<\/i>.<\/li>\n<\/ul>\n<p>\nSee aitab suurendada nii arenduse kui ka rakenduste haldamise t\u00f5husust.<\/p>\n<h3>+ Juhtimise piiramine production-klastrisse<\/h3>\n<p>\nOtsene t\u00f6\u00f6tamine prod-klastriga on haruldane, seega on v\u00f5imalik oluliselt piirata neid, kellel on sellele juurdep\u00e4\u00e4s.<\/p>\n<p>Saame minna veelgi kaugemale ja t\u00e4iesti keelata inimeste juurdep\u00e4\u00e4su sellele klastrile, tehes k\u00f5ik juurutamised automatiseeritud CI\/CD t\u00f6\u00f6riista abil. Selline l\u00e4henemine v\u00e4hendab inimlike vigade riski just seal, kus see on k\u00f5ige olulisem.<\/p>\n<p><i>Ja n\u00fc\u00fcd paar s\u00f5na puudustest.<\/i><\/p>\n<h3>\u2212 Aparaadi ja ressursside isolatsiooni puudumine rakenduste vahel<\/h3>\n<p>\nPeamine puudus on see, et rakenduste vahel puudub riistvara ja ressursside isolatsioon.<\/p>\n<p>\u00dcksikud rakendused kasutavad koos klastrite ressursside s\u00fcsteemi, protsessorit, m\u00e4lu ja m\u00f5ningaid teisi teenuseid.<\/p>\n<p>Nagu juba mainitud, v\u00f5ib see osutuda potentsiaalselt ohtlikuks.<\/p>\n<h3>\u2212 Rakenduste s\u00f5ltuvuste lokaliseerimise v\u00f5imatus<\/h3>\n<p>\nKui rakendusel on erilised n\u00f5udmised, tuleb neid t\u00e4ita k\u00f5igis klastrites.<\/p>\n<p>N\u00e4iteks, kui rakendus vajab GPU-d, peab iga klaster sisaldama v\u00e4hemalt \u00fchte GPU-ga t\u00f6\u00f6tlus\u00fcksust (isegi kui seda kasutatakse ainult selle rakenduse poolt).<\/p>\n<p>Tulemuseks on suuremad kulud ja ebaefektiivne ressursside kasutamine.<\/p>\n<h2>Kokkuv\u00f5te<\/h2>\n<p>\nKuna on olemas teatud rakenduste komplekt, saab need paigutada paarisse suurtesse klastritesse v\u00f5i paljudesse v\u00e4ikestesse.<\/p>\n<p>Artiklis k\u00e4sitletakse erinevate l\u00e4henemisviiside plusse ja miinuseid, alates \u00fchest globaalsest klastrist kuni paljude v\u00e4ikeste ja kitsaste:<\/p>\n<ul>\n<li> \u00fcks suur \u00fchisklaster;<\/li>\n<li> mitu v\u00e4ikest kitsalt spetsialiseerunud klastrit;<\/li>\n<li> \u00fcks klaster iga rakenduse jaoks;<\/li>\n<li> \u00fcks klaster iga keskkonna jaoks.<\/li>\n<\/ul>\n<p>\n<i>Niisiis, millist l\u00e4henemist valida?<\/i><\/p>\n<p>Nagu tavaliselt, s\u00f5ltub vastus kasutusstsenaariumist: tuleb kaaluda erinevate l\u00e4henemisviiside plusse ja miinuseid ning valida k\u00f5ige optimaalsem variant.<\/p>\n<p>Kuid valik ei piirdu ainult eespool toodud n\u00e4idetega \u2013 v\u00f5ib rakendada igasugust kombinatsiooni!<\/p>\n<p>N\u00e4iteks v\u00f5ib korraldada igale meeskonnale paar klastrit: arenduse klaster (kus on keskkonnad <i>dev<\/i> ja <i>test<\/i>) ja klaster <i>tootmisse<\/i> (kus asub tootmiskeskkond).<\/p>\n<p>Tuginedes sellele artiklile, saate vastavalt optimeerida iga variandi plussid ja miinused konkreetse stsenaariumi jaoks. Edu!<\/p>\n<h2>P.S.<\/h2>\n<p>\nLugege ka meie blogist:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/484954\/\">Visuaalne juhend Kubernetes'e t\u00f5rgete diagnoosimiseks<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/480946\/\">Logid Kuberneteses (ja mitte ainult) t\u00e4na: ootused ja reaalsus<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/478306\/\">Teenusete v\u00f5rk: mida iga tarkvarainsener peab teadma k\u00f5ige populaarsemast tehnoloogiast<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468679\/\">Kubernetes'e turvaabitus: autentimine, autoriseerimine, audit<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Allikas: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/498100\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e\u0442 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b \u043e\u0442 \u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 learnk8s \u2014 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u044b\u0439 \u0432\u043e\u043f\u0440\u043e\u0441 \u043f\u0440\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043d\u0430 \u0431\u0430\u0437\u0435 Kubernetes. \u041d\u0430\u0434\u0435\u0435\u043c\u0441\u044f, \u0447\u0442\u043e \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0437\u0432\u0451\u0440\u043d\u0443\u0442\u044b\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f \u043f\u043b\u044e\u0441\u043e\u0432 \u0438 \u043c\u0438\u043d\u0443\u0441\u043e\u0432 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0438\u0437 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u043e\u043f\u0442\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u0431\u043e\u0440 \u0438 \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430. TL;DR: \u043e\u0434\u0438\u043d \u0438 \u0442\u043e\u0442 \u0436\u0435 \u043d\u0430\u0431\u043e\u0440 \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u043d\u0430\u0433\u0440\u0443\u0437\u043e\u043a \u043c\u043e\u0436\u043d\u043e \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u043d\u0430 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u0445 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430\u0445 (\u043d\u0430 \u043a\u0430\u0436\u0434\u044b\u0439 \u043a\u043b\u0430\u0441\u0442\u0435\u0440 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":80077,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-80076","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e\u0442 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b \u043e\u0442 \u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 learnk8s \u2014 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u044b\u0439 \u0432\u043e\u043f\u0440\u043e\u0441 \u043f\u0440\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043d\u0430 \u0431\u0430\u0437\u0435 Kubernetes. \u041d\u0430\u0434\u0435\u0435\u043c\u0441\u044f, \u0447\u0442\u043e \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0437\u0432\u0451\u0440\u043d\u0443\u0442\u044b\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f \u043f\u043b\u044e\u0441\u043e\u0432 \u0438 \u043c\u0438\u043d\u0443\u0441\u043e\u0432 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0438\u0437 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u043e\u043f\u0442\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u0431\u043e\u0440 \u0438 \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430. TL;DR: \u043e\u0434\u0438\u043d \u0438 \u0442\u043e\u0442 \u0436\u0435 \u043d\u0430\u0431\u043e\u0440 \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u043d\u0430\u0433\u0440\u0443\u0437\u043e\u043a \u043c\u043e\u0436\u043d\u043e \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u043d\u0430 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u0445 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430\u0445 (\u043d\u0430 \u043a\u0430\u0436\u0434\u044b\u0439 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 Kubernetes-\u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432: \u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0438\u0445 \u0434\u043e\u043b\u0436\u043d\u043e \u0431\u044b\u0442\u044c? | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e\u0442 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b \u043e\u0442 \u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 learnk8s \u2014 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u044b\u0439 \u0432\u043e\u043f\u0440\u043e\u0441 \u043f\u0440\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043d\u0430 \u0431\u0430\u0437\u0435 Kubernetes. \u041d\u0430\u0434\u0435\u0435\u043c\u0441\u044f, \u0447\u0442\u043e \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0437\u0432\u0451\u0440\u043d\u0443\u0442\u044b\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f \u043f\u043b\u044e\u0441\u043e\u0432 \u0438 \u043c\u0438\u043d\u0443\u0441\u043e\u0432 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0438\u0437 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u043e\u043f\u0442\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u0431\u043e\u0440 \u0438 \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430. TL;DR: \u043e\u0434\u0438\u043d \u0438 \u0442\u043e\u0442 \u0436\u0435 \u043d\u0430\u0431\u043e\u0440 \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u043d\u0430\u0433\u0440\u0443\u0437\u043e\u043a \u043c\u043e\u0436\u043d\u043e \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u043d\u0430 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u0445 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430\u0445 (\u043d\u0430 \u043a\u0430\u0436\u0434\u044b\u0439 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-05-02T23:42:34+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-02T23:42:34+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kubernetes-klaastrite projekteerimine: kui palju neid peaks olema? | ProHoster","description":"M\u00e4rkus t\u00f5lkijalt: see materjal p\u00e4rineb \u00f5ppeprojektist learnk8s \u2014 vastus populaarsele k\u00fcsimusele Kubernetesel p\u00f5hineva infrastruktuuri projekteerimisel. Loodame, et piisavalt p\u00f5hjalikud plusside ja miinuste kirjeldused aitavad leida teie projektile parima lahenduse. TL;DR: sama koormuste kogumit saab k\u00e4itada mitmes suures klastris (iga k\u00fcber)","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt","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\u041f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 Kubernetes-\u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432: \u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0438\u0445 \u0434\u043e\u043b\u0436\u043d\u043e \u0431\u044b\u0442\u044c? | ProHoster","og:description":"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e\u0442 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b \u043e\u0442 \u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 learnk8s \u2014 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u044b\u0439 \u0432\u043e\u043f\u0440\u043e\u0441 \u043f\u0440\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043d\u0430 \u0431\u0430\u0437\u0435 Kubernetes. \u041d\u0430\u0434\u0435\u0435\u043c\u0441\u044f, \u0447\u0442\u043e \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0437\u0432\u0451\u0440\u043d\u0443\u0442\u044b\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f \u043f\u043b\u044e\u0441\u043e\u0432 \u0438 \u043c\u0438\u043d\u0443\u0441\u043e\u0432 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0438\u0437 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u043e\u043f\u0442\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u0431\u043e\u0440 \u0438 \u0434\u043b\u044f \u0432\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430. TL;DR: \u043e\u0434\u0438\u043d \u0438 \u0442\u043e\u0442 \u0436\u0435 \u043d\u0430\u0431\u043e\u0440 \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u043d\u0430\u0433\u0440\u0443\u0437\u043e\u043a \u043c\u043e\u0436\u043d\u043e \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u043d\u0430 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u0445 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430\u0445 (\u043d\u0430 \u043a\u0430\u0436\u0434\u044b\u0439 \u043a\u043b\u0430\u0441\u0442\u0435\u0440","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/proektirovanie-kubernetes-klasterov-skolko-ih-dolzhno-byt","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-02T23:42:34+00:00","article:modified_time":"2020-05-02T23:42:34+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"80076","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 16:24:58","updated":"2022-10-02 20:23:35"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/80076","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=80076"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/80076\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/80077"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=80076"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=80076"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=80076"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}