{"id":78373,"date":"2020-04-19T01:42:20","date_gmt":"2020-04-18T23:42:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-i-rekomendaczii-dlya-zapuska-kontejnerov-i-kubernetes-v-proizvodstvennyh-sredah"},"modified":"2020-04-19T01:42:20","modified_gmt":"2020-04-18T23:42:20","slug":"luchshie-praktiki-i-rekomendaczii-dlya-zapuska-kontejnerov-i-kubernetes-v-proizvodstvennyh-sredah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-i-rekomendaczii-dlya-zapuska-kontejnerov-i-kubernetes-v-proizvodstvennyh-sredah","title":{"rendered":"Najlep\u0161ie praktiky a odpor\u00fa\u010dania pre sp\u00fa\u0161\u0165anie kontajnerov a Kubernetes v produk\u010dn\u00fdch prostrediach","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Najlep\u0161ie
\nEkosyst\u00e9m technol\u00f3gi\u00ed kontajneriz\u00e1cie sa r\u00fdchlo vyv\u00edja a men\u00ed, a preto v tejto oblasti ch\u00fdbaj\u00fa dobr\u00e9 pracovn\u00e9 praktiky. Napriek tomu sa Kubernetes a kontajnery pou\u017e\u00edvaj\u00fa \u010doraz \u010dastej\u0161ie \u2013 ako pre moderniz\u00e1ciu star\u00fdch aplik\u00e1ci\u00ed, tak aj pre v\u00fdvoj modern\u00fdch cloudov\u00fdch aplik\u00e1ci\u00ed.\u00a0<\/p>\n

T\u00edm Kubernetes aaS od Mail.ru<\/a><\/noindex> zhroma\u017edili predpovede, rady a najlep\u0161ie praktiky pre l\u00eddrov trhu od Gartner, 451 Research, StacxRo\u0445 a \u010fal\u0161\u00edch. Tieto poskytn\u00fa zabezpe\u010denie a ur\u00fdchlenie nasadenia kontajnerov v produk\u010dn\u00fdch prostrediach.
\n<\/a><\/noindex><\/p>\n

Ako zisti\u0165, \u010di je va\u0161a spolo\u010dnos\u0165 pripraven\u00e1 nasadi\u0165 kontajnery v produk\u010dnom prostred\u00ed<\/h2>\n

\nPod\u013ea Gartnera<\/a><\/noindex>, v roku 2022 viac ako 75% organiz\u00e1ci\u00ed bude pou\u017e\u00edva\u0165 kontajnerizovan\u00e9 aplik\u00e1cie v produkcii. To je v\u00fdrazne viac ako v s\u00fa\u010dasnosti, ke\u010f tak\u00e9to aplik\u00e1cie vyu\u017e\u00edva menej ako 30% spolo\u010dnost\u00ed.\u00a0<\/p>\n

Pod\u013ea 451 Research<\/a><\/noindex>, predpokladan\u00fd trh pre aplik\u00e1ciu kontajnerov\u00fdch technol\u00f3gi\u00ed v roku 2022 dosiahne 4,3 miliardy dol\u00e1rov. To je viac ako dvojn\u00e1sobok predpovedan\u00fdch s\u00fam z roku 2019, pri\u010dom tempo rastu trhu dosahuje 30%.<\/p>\n

V v prieskume Portworx a Aqua Security<\/a><\/noindex> 87% respondentov uviedlo, \u017ee v s\u00fa\u010dasnosti pou\u017e\u00edvaj\u00fa kontajnerov\u00e9 technol\u00f3gie. Pre porovnanie \u2013 v roku 2017 bolo tak\u00fdch respondentov 55%.\u00a0<\/p>\n

Napriek rast\u00facemu z\u00e1ujmu a n\u00e1rastu zav\u00e1dzania kontajnerov, ich spustenie v produkcii si vy\u017eaduje \u0161kolenie z d\u00f4vodu technologickej nezrelosti a nedostatku know-how. Organiz\u00e1cie by mali realisticky pos\u00fadi\u0165 obchodn\u00e9 procesy, ktor\u00e9 si vy\u017eaduj\u00fa kontajneriz\u00e1ciu aplik\u00e1ci\u00ed. IT l\u00eddri by mali pos\u00fadi\u0165, \u010di maj\u00fa potrebn\u00e9 zru\u010dnosti na pokra\u010dovanie s oh\u013eadom na potrebu r\u00fdchleho u\u010denia.\u00a0<\/p>\n

Odborn\u00edci z Gartnera<\/a><\/noindex> pova\u017euj\u00fa ot\u00e1zky na obr\u00e1zku ni\u017e\u0161ie za pomoc pri vyhodnocovan\u00ed, \u010di ste pripraven\u00ed na nasadenie kontajnerov v produkcii:<\/p>\n

\"Najlep\u0161ie<\/p>\n

Naj\u010dastej\u0161ie chyby pri aplik\u00e1cii kontajnerov v produkcii<\/h2>\n

\nOrganiz\u00e1cie \u010dasto podce\u0148uj\u00fa \u00fasilie potrebn\u00e9 na prev\u00e1dzkovanie kontajnerov v produkcii. Gartner zistil<\/a><\/noindex> nieko\u013eko be\u017en\u00fdch ch\u00fdb v scen\u00e1roch z\u00e1kazn\u00edkov pri aplik\u00e1cii kontajnerov v produk\u010dn\u00fdch prostrediach:<\/p>\n

\"Najlep\u0161ie<\/p>\n

Ako zabezpe\u010di\u0165 bezpe\u010dnos\u0165 kontajnerov<\/h2>\n

\nBezpe\u010dnos\u0165 nie je nie\u010do, \u010d\u00edm sa d\u00e1 zaobera\u0165 \u201enielen tak\u201c. Mus\u00ed by\u0165 zakomponovan\u00e1 do procesu DevOps, preto sa objavil aj \u0161peci\u00e1lny term\u00edn \u2014 DevSecOps. Organiz\u00e1cie musia pl\u00e1nova\u0165 ochranu kontajnerov\u00e9ho prostredia<\/a><\/noindex> po\u010das cel\u00e9ho \u017eivotn\u00e9ho cyklu v\u00fdvoja, ktor\u00fd zah\u0155\u0148a proces zostavovania a v\u00fdvoja, nasadenie a spustenie aplik\u00e1cie.<\/p>\n

Odpor\u00fa\u010dania od Gartner<\/a><\/noindex>:\u00a0<\/p>\n

    \n
  1. Integrujte proces skenovania obrazov aplik\u00e1ci\u00ed na vyh\u013ead\u00e1vanie zranite\u013enost\u00ed do pipeline kontinu\u00e1lnej integr\u00e1cie\/kontinu\u00e1lneho dod\u00e1vania (CI\/CD). Aplik\u00e1cie sa skenuj\u00fa po\u010das f\u00e1zy zostavovania a sp\u00fa\u0161\u0165ania softv\u00e9ru. Zd\u00f4raznite potrebu skenovania a identifik\u00e1cie komponentov s otvoren\u00fdm zdrojov\u00fdm k\u00f3dom, kni\u017en\u00edc a r\u00e1mcov. Pou\u017e\u00edvanie star\u0161\u00edch zranite\u013en\u00fdch verzi\u00ed v\u00fdvoj\u00e1rmi je jednou z hlavn\u00fdch pr\u00ed\u010din zranite\u013enost\u00ed kontajnerov.<\/li>\n
  2. Zlep\u0161ujte konfigur\u00e1ciu pomocou testov Center for Internet Security (CIS<\/a><\/noindex>), ktor\u00e9 s\u00fa dostupn\u00e9 pre Docker aj pre Kubernetes.<\/li>\n
  3. Ur\u010dite implementujte kontrolu pr\u00edstupu, zabezpe\u010dte rozdelenie povinnost\u00ed a zav\u00e1dzan\u00edm politiky spr\u00e1vy tajomstiev. D\u00f4vern\u00e9 inform\u00e1cie, ako s\u00fa k\u013e\u00fa\u010de Secure Sockets Layer (SSL) alebo poverenia datab\u00e1zy, s\u00fa \u0161ifrovan\u00e9 orchestr\u00e1torom alebo extern\u00fdmi slu\u017ebami spr\u00e1vy a poskytnut\u00e9 po\u010das behu<\/li>\n
  4. Vyhnite sa kontajnerom s privil\u00e9giami pomocou spr\u00e1vy bezpe\u010dnostn\u00fdch polit\u00edk, to zni\u017euje potenci\u00e1lne riziko hackerstva.<\/li>\n
  5. Pou\u017e\u00edvajte bezpe\u010dnostn\u00e9 n\u00e1stroje, ktor\u00e9 poskytuj\u00fa biele zoznamy, behavior\u00e1lne monitorovanie a detekciu anom\u00e1li\u00ed na prevenciu \u0161kodliv\u00fdch \u010dinnost\u00ed.<\/li>\n<\/ol>\n

    \nOdpor\u00fa\u010dania od StacxRox<\/a><\/noindex>:<\/p>\n

      \n
    1. Vyu\u017e\u00edvajte vstavan\u00e9 funkcie Kubernetes. Nastavte pr\u00edstup pre pou\u017e\u00edvate\u013eov pomocou rol\u00ed. Uistite sa, \u017ee neposkytujete zbyto\u010dn\u00e9 povolenia jednotliv\u00fdm subjektom, aj ke\u010f m\u00f4\u017ee trva\u0165 ur\u010dit\u00fd \u010das na premyslenie minim\u00e1lne potrebn\u00fdch povolen\u00ed. M\u00f4\u017ee sa zda\u0165 l\u00e1kav\u00e9 da\u0165 spr\u00e1vcovi klastra \u0161irok\u00e9 privil\u00e9gi\u00e1, preto\u017ee to \u0161etr\u00ed \u010das v po\u010diato\u010dnej f\u00e1ze. Av\u0161ak ak\u00fdko\u013evek kompromis alebo chyba v \u00fa\u010dte m\u00f4\u017ee ma\u0165 zni\u010duj\u00face n\u00e1sledky v bud\u00facnosti.\u00a0<\/li>\n
    2. Vyhnite sa duplicitn\u00e9mu ude\u013eovaniu pr\u00edstupov\u00fdch pr\u00e1v. Niekedy m\u00f4\u017ee by\u0165 u\u017eito\u010dn\u00e9, aby sa r\u00f4zne \u00falohy prekr\u00fdvali, ale to m\u00f4\u017ee vies\u0165 k probl\u00e9mom s prev\u00e1dzkou a vytvori\u0165 \"m\u0155tve z\u00f3ny\" pri odstra\u0148ovan\u00ed pr\u00edstupov\u00fdch pr\u00e1v. Okrem toho je d\u00f4le\u017eit\u00e9 odstra\u0148ova\u0165 nepou\u017e\u00edvan\u00e9 a neakt\u00edvne \u00falohy.<\/li>\n
    3. Nastavte sie\u0165ov\u00e9 politiky: izolujte moduly, aby ste obmedzili k nim pr\u00edstup; jasne povo\u013ete pr\u00edstup na internet t\u00fdm modulom, ktor\u00e9 to potrebuj\u00fa, pomocou \u0161t\u00edtkov; jasne povo\u013ete komunik\u00e1ciu medzi t\u00fdmi modulmi, ktor\u00e9 si potrebuj\u00fa navz\u00e1jom komunikova\u0165.\u00a0<\/li>\n<\/ol>\n

      <\/p>\n

      Ako usporiada\u0165 monitorovanie kontajnerov a slu\u017eieb v nich<\/h2>\n

      \nBezpe\u010dnos\u0165 a monitoring \u2014 hlavn\u00e9 probl\u00e9my spolo\u010dnost\u00ed<\/a><\/noindex> pri nasadzovan\u00ed klastrov Kubernetes. V\u00fdvoj\u00e1ri sa v\u017edy viac zameriavaj\u00fa na funkcie aplik\u00e1ci\u00ed, ktor\u00e9 vyv\u00edjaj\u00fa, ne\u017e na aspekty monitorovania t\u00fdchto aplik\u00e1ci\u00ed.<\/a><\/noindex>.\u00a0<\/p>\n

      Odpor\u00fa\u010dania od Gartner<\/a><\/noindex>:<\/p>\n

        \n
      1. Sna\u017ete sa monitorova\u0165 stav kontajnerov alebo slu\u017eieb v nich spolu s monitoringom hostite\u013esk\u00fdch syst\u00e9mov.<\/li>\n
      2. Uprednost\u0148ujte v\u00fdrobcov a n\u00e1stroje s hlbokou integr\u00e1ciou do orchestr\u00e1cie kontajnerov, najm\u00e4 Kubernetes.<\/li>\n
      3. Vyberte si n\u00e1stroje, ktor\u00e9 poskytuj\u00fa podrobn\u00e9 logovanie, automatick\u00e9 objavovanie slu\u017eieb a odpor\u00fa\u010dania v re\u00e1lnom \u010dase s pou\u017eit\u00edm analytiky a\/alebo strojov\u00e9ho u\u010denia.<\/li>\n<\/ol>\n

        \nV blogu SolarWinds odpor\u00fa\u010daj\u00fa<\/a><\/noindex>:<\/p>\n

          \n
        1. Pou\u017e\u00edva\u0165 n\u00e1stroje na automatick\u00e9 zistenie a sledovanie metriky kontajnera, korel\u00e1ciu metr\u00edk v\u00fdkonu, ako je procesor, pam\u00e4\u0165 a doba bezporuchovosti.<\/li>\n
        2. Zabezpe\u010dte optim\u00e1lne pl\u00e1novanie kapacity predpovedan\u00edm term\u00ednov vy\u010derpania kapacity na z\u00e1klade ukazovate\u013eov monitorovania kontajnerov.<\/li>\n
        3. Organizujte monitorovanie aplik\u00e1ci\u00ed umiestnen\u00fdch v kontajneroch pod\u013ea parametrov dostupnosti a v\u00fdkonu, \u010do je u\u017eito\u010dn\u00e9 ako na pl\u00e1novanie kapacity, tak na odstra\u0148ovanie probl\u00e9mov s v\u00fdkonom.<\/li>\n
        4. Automatizujte pracovn\u00e9 postupy, poskytovan\u00edm podpory riadenia a \u0161k\u00e1lovania pre kontajnery a ich prostredia nasadenia.<\/li>\n
        5. Automatizujte kontrolu pr\u00edstupu, aby ste sledovali datab\u00e1zu pou\u017e\u00edvate\u013eov, vyp\u00ednali zastaran\u00e9 a hostite\u013esk\u00e9 \u00fa\u010dty, odstra\u0148ovali zbyto\u010dn\u00e9 privil\u00e9gia.<\/li>\n
        6. Uistite sa, \u017ee v\u00e1\u0161 n\u00e1strojov\u00fd s\u00fabor dok\u00e1\u017ee sledova\u0165 tieto kontajnery a aplik\u00e1cie v r\u00f4znych prostrediach (s\u00fa\u010dasn\u00fdch, lok\u00e1lnych alebo hybridn\u00fdch) na vizualiz\u00e1ciu a porovn\u00e1vanie v\u00fdkonu v infrastruk\u0442\u0443\u0440e, sieti, syst\u00e9moch a aplik\u00e1ci\u00e1ch.<\/li>\n<\/ol>\n

          <\/p>\n

          Ako uchov\u00e1va\u0165 \u00fadaje a zabezpe\u010di\u0165 ich bezpe\u010dnos\u0165<\/h2>\n

          \nS narastaj\u00facim po\u010dtom pracovn\u00fdch kontajnerov so zachovan\u00edm stavu by mali z\u00e1kazn\u00edci zv\u00e1\u017ei\u0165 umiestnenie \u00fadajov mimo hostite\u013ea, ako aj potrebu chr\u00e1ni\u0165 tieto \u00fadaje.\u00a0<\/p>\n

          Pod\u013ea prieskumu Portworx a Aqua Security<\/a><\/noindex>, bezpe\u010dnos\u0165 \u00fadajov sa umiest\u0148uje na prvom mieste medzi bezpe\u010dnostn\u00fdmi probl\u00e9mami, ktor\u00e9 uviedlo v\u00e4\u010d\u0161ina respondentov (61%).\u00a0<\/p>\n

          \u0160ifrovanie \u00fadajov je z\u00e1kladnou bezpe\u010dnostnou strat\u00e9giou (64%), av\u0161ak respondenti tie\u017e vyu\u017e\u00edvaj\u00fa monitorovanie prev\u00e1dzky<\/p>\n

          (49%), skenovanie zranite\u013enost\u00ed v registroch (49%), skenovanie zranite\u013enost\u00ed v CI\/CD pipeline (49%) a blokovanie anom\u00e1li\u00ed prostredn\u00edctvom ochrany v re\u00e1lnom \u010dase (48%).<\/p>\n

          Odpor\u00fa\u010dania od Gartner<\/a><\/noindex>:<\/p>\n

            \n
          1. Vyberte si rie\u0161enia na uchov\u00e1vanie \u00fadajov, ktor\u00e9 s\u00fa postaven\u00e9 na princ\u00edpoch mikroslu\u017ebovej architekt\u00fary<\/a><\/noindex>. Je lep\u0161ie zvoli\u0165 tie, ktor\u00e9 sp\u013a\u0148aj\u00fa po\u017eiadavky na uchov\u00e1vanie \u00fadajov pre kontajnerov\u00e9 slu\u017eby, s\u00fa hardv\u00e9rovo nez\u00e1visl\u00e9, spravovan\u00e9 prostredn\u00edctvom API, maj\u00fa distribuovan\u00fa architekt\u00faru a podporuj\u00fa lok\u00e1lne a verejn\u00e9 nasadenia v cloude.<\/li>\n
          2. Vyhnite sa propriet\u00e1rnym pluginom a rozhran\u00edm. Vyberte si v\u00fdrobcov, ktor\u00ed poskytuj\u00fa integr\u00e1ciu s Kubernetes a podporuj\u00fa \u0161tandardn\u00e9 rozhrania, ako CSI (Container Storage Interfaces).<\/li>\n<\/ol>\n

            <\/p>\n

            Ako pracova\u0165 so sie\u0165ami<\/h2>\n

            \nTradi\u010dn\u00fd model podnikovej siete, kde odborn\u00edci na IT vytv\u00e1raj\u00fa sie\u0165ov\u00e9 prostredia pre v\u00fdvoj, testovanie, zabezpe\u010denie kvality a v\u00fdrobu pre ka\u017ed\u00fd projekt, sa nie v\u017edy dobre zhoduje s pracovn\u00fdm tokom nepretr\u017eit\u00e9ho v\u00fdvoja. Okrem toho sa kontajnerov\u00e9 siete t\u00fdkaj\u00fa viacer\u00fdch \u00farovn\u00ed.<\/p>\n

            V v blogu Magalix zhroma\u017edili<\/a><\/noindex> v\u0161eobecn\u00e9 pravidl\u00e1, ktor\u00fdm by mala zodpoveda\u0165 implement\u00e1cia klustrov\u00e9ho sie\u0165ov\u00e9ho rie\u0161enia:<\/p>\n

              \n
            1. Pod, ktor\u00e9 s\u00fa napl\u00e1novan\u00e9 na jednom a tom istom uzle, by mali ma\u0165 mo\u017enos\u0165 vymie\u0148a\u0165 si d\u00e1ta s ostatn\u00fdmi modulmi bez pou\u017eitia NAT (prekladu sie\u0165ov\u00fdch adries).<\/li>\n
            2. V\u0161etky syst\u00e9mov\u00e9 d\u00e9mony (procesy na pozad\u00ed, ako napr\u00edklad kubelet) be\u017eiace na konkr\u00e9tnom uzle m\u00f4\u017eu interagova\u0165 s podmi, ktor\u00e9 be\u017eia na tom istom uzle.<\/li>\n
            3. Pody, ktor\u00e9 pou\u017e\u00edvaj\u00fa hostite\u013esk\u00fa sie\u0165,<\/a><\/noindex> by mali by\u0165 schopn\u00e9 komunikova\u0165 so v\u0161etk\u00fdmi ostatn\u00fdmi podmi na v\u0161etk\u00fdch ostatn\u00fdch uzloch bez pou\u017eitia NAT. Upozor\u0148ujeme, \u017ee hostite\u013esk\u00e1 sie\u0165 je podporovan\u00e1 iba na Linuxov\u00fdch hostite\u013eoch.<\/li>\n<\/ol>\n

              \nSie\u0165ov\u00e9 rie\u0161enia by mali by\u0165 \u00fazko integrovan\u00e9 s primit\u00edvami a politikami Kubernetes. IT mana\u017e\u00e9ri by mali usilova\u0165 o vysok\u00fa \u00farove\u0148 automatiz\u00e1cie siete, poskytova\u0165 v\u00fdvoj\u00e1rom spr\u00e1vne n\u00e1stroje a dostato\u010dn\u00fa flexibilitu.<\/p>\n

              Odpor\u00fa\u010dania od Gartner<\/a><\/noindex>:<\/p>\n

                \n
              1. Zistite, \u010di v\u00e1\u0161 CaaS (kontajner ako slu\u017eba) alebo va\u0161a sie\u0165 SDN (Software Defined Network) podporuje Kubernetes siete. Ak nie, alebo ak je podpora nedostato\u010dn\u00e1, pou\u017eite pre svoje kontajnery sie\u0165ov\u00e9 rozhranie CNI (Container Network Interface), ktor\u00e9 podporuje potrebn\u00fa funk\u010dnos\u0165 a politiky.<\/li>\n
              2. Uistite sa, \u017ee v\u00e1\u0161 CaaS alebo PaaS (platforma ako slu\u017eba) podporuje vytv\u00e1ranie prich\u00e1dzaj\u00facich kontrol\u00f3rov a\/alebo vyva\u017eova\u010dov za\u0165a\u017eenia, ktor\u00e9 rozde\u013euj\u00fa prich\u00e1dzaj\u00faci tok medzi uzlami klastru. Ak tak\u00e1to mo\u017enos\u0165 neexistuje, zv\u00e1\u017ete pou\u017eitie extern\u00fdch proxy alebo mechanizmov service mesh.<\/li>\n
              3. Vy\u0161kolte svojich sie\u0165ov\u00fdch in\u017einierov na pr\u00e1cu so sie\u0165ami Linux a n\u00e1strojmi na automatiz\u00e1ciu siete, aby ste zn\u00ed\u017eili zru\u010dnostn\u00fd rozdiel a zv\u00fd\u0161ili flexibilitu.<\/li>\n<\/ol>\n

                <\/p>\n

                Ako spravova\u0165 \u017eivotn\u00fd cyklus aplik\u00e1ci\u00ed<\/h2>\n

                \nPre automatizovan\u00e9 a plynul\u00e9 doru\u010dovanie aplik\u00e1ci\u00ed je potrebn\u00e9 doplni\u0165 orchestr\u00e1ciu kontajnerov \u010fal\u0161\u00edmi n\u00e1strojmi automatiz\u00e1cie, ako s\u00fa produkty infra\u0161trukt\u00fary ako k\u00f3d (IaC). Patr\u00ed sem Chef, Puppet, Ansible a Terraform.\u00a0<\/p>\n

                Tie\u017e s\u00fa potrebn\u00e9 prostriedky na automatiz\u00e1ciu zostavenia a nasadenia aplik\u00e1ci\u00ed (pozri \"Magick\u00fd kvadrant pre orchestr\u00e1ciu vydania aplik\u00e1ci\u00ed<\/a><\/noindex>\"). Kontajnery tie\u017e poskytuj\u00fa mo\u017enosti pre \u0161k\u00e1lovanie, podobn\u00e9 mo\u017enostiam, ktor\u00e9 existovali pri nasadzovan\u00ed virtu\u00e1lnych strojov (VM). T\u00fdm p\u00e1dom by mali IT mana\u017e\u00e9ri ma\u0165 n\u00e1stroje na spr\u00e1vu \u017eivotn\u00e9ho cyklu kontajnerov<\/a><\/noindex>.<\/p>\n

                Odpor\u00fa\u010dania od Gartner<\/a><\/noindex>:<\/p>\n

                  \n
                1. Stanovte \u0161tandardy z\u00e1kladn\u00fdch obrazov kontajnerov z h\u013eadiska ve\u013ekosti, licencovania a flexibility na prid\u00e1vanie komponentov v\u00fdvoj\u00e1rmi.<\/li>\n
                2. Pou\u017e\u00edvajte syst\u00e9my na spr\u00e1vu konfigur\u00e1cie na riadenie \u017eivotn\u00e9ho cyklu kontajnerov, ktor\u00e9 uchov\u00e1vaj\u00fa konfigur\u00e1ciu v vrstv\u00e1ch na z\u00e1klade z\u00e1kladn\u00fdch obrazov nach\u00e1dzaj\u00facich sa v verejn\u00fdch alebo s\u00fakromn\u00fdch repozit\u00e1roch.<\/li>\n
                3. Integrujte platformu CaaS s automatiza\u010dn\u00fdmi n\u00e1strojmi na automatiz\u00e1ciu cel\u00e9ho pracovn\u00e9ho procesu aplik\u00e1cie.<\/li>\n<\/ol>\n

                  <\/p>\n

                  Ako spravova\u0165 kontajnery pomocou orchestr\u00e1torov<\/h2>\n

                  \nZ\u00e1kladn\u00e9 funkcie na nasadenie kontajnerov s\u00fa poskytovan\u00e9 na \u00farovniach orchesterovania a pl\u00e1novania. Pri pl\u00e1novan\u00ed s\u00fa kontajnery umiestnen\u00e9 na najoptim\u00e1lnej\u0161\u00edch hostite\u013eoch v klastre, ako stanovuj\u00fa po\u017eiadavky \u00farovne orchesterovania.\u00a0<\/p>\n

                  Kubernetes sa de facto stal \u0161tandardom orchestr\u00e1cie kontajnerov s akt\u00edvnou komunitou, ktor\u00fa podporuje v\u00e4\u010d\u0161ina popredn\u00fdch komer\u010dn\u00fdch poskytovate\u013eov.\u00a0<\/p>\n

                  Odpor\u00fa\u010dania od Gartner<\/a><\/noindex>:<\/p>\n

                    \n
                  1. Definujte z\u00e1kladn\u00e9 po\u017eiadavky na prvky spr\u00e1vy bezpe\u010dnosti, monitorovanie, spr\u00e1vu polit\u00edk, uchov\u00e1vanie \u00fadajov, spr\u00e1vu siet\u00ed a \u017eivotn\u00fd cyklus kontajnerov.<\/li>\n
                  2. Na z\u00e1klade t\u00fdchto po\u017eiadaviek vyberte n\u00e1stroj, ktor\u00fd najlep\u0161ie vyhovuje va\u0161im potreb\u00e1m a scen\u00e1rom pou\u017eitia.<\/li>\n
                  3. Vyu\u017eite v\u00fdskumy Gartner (pozri \u201eAko zvoli\u0165 model nasadenia Kubernetes<\/a><\/noindex>\u201c), aby ste pochopili v\u00fdhody a nev\u00fdhody r\u00f4znych modelov nasadenia Kubernetes a vybrali ten najvhodnej\u0161\u00ed pre va\u0161u \u00falohu.<\/li>\n
                  4. Vyberte poskytovate\u013ea, ktor\u00fd m\u00f4\u017ee zabezpe\u010di\u0165 hybridn\u00e9 orchesterovanie pracovn\u00fdch kontajnerov v r\u00f4znych prostrediach s tesnou integr\u00e1ciou s backendmi, spolo\u010dn\u00fdmi pl\u00e1nmi spr\u00e1vy a konzistentn\u00fdmi modelmi cenotvorby.<\/li>\n<\/ol>\n

                    <\/p>\n

                    Ako vyu\u017ei\u0165 kapacity poskytovate\u013eov cloudu<\/h2>\n

                    \nV Gartneri sa pova\u017euje<\/a><\/noindex>, \u017ee z\u00e1ujem o nasadenie kontajnerov v verejnom cloude IaaS rastie kv\u00f4li dostupnosti hotov\u00fdch pon\u00fak CaaS a tie\u017e tesnej integr\u00e1cii t\u00fdchto pon\u00fak s in\u00fdmi produktmi, ktor\u00e9 pon\u00fakaj\u00fa poskytovatelia cloudu.<\/p>\n

                    Cloude IaaS pon\u00fakaj\u00fa konzum\u00e1ciu zdrojov na po\u017eiadanie, r\u00fdchlu \u0161k\u00e1lovate\u013enos\u0165 a spr\u00e1vu slu\u017eieb<\/a><\/noindex>, ktor\u00e1 pom\u00e1ha vyhn\u00fa\u0165 sa potrebe hlbok\u00fdch znalost\u00ed o infra\u0161trukt\u00fare a jej \u00fadr\u017ebe. V\u00e4\u010d\u0161ina poskytovate\u013eov cloudu pon\u00faka slu\u017ebu spr\u00e1vy kontajnerov a niektor\u00ed pon\u00fakaj\u00fa nieko\u013eko mo\u017enost\u00ed orchestr\u00e1cie.\u00a0<\/p>\n

                    K\u013e\u00fa\u010dov\u00ed poskytovatelia spravovan\u00fdch cloudov\u00fdch slu\u017eieb s\u00fa uveden\u00ed v tabu\u013eke:\u00a0<\/p>\n

                    Cloudov\u00fd poskytovate\u013e<\/strong>
                    \nTyp slu\u017eieb<\/strong>
                    \nProdukt\/slu\u017eba<\/strong><\/p>\n

                    Alibaba
                    \nNative Cloud Service
                    \nAlibaba Cloud Container Service, Alibaba Cloud Container Service for Kubernetes<\/p>\n

                    Amazon Web Services (AWS)
                    \nNative Cloud Service
                    \nAmazon Elastic Container Services (ECS), Amazon ECS for Kubernetes (EKS), AWS Fargate<\/p>\n

                    Giant Swarm
                    \nMSP
                    \nGiant Swarm Managed Kubernetes Infrastructure<\/p>\n

                    Google
                    \nNative Cloud Service
                    \nGoogle Container Engine (GKE)<\/p>\n

                    IBM
                    \nNative Cloud Service
                    \nIBM Cloud Kubernetes Service<\/p>\n

                    Microsoft
                    \nNative Cloud Service
                    \nAzure Kubernetes Service, Azure Service Fabric<\/p>\n

                    Oracle
                    \nNative Cloud Service
                    \nOCI Container Engine for Kubernetes<\/p>\n

                    Platform9
                    \nMSP
                    \nManaged Kubernetes<\/p>\n

                    Red Hat
                    \nHosted Service
                    \nOpenShift Dedicated & Online<\/p>\n

                    VMware
                    \nHosted Service
                    \nCloud PKS (Beta)<\/p>\n

                    Mail.ru Cloud Solutions*
                    \nNative Cloud Service
                    \nMail.ru Cloud Containers<\/p>\n

                    \n* Nebudeme skr\u00fdva\u0165, my sme sa tu sami pridali pri preklade \ud83d\ude42<\/p>\n

                    Poskytovatelia verejn\u00fdch cloudov tie\u017e prid\u00e1vaj\u00fa nov\u00e9 funkcie a vyd\u00e1vaj\u00fa lok\u00e1lne produkty. V najbli\u017e\u0161ej bud\u00facnosti bud\u00fa poskytovatelia cloudov rozv\u00edja\u0165 podporu hybridn\u00fdch cloudov a multi-cloudov\u00fdch prostred\u00ed.\u00a0<\/p>\n

                    Odpor\u00fa\u010dania Gartner<\/a><\/noindex>:<\/strong><\/p>\n

                      \n
                    1. Objekt\u00edvne zhodno\u0165te mo\u017enosti va\u0161ej organiz\u00e1cie nasadzova\u0165 a spravova\u0165 relevantn\u00e9 n\u00e1stroje a zv\u00e1\u017ete alternat\u00edvne slu\u017eby na spr\u00e1vu cloudov\u00fdch kontajnerov.<\/li>\n
                    2. D\u00f4kladne vyberajte softv\u00e9r, pou\u017e\u00edvajte open source tam, kde je to mo\u017en\u00e9.<\/li>\n
                    3. Vyberajte poskytovate\u013eov s jednotn\u00fdmi opera\u010dn\u00fdmi modelmi v hybridn\u00fdch prostrediach, ktor\u00ed pon\u00fakaj\u00fa spr\u00e1vu zjednoten\u00fdch klastrov z jednej konzoly a tie\u017e poskytovate\u013eov, ktor\u00ed u\u013eah\u010duj\u00fa samostatn\u00e9 vyu\u017e\u00edvanie IaaS.<\/li>\n<\/ol>\n

                      \nNieko\u013eko tipov na v\u00fdber poskytovate\u013ea Kubernetes aaS z blogu Replex<\/a><\/noindex>:<\/p>\n

                        \n
                      1. H\u013eadajte distrib\u00facie, ktor\u00e9 podporuj\u00fa vysok\u00fa dostupnos\u0165 priamo z krabice. To zah\u0155\u0148a podporu viacer\u00fdch z\u00e1kladn\u00fdch architekt\u00far, vysoko dostupn\u00e9 komponenty etcd a tie\u017e z\u00e1lohovanie a obnovu.<\/li>\n
                      2. Aby ste zabezpe\u010dili mobilitu prostred\u00ed Kubernetes, je lep\u0161ie vybera\u0165 cloudov\u00fdch poskytovate\u013eov, ktor\u00ed podporuj\u00fa \u0161irok\u00e9 spektrum modelov nasadenia: od lok\u00e1lnych cez hybridn\u00e9 po multi-cloudov\u00e9.\u00a0<\/li>\n
                      3. Ponuky poskytovate\u013eov tie\u017e stoj\u00ed za to hodnoti\u0165 s oh\u013eadom na jednoduchos\u0165 nastavenia, in\u0161tal\u00e1cie a vytvorenia klastru, ako aj aktualiz\u00e1ci\u00ed, monitorovania a odstra\u0148ovania probl\u00e9mov. Z\u00e1kladnou po\u017eiadavkou je podpora plne automatizovan\u00fdch aktualiz\u00e1ci\u00ed klastru s nulov\u00fdm \u010dasom v\u00fdpadku. Vybran\u00e9 rie\u0161enie by malo umo\u017eni\u0165 aj manu\u00e1lne spustenie aktualiz\u00e1ci\u00ed.\u00a0<\/li>\n
                      4. Spr\u00e1va identity a pr\u00edstupu je d\u00f4le\u017eit\u00e1 z h\u013eadiska bezpe\u010dnosti aj spr\u00e1vy. Uistite sa, \u017ee vybran\u00fd Kubernetes distrib\u00facia podporuje integr\u00e1ciu s autentifika\u010dn\u00fdmi a autoriza\u010dn\u00fdmi prostriedkami, ktor\u00e9 sa pou\u017e\u00edvaj\u00fa vo vn\u00fatri spolo\u010dnosti. RBAC a podrobn\u00e1 kontrola pr\u00edstupu s\u00fa tie\u017e d\u00f4le\u017eit\u00fdmi funkciami.<\/li>\n
                      5. Vybran\u00fd distrib\u00facia by mala ma\u0165 vlastn\u00e9 sie\u0165ov\u00e9 rie\u0161enie, definovan\u00e9 softv\u00e9rom a pokr\u00fdvaj\u00face \u0161irok\u00e9 spektrum po\u017eiadaviek, ktor\u00e9 klad\u00fa r\u00f4zne aplik\u00e1cie alebo infra\u0161trukt\u00fara, alebo by mala podporova\u0165 jednu z popul\u00e1rnych implement\u00e1ci\u00ed siet\u00ed zalo\u017een\u00fdch na CNI, vr\u00e1tane Flannel, Calico, kube-router alebo OVN.<\/li>\n<\/ol>\n

                        \nZav\u00e1dzanie kontajnerov do v\u00fdroby sa st\u00e1va hlavn\u00fdm trendom, \u010do dokazuj\u00fa v\u00fdsledky prieskumu, ktor\u00fd bol uskuto\u010dnen\u00fd na sesi\u00e1ch Gartner<\/a><\/noindex> o infra\u0161trukt\u00fare, oper\u00e1ci\u00e1ch a cloudov\u00fdch strat\u00e9gi\u00e1ch (IOCS) v decembri 2018:<\/p>\n

                        \"Najlep\u0161ie
                        \nAko vid\u00edme, 27% respondentov u\u017e pou\u017e\u00edva kontajnery v praxi, zatia\u013e \u010do 63% pl\u00e1nuje ich zavies\u0165.<\/p>\n

                        V v prieskume Portworx a Aqua Security<\/a><\/noindex> 24% respondentov uviedlo, \u017ee investuj\u00fa viac ako pol mili\u00f3na dol\u00e1rov ro\u010dne do kontajnerov\u00fdch technol\u00f3gi\u00ed, a 17% respondentov m\u00ed\u0148a na tieto technol\u00f3gie viac ako mili\u00f3n dol\u00e1rov ro\u010dne.\u00a0<\/p>\n

                        \u010cl\u00e1nok pripravil t\u00edm cloudovej platformy <\/i>Mail.ru Cloud Solutions<\/i><\/a><\/noindex>.<\/i><\/p>\n

                        \u010co \u010fal\u0161ie si pre\u010d\u00edta\u0165 na t\u00fato t\u00e9mu<\/strong>:<\/p>\n

                          \n
                        1. Najlep\u0161ie praktiky DevOps: spr\u00e1va DORA<\/a><\/noindex>.<\/li>\n
                        2. Kubernetes v duchu pir\u00e1tstva s \u0161abl\u00f3nou na zavedenie<\/a><\/noindex>.<\/li>\n
                        3. 25 u\u017eito\u010dn\u00fdch n\u00e1strojov pre nasadenie a implement\u00e1ciu Kubernetes<\/a><\/noindex>.<\/li>\n<\/ol>\n

                          Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

                          \u042d\u043a\u043e\u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0438\u0437\u0430\u0446\u0438\u0438 \u0431\u044b\u0441\u0442\u0440\u043e \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u0438 \u043c\u0435\u043d\u044f\u0435\u0442\u0441\u044f, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0432 \u044d\u0442\u043e\u0439 \u0441\u0444\u0435\u0440\u0435 \u043d\u0435 \u0445\u0432\u0430\u0442\u0430\u0435\u0442 \u0445\u043e\u0440\u043e\u0448\u0438\u0445 \u0440\u0430\u0431\u043e\u0447\u0438\u0445 \u043f\u0440\u0430\u043a\u0442\u0438\u043a. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435 Kubernetes \u0438 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 \u0432\u0441\u0435 \u0447\u0430\u0449\u0435 \u2014 \u043a\u0430\u043a \u0434\u043b\u044f \u043c\u043e\u0434\u0435\u0440\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441\u0442\u0430\u0440\u044b\u0445 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u0442\u0430\u043a \u0438 \u0434\u043b\u044f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0441\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0445 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439.\u00a0 \u041a\u043e\u043c\u0430\u043d\u0434\u0430 Kubernetes aaS \u043e\u0442 Mail.ru \u0441\u043e\u0431\u0440\u0430\u043b\u0430 \u043f\u0440\u043e\u0433\u043d\u043e\u0437\u044b, \u0441\u043e\u0432\u0435\u0442\u044b \u0438 \u043b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 \u0434\u043b\u044f \u043b\u0438\u0434\u0435\u0440\u043e\u0432 \u0440\u044b\u043d\u043a\u0430 \u043e\u0442 Gartner, 451 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":78374,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-78373","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\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\udd47Najlep\u0161ie praktiky a odpor\u00fa\u010dania pre sp\u00fa\u0161\u0165anie kontajnerov a Kubernetes v produk\u010dn\u00fdch prostrediach | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-i-rekomendaczii-dlya-zapuska-kontejnerov-i-kubernetes-v-proizvodstvennyh-sredah","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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 \u0438 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0430\u0446\u0438\u0438 \u0434\u043b\u044f \u0437\u0430\u043f\u0443\u0441\u043a\u0430 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u0438 Kubernetes \u0432 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0445 \u0441\u0440\u0435\u0434\u0430\u0445 | ProHoster","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-praktiki-i-rekomendaczii-dlya-zapuska-kontejnerov-i-kubernetes-v-proizvodstvennyh-sredah","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-04-18T23:42:20+00:00","article:modified_time":"2020-04-18T23:42:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"78373","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:59:34","updated":"2022-10-07 00:18:57","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/78373","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=78373"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/78373\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/78374"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=78373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=78373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=78373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}