{"id":37204,"date":"2019-10-31T22:16:20","date_gmt":"2019-10-31T19:16:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4\/"},"modified":"2019-10-31T22:16:20","modified_gmt":"2019-10-31T19:16:20","slug":"uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","title":{"rendered":"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Ofici\u00e1lny \u0161tart platformy Red Hat OpenShift 4 sa uskuto\u010dnil. Dnes v\u00e1m povieme, ako prejs\u0165 na \u0148u z OpenShift Container Platform 3 \u010do najr\u00fdchlej\u0161ie a najjednoduch\u0161ie.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/f7411df89b507a9a7e5825c1b5d3fbf5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV r\u00e1mci tohto \u010dl\u00e1nku n\u00e1s predov\u0161etk\u00fdm zauj\u00edmaj\u00fa nov\u00e9 klastre OpenShift 4, ktor\u00e9 vyu\u017e\u00edvaj\u00fa mo\u017enosti inteligentnej a nemennej (immutable \u2013 rovnak\u00e9 pre v\u0161etky prostredia nasadenia) infra\u0161trukt\u00fary zalo\u017eenej na RHEL CoreOS a automatiza\u010dn\u00fdch n\u00e1strojov. Ni\u017e\u0161ie uk\u00e1\u017eeme, ako prejs\u0165 na OpenShift 4 bez zbyto\u010dn\u00fdch probl\u00e9mov.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nViac inform\u00e1ci\u00ed o rozdieloch medzi novou a starou verziou n\u00e1jdete <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/blog.openshift.com\/openshift-commons-briefing-openshift-4-0-release-update-with-ali-mobreem\/&amp;sa=D&amp;ust=1562087733741000\">tu<\/a><\/noindex>.<\/p>\n<h3>Migr\u00e1cia klastrov z OpenShift 3 na OpenShift 4 s vyu\u017eit\u00edm certifikovanej platformy Red Hat Appranix<\/h3>\n<p>\nAppranix a Red Hat \u00fazko spolupracovali na zjednodu\u0161en\u00ed migr\u00e1cie klastrov\u00fdch zdrojov z OpenShift 3 na OpenShift 4 pomocou \u0161peci\u00e1lnej slu\u017eby, ktor\u00e1 funguje na vrchu Appranix Site Reliability Automation pre Kubernetes.<\/p>\n<p>Rie\u0161enie Appranix (n\u00e1jdete ho v <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/access.redhat.com\/containers\/?tab%3Dimages%23\/registry.connect.redhat.com\/appranix\/apx-manager&amp;sa=D&amp;ust=1562087733743000\">Red Hat Container Catalog<\/a><\/noindex>) umo\u017e\u0148uje vytv\u00e1ra\u0165 z\u00e1lohy v\u0161etk\u00fdch klastrov OpenShift 3 a obnovi\u0165 ich na OpenShift 4 len za nieko\u013eko kliknut\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/5ed42cbbe2cead8c793b4c9fc69ccb0e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Ak\u00e9 s\u00fa v\u00fdhody migr\u00e1cie s Appranix pre OpenShift 4<\/h3>\n<p><\/p>\n<ul>\n<li>R\u00fdchly \u0161tart. Ke\u010f\u017ee rie\u0161enie Appranix je postaven\u00e9 na z\u00e1sade SaaS, nie je potrebn\u00e9 nastavova\u0165 \u017eiadnu infra\u0161trukt\u00faru ani konfigurova\u0165 \u010di pou\u017e\u00edva\u0165 samostatn\u00e9 \u0161pecializovan\u00e9 rie\u0161enia na migr\u00e1ciu.<\/li>\n<li>\u0160k\u00e1lovate\u013enos\u0165 Appranix u\u013eah\u010duje migr\u00e1ciu ve\u013ek\u00fdch klastrov.<\/li>\n<li>Automatick\u00e1 z\u00e1loha zlo\u017eit\u00fdch klastrov\u00fdch konfigur\u00e1ci\u00ed OpenShift 3 s n\u00e1sledn\u00fdm pren\u00e1\u0161an\u00edm na OpenShift 4 u\u013eah\u010duje samotn\u00fd proces migr\u00e1cie.<\/li>\n<li>Mo\u017enos\u0165 otestova\u0165, ako sa aplik\u00e1cie z firemnej infra\u0161trukt\u00fary OpenShift 3 spr\u00e1vaj\u00fa na platforme OpenShift 4 v cloude AWS.<\/li>\n<li>Migr\u00e1cia RBAC nastaven\u00ed pr\u00edstupu spolu so zdrojmi klastra.<\/li>\n<li>Selekt\u00edvna alebo \u00fapln\u00e1 migr\u00e1cia v\u0161etk\u00fdch projektov na nov\u00e9 klastre OpenShift 4.<\/li>\n<li>Volite\u013ene \u2013 organiz\u00e1cia nieko\u013ek\u00fdch \u00farovn\u00ed odolnosti vo\u010di v\u00fdpadkom pre kontajnerov\u00e9 aplik\u00e1cie pri platnej predplatnej slu\u017ebe.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/efea466d37f85d204ff868ceb2eddfca.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Viac\u00farov\u0148ov\u00e1 odolnos\u0165 (resiliency) pre aplik\u00e1cie OpenShift<\/h3>\n<p>\nPo migr\u00e1cii z 3. na 4. verziu OpenShift m\u00f4\u017ee by\u0165 rie\u0161enie Appranix pou\u017eit\u00e9 na zabezpe\u010denie kontinu\u00e1lnej odolnosti aplik\u00e1ci\u00ed (Continuous App Resilience), pri ktorej s\u00fa mo\u017en\u00e9 tri varianty. <b>\u00darove\u0148 1<\/b> odolnos\u0165 (Level 1 Resiliency) umo\u017e\u0148uje obnovenie aplik\u00e1ci\u00ed bez zmeny regi\u00f3nu a cloudov\u00e9ho poskytovate\u013ea. M\u00f4\u017ee sa pou\u017ei\u0165 na vr\u00e1tenie aplik\u00e1ci\u00ed sp\u00e4\u0165 alebo na obnovenie po miestnom zlyhan\u00ed na \u00farovni regi\u00f3nu, napr\u00edklad v pr\u00edpade ne\u00faspe\u0161n\u00e9ho nasadenia aplik\u00e1cie, alebo v situ\u00e1cii, kde je potrebn\u00e9 r\u00fdchlo vytvori\u0165 testovacie prostredie v tom istom regi\u00f3ne, ale v samostatnom klastri OpenShift.<\/p>\n<p><b>\u00darove\u0148 2<\/b> umo\u017e\u0148uje prenies\u0165 aplik\u00e1cie do in\u00e9ho regi\u00f3nu bez zmeny poskytovate\u013ea. Pri tom je mo\u017en\u00e9 zachova\u0165 hlavn\u00fa (primary) infra\u0161trukt\u00faru d\u00e1t v prim\u00e1rnom regi\u00f3ne, ale sp\u00fa\u0161\u0165a\u0165 aplik\u00e1cie v inom klastri v inom regi\u00f3ne. T\u00e1to mo\u017enos\u0165 je u\u017eito\u010dn\u00e1, ke\u010f zlyh\u00e1 cloudov\u00fd regi\u00f3n alebo z\u00f3na, alebo je potrebn\u00e9 presun\u00fa\u0165 aplik\u00e1cie do in\u00e9ho regi\u00f3nu kv\u00f4li kybernetick\u00e9mu \u00fatoku. A nakoniec, <b>\u00darove\u0148 3<\/b> umo\u017e\u0148uje meni\u0165 nielen regi\u00f3n, ale aj cloudov\u00e9ho poskytovate\u013ea.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/b336f68bb81ad007025e1a10e9b83a59.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><b>Ako funguje Appranix SRA<\/b><br \/>\nViac\u00farov\u0148ov\u00e1 odolnos\u0165 aplik\u00e1ci\u00ed OpenShift v Appranix sa dosahuje v\u010faka funk\u010dnosti \u201e\u010dasovej ma\u0161iny\u201c, ktor\u00e1 automaticky vytv\u00e1ra k\u00f3pie prostredia aplik\u00e1ci\u00ed. Na aktiv\u00e1ciu tejto funk\u010dnosti a zv\u00fd\u0161enie zabezpe\u010denia aplik\u00e1ci\u00ed sta\u010d\u00ed prida\u0165 do DevOps pipeline iba jeden riadok k\u00f3du.<br \/>\nV infra\u0161trukt\u00farnych slu\u017eb\u00e1ch cloudov\u00fdch poskytovate\u013eov sa tie\u017e vyskytuj\u00fa probl\u00e9my, preto je mo\u017enos\u0165 r\u00fdchlo prepn\u00fa\u0165 sa na in\u00e9ho poskytovate\u013ea u\u017eito\u010dn\u00e1, aby sa predi\u0161lo z\u00e1vislosti od jedin\u00e9ho dod\u00e1vate\u013ea slu\u017eieb.<\/p>\n<p><b>Ako je zn\u00e1zornen\u00e9 na obr\u00e1zku ni\u017e\u0161ie<\/b>, z\u00e1lohy prostredia aplik\u00e1ci\u00ed m\u00f4\u017eu by\u0165 v Appranix vytv\u00e1ran\u00e9 nielen automaticky s nastavenou periodicitou, ale aj na po\u017eiadanie z pipeline nepretr\u017eitej integr\u00e1cie a dod\u00e1vky CI\/CD. Pri tom \u201e\u010dasov\u00e1 ma\u0161ina\u201c zabezpe\u010duje:<\/p>\n<ul>\n<li>Inkrement\u00e1lne, typu GitHub, zaznamen\u00e1vanie priestorov a prostred\u00ed aplik\u00e1ci\u00ed.<\/li>\n<li>Jednoduch\u00e9 vr\u00e1tenie aplik\u00e1ci\u00ed.<\/li>\n<li>Spr\u00e1va verzi\u00ed konfigur\u00e1ci\u00ed cloudov\u00fdch prostred\u00ed a kontajnerov.<\/li>\n<li>Automatizovan\u00e9 riadenie \u017eivotn\u00fdm cyklom d\u00e1t.<\/li>\n<li>Automatizovanie spr\u00e1vy infra\u0161trukt\u00fary ako k\u00f3du (IaC).<\/li>\n<li>Automatizovan\u00e9 riadenie stavov IaC.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/f22fdab2ecf9535511f203bebae3d647.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>S pomocou Appranix m\u00f4\u017eete organizova\u0165 ochranu a obnovenie na \u00farovni aplik\u00e1ci\u00ed celkom pre tak\u00e9 scen\u00e1re, ako s\u00fa chaos engineering, havarijn\u00e9 obnovenie, ochrana pred ransomware a zabezpe\u010denie kontinuity obchodn\u00fdch procesov. Nebudeme sa na tom podrobne zastavova\u0165 a nesk\u00f4r sa pozrieme, ako pou\u017ei\u0165 Appranix na migr\u00e1ciu z OpenShift 3 na OpenShift 4.<\/p>\n<h3>Ako prebieha migr\u00e1cia OpenShift 3 na OpenShift 4 s pou\u017eit\u00edm Appranix Site Reliability Platform<\/h3>\n<p>\nProces zah\u0155\u0148a tri f\u00e1zy:<\/p>\n<ol>\n<li>Nastavujeme OpenShift 3 a OpenShift 4 pre automatick\u00e9 objavovanie v\u0161etk\u00fdch komponentov, ktor\u00e9 sa maj\u00fa prenies\u0165.<\/li>\n<li>Vytv\u00e1rame politiky a ur\u010den\u00e9 priestory mien pre migr\u00e1ciu.<\/li>\n<li>Obnovujeme v\u0161etky priestory mien na OpenShift 4 na jeden klik.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/005a7d892f21324a57b13e57ad0fd474.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Nastavujeme clustre OpenShift 3 a 4 pre automatick\u00e9 objavovanie<\/h3>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/6913f438b885652cc1e99314f2a90e6a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix predpoklad\u00e1, \u017ee u\u017e m\u00e1te funk\u010dn\u00e9 clustre OpenShift 3 a OpenShift 4. Ak clustre OpenShift 4 zatia\u013e nem\u00e1te, vytvorte ich pod\u013ea <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/blog.openshift.com\/installing-openshift-4-from-start-to-finish\/&amp;sa=D&amp;ust=1562087733749000\">dokument\u00e1cie Red Hat k nasadeniu OpenShift 4<\/a><\/noindex>. Nastavenie prim\u00e1rneho a cie\u013eov\u00e9ho klastru v Appranix sa vykon\u00e1va rovnako a zah\u0155\u0148a iba nieko\u013eko krokov.<\/p>\n<h3>In\u0161talujeme Appranix Controller Agent na objavovanie klastrov<\/h3>\n<p>\nNa objavovanie klastrov\u00fdch zdrojov je potrebn\u00fd mal\u00fd agent sidecar-kontrol\u00f3ra. Na jeho nasadenie sta\u010d\u00ed skop\u00edrova\u0165 a vlo\u017ei\u0165 pr\u00edslu\u0161n\u00fd pr\u00edkaz curl, <b>ako je zn\u00e1zornen\u00e9 ni\u017e\u0161ie<\/b>. Po tom, \u010do bude agent nain\u0161talovan\u00fd v OpenShift 3 a v OpenShift 4, Appranix automaticky objav\u00ed v\u0161etky klastrov\u00e9 zdroje, ktor\u00e9 sa maj\u00fa migrova\u0165, vr\u00e1tane priestorov mien, nasaden\u00ed, pod-ov, slu\u017eieb, ako aj hostite\u013eov s in\u00fdmi zdrojmi.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/20caf8a39d0c99a6ff86d3f53b1cffbf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Migr\u00e1cia ve\u013ek\u00fdch distribuovan\u00fdch aplik\u00e1ci\u00ed<br \/>\nTeraz si na pr\u00edklade uk\u00e1\u017eeme, ako bez zbyto\u010dn\u00e9ho \u00fasilia prenies\u0165 z OpenShift 3 na OpenShift 4 distribuovan\u00fa mikroslu\u017ebov\u00fa aplik\u00e1ciu SockShop (odkaz \u2013 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/github.com\/microservices-demo&amp;sa=D&amp;ust=1562087733751000\">podrobn\u00e9 op\u00edsanie tejto aplik\u00e1cie a jej mikroslu\u017eobnej architekt\u00fary<\/a><\/noindex>). Ako je vidie\u0165 z <b>obr\u00e1zku ni\u017e\u0161ie<\/b>, architekt\u00fara SockShop obsahuje mno\u017estvo komponentov.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/6c9e65a9cd23869175aa736e03c71798.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix objavuje v\u0161etky zdroje, pre ktor\u00e9 je potrebn\u00e9 zabezpe\u010di\u0165 ochranu a migr\u00e1ciu na OpenShift 4, vr\u00e1tane pod-ov, nasaden\u00ed, slu\u017eieb a klastrov\u00fdch konfigur\u00e1ci\u00ed.<\/p>\n<h3>OpenShift 3 s funguj\u00facou aplik\u00e1ciou SockShop<\/h3>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/5340aacbea58e3d80d73a3b581f9ef08.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/eeb107cb553ccfd1f5bffbfb4e745acf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Vytv\u00e1rame politiky Protection Policies pre migr\u00e1ciu<\/h3>\n<p>\nPolitiky je mo\u017en\u00e9 nastavova\u0165 flexibilne v z\u00e1vislosti od toho, ako sa m\u00e1 migr\u00e1cia uskuto\u010dni\u0165. Napr\u00edklad na z\u00e1klade nieko\u013ek\u00fdch krit\u00e9ri\u00ed alebo z\u00e1lohy raz za hodinu.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/7c62333127d08fe469222562146df10b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Realizujeme migr\u00e1ciu viacer\u00fdch klastrov OpenShift 3 pomocou pl\u00e1nov ochrany (Protection Plans)<\/h3>\n<p>\nV z\u00e1vislosti od \u0161pecif\u00edk aplik\u00e1cie alebo menn\u00e9ho priestoru je mo\u017en\u00e9 na klastre OpenShift 3 aplikova\u0165 politiky, ktor\u00e9 sa vykon\u00e1vaj\u00fa raz za hodinu, raz za t\u00fd\u017ede\u0148 alebo dokonca raz za mesiac.<\/p>\n<p>Appranix umo\u017e\u0148uje presun\u00fa\u0165 na OpenShift 4 v\u0161etky menn\u00e9 priestory klastru alebo iba vybran\u00e9 priestory.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/e1acfff015e8d6b57d316c2a21bb5cea.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Realizujeme migr\u00e1ciu na OpenShift 4 jedn\u00fdm kliknut\u00edm<\/h3>\n<p>\nMigr\u00e1cia znamen\u00e1 obnovenie vybran\u00fdch menn\u00fdch priestorov na cie\u013eovom klastru OpenShift 4. T\u00e1to oper\u00e1cia sa vykon\u00e1va jedn\u00fdm kliknut\u00edm. Appranix s\u00e1m vykon\u00e1va v\u0161etku pr\u00e1cu oh\u013eadom zhroma\u017edenia \u00fadajov o konfigur\u00e1cii a zdrojoch p\u00f4vodn\u00e9ho prostredia a potom samo\u010dinne obnovuje na platforme OpenShift 4.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/a6de0780bbcd4fb05663ca48f0da58ee.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/d32618d1dbeb74a96af1b8fce362352e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Kontrolujeme aplik\u00e1cie po migr\u00e1cii na OpenShift 4<\/h3>\n<p>\nPrihl\u00e1ste sa do klastru OpenShift 4, aktualizujte projekty a skontrolujte, \u010di s\u00fa v\u0161etky aplik\u00e1cie a menn\u00e9 priestory v poriadku. Opakujte proces migr\u00e1cie pre \u010fal\u0161ie menn\u00e9 priestory vytvoren\u00edm nov\u00fdch pl\u00e1nov Protection Plans alebo modifikovan\u00edm u\u017e existuj\u00facich.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/0819a06d267a406c6f0bc98d458456a8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Sp\u00fa\u0161\u0165ame migrovan\u00e9 aplik\u00e1cie na OpenShift 4<\/h3>\n<p>\nPo migr\u00e1cii aplik\u00e1ci\u00ed pomocou obnovovacej proced\u00fary Appranix je d\u00f4le\u017eit\u00e9 nezabudn\u00fa\u0165 nastavi\u0165 trasy \u2013 tie musia smerova\u0165 na OpenShift 4. Mo\u017eno, \u017ee pred \u00fapln\u00fdm presunom produkcie z OpenShift 3 by ste chceli uskuto\u010dni\u0165 testov\u00fa obnovu. Ke\u010f na OpenShift 4 bude nieko\u013eko funk\u010dn\u00fdch aplik\u00e1ci\u00ed v pr\u00edslu\u0161n\u00fdch menn\u00fdch priestoroch, vznikne potreba presun\u00fa\u0165 aj ostatn\u00e9 aplik\u00e1cie pomocou tohto procesu.<\/p>\n<p>Po presune v\u0161etk\u00fdch menn\u00fdch priestorov budete m\u00f4c\u0165 chr\u00e1ni\u0165 v\u0161etky klastry OpenShift pre kontinu\u00e1lne havarijn\u00e9 obnovenie, ochranu pred ransomware, zabezpe\u010denie kontinuity biznis procesov alebo na n\u00e1sledn\u00fa migr\u00e1ciu, preto\u017ee Appranix Site Reliability Automation sa automaticky aktualizuje s nov\u00fdmi verziami OpenShift.<\/p>\n<p><img decoding=\"async\" alt=\"U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/c5e2cd72465d7ba096ab225bff1e3c42.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Spolu<\/h3>\n<p>\nOpenShift 4 je v\u00fdznamn\u00fd krok vpred, predov\u0161etk\u00fdm v\u010faka novej nemennej architekt\u00fare a modelu platformy Operator na automatiz\u00e1ciu zlo\u017eit\u00fdch konfigur\u00e1ci\u00ed aplik\u00e1ci\u00ed a platforiem, ktor\u00e9 pracuj\u00fa v klastrov\u00fdch prostrediach. Appranix pon\u00faka pou\u017e\u00edvate\u013eom OpenShift jednoduch\u00fd a pohodln\u00fd sp\u00f4sob prechodu na OpenShift 4 pomocou svojho cloudov\u00e9ho rie\u0161enia na obnovu aplik\u00e1ci\u00ed Site Reliability Platform. <\/p>\n<p><b>Rie\u0161enie Appranix je mo\u017en\u00e9 pou\u017e\u00edva\u0165 priamo z <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/access.redhat.com\/containers\/?tab%3Dimages%23\/registry.connect.redhat.com\/appranix\/apx-manager&amp;sa=D&amp;ust=1562087733756000\">Red Hat Container Catalog<\/a><\/noindex>.<\/b><br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/redhatrussia\/blog\/463763\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0418\u0442\u0430\u043a, \u0441\u043e\u0441\u0442\u043e\u044f\u043b\u0441\u044f \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 \u0437\u0430\u043f\u0443\u0441\u043a \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u044b Red Hat OpenShift 4. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u043c, \u043a\u0430\u043a \u043f\u0435\u0440\u0435\u0439\u0442\u0438 \u043d\u0430 \u043d\u0435\u0435 \u0441 OpenShift Container Platform 3 \u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u043e \u0431\u044b\u0441\u0442\u0440\u043e \u0438 \u043f\u0440\u043e\u0441\u0442\u043e. \u0412 \u0440\u0430\u043c\u043a\u0430\u0445 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u043d\u0430\u0441 \u043f\u0440\u0435\u0436\u0434\u0435 \u0432\u0441\u0435\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u0443\u044e\u0442 \u043d\u043e\u0432\u044b\u0435 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u044b OpenShift 4, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0443\u043c\u043d\u043e\u0439 \u0438 \u043d\u0435\u0438\u0437\u043c\u0435\u043d\u043d\u043e\u0439 (immutable \u2013 \u043e\u0434\u0438\u043d\u0430\u043a\u043e\u0432\u043e\u0439 \u0434\u043b\u044f \u0432\u0441\u0435\u0445 \u0441\u0440\u0435\u0434 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f) \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 RHEL CoreOS \u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27897,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37204","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0418\u0442\u0430\u043a, \u0441\u043e\u0441\u0442\u043e\u044f\u043b\u0441\u044f \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 \u0437\u0430\u043f\u0443\u0441\u043a \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u044b Red Hat OpenShift 4.\" \/>\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\/sk\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\u0423\u043f\u0440\u043e\u0449\u0430\u0435\u043c \u043c\u0438\u0433\u0440\u0430\u0446\u0438\u044e \u0441 OpenShift 3 \u043d\u0430 OpenShift 4 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0418\u0442\u0430\u043a, \u0441\u043e\u0441\u0442\u043e\u044f\u043b\u0441\u044f \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 \u0437\u0430\u043f\u0443\u0441\u043a \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u044b Red Hat OpenShift 4.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4\" \/>\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=\"2019-10-31T19:16:20+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:16:20+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\udd47U\u013eah\u010dujeme migr\u00e1ciu z OpenShift 3 na OpenShift 4 | ProHoster","description":"Tak\u017ee sa uskuto\u010dnil ofici\u00e1lny \u0161tart platformy Red Hat OpenShift 4.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","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\u0423\u043f\u0440\u043e\u0449\u0430\u0435\u043c \u043c\u0438\u0433\u0440\u0430\u0446\u0438\u044e \u0441 OpenShift 3 \u043d\u0430 OpenShift 4 | ProHoster","og:description":"\u0418\u0442\u0430\u043a, \u0441\u043e\u0441\u0442\u043e\u044f\u043b\u0441\u044f \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 \u0437\u0430\u043f\u0443\u0441\u043a \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u044b Red Hat OpenShift 4.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","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":"2019-10-31T19:16:20+00:00","article:modified_time":"2019-10-31T19:16:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37204","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":"2026-01-23 16:43:23","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:31:25","updated":"2026-01-23 16:43:23","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\/37204","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=37204"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37204\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/27897"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=37204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=37204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=37204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}