{"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\/lv\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","title":{"rendered":"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>T\u0101tad ofici\u0101li tika uzs\u0101kta Red Hat OpenShift 4 platforma. \u0160odien m\u0113s izst\u0101st\u012bsim, k\u0101 \u0101tri un viegli p\u0101riet uz to no OpenShift Container Platform 3.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/f7411df89b507a9a7e5825c1b5d3fbf5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u0160\u012bs raksta ietvaros vispirms m\u016bs interes\u0113 jaunie OpenShift 4 klasteri, kas izmanto inteli\u0123entas un nemain\u012bgas (immutable \u2013 vien\u0101das vis\u0101m izvieto\u0161anas vid\u0113m) infrastrukt\u016bras iesp\u0113jas, pamatojoties uz RHEL CoreOS un automatiz\u0101cijas r\u012bkiem. Zem\u0101k m\u0113s par\u0101d\u012bsim, k\u0101 p\u0101riet uz OpenShift 4 bez liek\u0101m probl\u0113m\u0101m.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nLai uzzin\u0101tu vair\u0101k par jaun\u0101s versijas at\u0161\u0137ir\u012bb\u0101m no iepriek\u0161\u0113j\u0101s, varat <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\">\u0161eit<\/a><\/noindex>.<\/p>\n<h3>Migr\u0101cija no OpenShift 3 uz OpenShift 4, izmantojot sertific\u0113to Red Hat Appranix platformu<\/h3>\n<p>\nAppranix un Red Hat r\u016bp\u012bgi str\u0101d\u0101ja, lai vienk\u0101r\u0161otu klasteru resursu migr\u0101ciju no OpenShift 3 uz OpenShift 4, izmantojot \u012bpa\u0161u pakalpojumu, kas darbojas virs Appranix Site Reliability Automation risin\u0101juma Kubernetes.<\/p>\n<p>Appranix risin\u0101jums (to var atrast <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>) \u013cauj izveidot rezervkopijas visiem OpenShift 3 klasteriem un atjaunot tos OpenShift 4 tikai da\u017e\u0101s klik\u0161\u0137os.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/5ed42cbbe2cead8c793b4c9fc69ccb0e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>K\u0101p\u0113c migr\u0101cija, izmantojot Appranix, ir lab\u0101ka OpenShift 4<\/h3>\n<p><\/p>\n<ul>\n<li>\u0100tra palai\u0161ana. T\u0101 k\u0101 Appranix risin\u0101jums ir balst\u012bts uz SaaS principiem, nav nepiecie\u0161ams konfigur\u0113t nek\u0101du infrastrukt\u016bru, k\u0101 ar\u012b izmantot atsevi\u0161\u0137us specializ\u0113tus migr\u0101cijas risin\u0101jumus.<\/li>\n<li>Appranix m\u0113rogojam\u012bba atvieglo lielu klasteru migr\u0101ciju.<\/li>\n<li>Autom\u0101tiska sare\u017e\u0123\u012btu OpenShift 3 klasteru konfigur\u0101ciju rezervkop\u0113\u0161ana ar turpm\u0101ku p\u0101rs\u016bt\u012b\u0161anu uz OpenShift 4 atvieglo pa\u0161u migr\u0101cijas procesu.<\/li>\n<li>Iesp\u0113ja izm\u0113\u0123in\u0101t, k\u0101 lietojumprogrammas no uz\u0146\u0113muma OpenShift 3 infrastrukt\u016bras uzvedas OpenShift 4 platform\u0101 AWS m\u0101ko\u0146\u0101.<\/li>\n<li>RBAC piek\u013cuves iestat\u012bjumu migr\u0101cija kop\u0101 ar klastera resursiem.<\/li>\n<li>Izv\u0113les vai pilna visu projektu migr\u0101cija uz jaunajiem OpenShift 4 klasteriem.<\/li>\n<li>P\u0113c izv\u0113les \u2013 vair\u0101ku l\u012bme\u0146u nep\u0101rtraukt\u012bbas organiz\u0113\u0161ana konteineru lietojumprogramm\u0101m, ja ir atbilsto\u0161a abon\u0113\u0161ana.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/efea466d37f85d204ff868ceb2eddfca.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Vair\u0101ku l\u012bme\u0146u notur\u012bba (resiliency) OpenShift lietojumprogramm\u0101m<\/h3>\n<p>\nP\u0113c migr\u0101cijas no 3. versijas uz 4. versiju OpenShift risin\u0101jumu Appranix var izmantot, lai nodro\u0161in\u0101tu nep\u0101rtrauktu lietojumprogrammu notur\u012bbu (Continuous App Resilience), kur\u0101 ir tr\u012bs iesp\u0113jas. <b>L\u012bmenis 1<\/b> notur\u012bbas (Level 1 Resiliency) funkcionalit\u0101te \u013cauj atjaunot lietotnes bez re\u0123iona un m\u0101ko\u0146u pakalpojumu sniedz\u0113ja mai\u0146as. To var izmantot lietot\u0146u atgrie\u0161anai atpaka\u013c vai atjauno\u0161anai p\u0113c viet\u0113ja boj\u0101juma re\u0123iona l\u012bmen\u012b, piem\u0113ram, neveiksm\u012bga lietotnes izvieto\u0161anas gad\u012bjum\u0101, vai situ\u0101cij\u0101, kur\u0101 nepiecie\u0161ams \u0101tri izveidot test\u0113\u0161anas vidi taj\u0101 pa\u0161\u0101 re\u0123ion\u0101, bet cit\u0101 OpenShift klaster\u012b.<\/p>\n<p><b>L\u012bmenis 2<\/b> \u013cauj p\u0101rvietot lietotnes uz citu re\u0123ionu bez pakalpojumu sniedz\u0113ja mai\u0146as. \u0160aj\u0101 gad\u012bjum\u0101 var saglab\u0101t pamata (primary) datu infrastrukt\u016bru galvenaj\u0101 re\u0123ion\u0101, ta\u010du lietotnes var darbin\u0101t cit\u0101 klaster\u012b cit\u0101 re\u0123ion\u0101. \u0160\u012b iesp\u0113ja ir noder\u012bga, kad m\u0101ko\u0146u re\u0123ions vai zona k\u013c\u016bst neder\u012bga, vai ir nepiecie\u0161ams p\u0101rs\u016bt\u012bt lietotnes uz citu re\u0123ionu kiberdraudu d\u0113\u013c. Un visbeidzot, <b>L\u012bmenis 3<\/b> \u013cauj main\u012bt ne tikai re\u0123ionu, bet ar\u012b m\u0101ko\u0146u pakalpojumu sniedz\u0113ju.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/b336f68bb81ad007025e1a10e9b83a59.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><b>K\u0101 darbojas Appranix SRA<\/b><br \/>\nDaudzk\u0101rt\u0113ja OpenShift lietot\u0146u k\u013c\u016bmes iztur\u012bba Appranix tiek sasniegta, pateicoties \u201elaika ma\u0161\u012bnas\u201d funkcionalit\u0101tei, kas autom\u0101tiski izveido lietot\u0146u vid\u0113m rezerves kopijas. Lai izmantotu \u0161o funkcionalit\u0101ti un palielin\u0101tu lietot\u0146u dro\u0161\u012bbu, pietiek pievienot savam DevOps kan\u0101lam tikai vienu koda rindu.<br \/>\nInfrastrukt\u016bras pakalpojumos m\u0101ko\u0146u pakalpojumu sniedz\u0113jos ar\u012b rodas probl\u0113mas, t\u0101p\u0113c iesp\u0113ja \u0101tri p\u0101riet pie cita pakalpojumu sniedz\u0113ja ir noder\u012bga, lai izvair\u012btos no atkar\u012bbas no viena pakalpojumu sniedz\u0113ja.<\/p>\n<p><b>K\u0101 par\u0101d\u012bts att\u0113l\u0101 zem\u0101k<\/b>, lietot\u0146u vidi rezerves kopijas var tikt izveidotas Appranix ne tikai autom\u0101tiski ar noteiktu periodiskumu, bet ar\u012b r\u012bkojuma form\u0101 no nep\u0101rtraukta integr\u0101cijas un pieg\u0101des CI\/CD kan\u0101la. \u0160aj\u0101 gad\u012bjum\u0101 \u201elaika ma\u0161\u012bna\u201d nodro\u0161ina:<\/p>\n<ul>\n<li>Inkrement\u0101lo GitHub veida nosaukumu telpu un lietot\u0146u vid\u0113m \u017eurn\u0101lu.<\/li>\n<li>Vienk\u0101r\u0161a lietot\u0146u atgrie\u0161ana atpaka\u013c.<\/li>\n<li>M\u0101ko\u0146u vid\u0113m un konteineru konfigur\u0101ciju versiju p\u0101rvald\u012bba.<\/li>\n<li>Automatiz\u0113ta datu dz\u012bves cikla p\u0101rvald\u012bba.<\/li>\n<li>Infrastrukt\u016bras k\u0101 koda (IaC) automatiz\u0113ta p\u0101rvald\u012bba.<\/li>\n<li>Automatiz\u0113ta IaC st\u0101vok\u013cu p\u0101rvald\u012bba.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/f22fdab2ecf9535511f203bebae3d647.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Ar pal\u012bdz\u012bbu Appranix var organiz\u0113t aizsardz\u012bbu un atjauno\u0161anu lietojumprogrammu l\u012bmen\u012b piln\u012bg\u0101m situ\u0101cij\u0101m, piem\u0113ram, haosa in\u017eenierijai (chaos engineering), katastrofu atjauno\u0161anai, aizsardz\u012bbai pret izspie\u0161anu un biznesa procesu nep\u0101rtraukt\u012bbas nodro\u0161in\u0101\u0161anai. M\u0113s neapst\u0101simies pie t\u0101 s\u012bk\u0101k un turpin\u0101sim apspriest, k\u0101 izmantot Appranix migr\u0101cijai no OpenShift 3 uz OpenShift 4.<\/p>\n<h3>K\u0101 notiek migr\u0101cija no OpenShift 3 uz OpenShift 4, izmantojot Appranix Site Reliability Platform<\/h3>\n<p>\nProcess ietver tr\u012bs posmus:<\/p>\n<ol>\n<li>Konfigur\u0113jam OpenShift 3 un OpenShift 4 autom\u0101tiskai atkl\u0101\u0161anai visiem p\u0101rvietojamiem komponentiem.<\/li>\n<li>Izveidojam politikas un iestat\u0101m nosaukuma telpas migr\u0101cijai.<\/li>\n<li>Atjaunojam visas nosaukuma telpas OpenShift 4 vien\u0101 klik\u0161\u0137\u012b.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/005a7d892f21324a57b13e57ad0fd474.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Konfigur\u0113jam OpenShift 3 un 4 klasterus autom\u0101tiskai atkl\u0101\u0161anai<\/h3>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/6913f438b885652cc1e99314f2a90e6a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix uzskata, ka jums jau ir darboto OpenShift 3 un OpenShift 4 klasteri. Ja OpenShift 4 klasteri v\u0113l nav izveidoti, izveidojiet tos, izmantojot <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\">Red Hat dokument\u0101ciju OpenShift 4 izvieto\u0161anai<\/a><\/noindex>. Pamata (primary) un m\u0113r\u0137a (target) klasteru iestat\u012b\u0161ana Appranix notiek vien\u0101di un ietver tikai da\u017eus so\u013cus.<\/p>\n<h3>Instal\u0113jam Appranix Controller Agent klasteru atkl\u0101\u0161anai<\/h3>\n<p>\nKlasteru resursu atkl\u0101\u0161anai nepiecie\u0161ams neliels sekojo\u0161s a\u0123ents. Lai to izvietotu, pietiek ar to, ka kop\u0113jat un iel\u012bm\u0113jat attiec\u012bgo curl komandu, <b>k\u0101 nor\u0101d\u012bts zem\u0101k<\/b>. P\u0113c tam, kad a\u0123ents ir uzst\u0101d\u012bts OpenShift 3 un OpenShift 4, Appranix autom\u0101tiski atkl\u0101s visus p\u0101rvietojamos klasteru resursus, tostarp nosaukuma telpas, izvietojumus, podus, pakalpojumus un citus resursus.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/20caf8a39d0c99a6ff86d3f53b1cffbf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Lielu sadal\u012btu lietojumprogrammu migr\u0101cija<br \/>\nTagad m\u0113s piem\u0113ra ietvaros apl\u016bkosim, k\u0101 bez liek\u0101m p\u016bl\u0113m p\u0101rvietot no OpenShift 3 uz OpenShift 4 sadal\u012btu mikropakalpojumu lietojumprogrammu SockShop (saites \u2013 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/github.com\/microservices-demo&amp;sa=D&amp;ust=1562087733751000\">detaliz\u0113ts \u0161\u012bs lietojumprogrammas apraksts un t\u0101s mikropakalpojumu arhitekt\u016bra<\/a><\/noindex>). K\u0101 redzams no <b>att\u0113la zem\u0101k<\/b>, SockShop arhitekt\u016bra satur daudz komponentu.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/6c9e65a9cd23869175aa736e03c71798.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix atkl\u0101j visus resursus, kuriem nepiecie\u0161ama aizsardz\u012bba un migr\u0101cija uz OpenShift 4, tostarp podus, izvietojumus, pakalpojumus un klastera konfigur\u0101cijas.<\/p>\n<h3>OpenShift 3 ar darbin\u0101mo SockShop lietojumprogrammu<\/h3>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/5340aacbea58e3d80d73a3b581f9ef08.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/eeb107cb553ccfd1f5bffbfb4e745acf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Izveidojam aizsardz\u012bbas politikas (Protection Policies) migr\u0101cijai<\/h3>\n<p>\nPolitikas var noteikt elast\u012bgi atkar\u012bb\u0101 no t\u0101, k\u0101 migr\u0101cija j\u0101veic. Piem\u0113ram, pamatojoties uz vair\u0101kiem krit\u0113rijiem vai dro\u0161\u012bbas kopij\u0101m reizi stund\u0101.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/7c62333127d08fe469222562146df10b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>M\u0113s veicam vair\u0101kus OpenShift 3 klasteru migr\u0101cijas procesus, izmantojot aizsardz\u012bbas pl\u0101nus (Protection Plans).<\/h3>\n<p>\nAtkar\u012bb\u0101 no lietojumprogrammas vai nosaukumtelpas \u012bpatn\u012bb\u0101m, OpenShift 3 klasteriem var pielietot politikas, kas tiek p\u0101rbaud\u012btas reizi stund\u0101, reizi ned\u0113\u013c\u0101 vai pat reizi m\u0113nes\u012b.<\/p>\n<p>Appranix \u013cauj p\u0101rvietot uz OpenShift 4 visus klastera nosaukumtelpas vai tikai izv\u0113l\u0113t\u0101s telpas.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/e1acfff015e8d6b57d316c2a21bb5cea.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>M\u0113s migr\u0113jam uz OpenShift 4 ar vienu klik\u0161\u0137i.<\/h3>\n<p>\nMigr\u0101cija ir izv\u0113l\u0113to nosaukumtelpu atjauno\u0161ana jaunaj\u0101 OpenShift 4 klaster\u012b. \u0160\u012b darb\u012bba tiek veikta vien\u0101 klik\u0161\u0137\u012b. Appranix pats veic visu darbu, v\u0101cot inform\u0101ciju par konfigur\u0101ciju un s\u0101kotn\u0113j\u0101s vides resursiem, un p\u0113c tam atjauno to OpenShift 4 platform\u0101.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/a6de0780bbcd4fb05663ca48f0da58ee.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/d32618d1dbeb74a96af1b8fce362352e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>P\u0101rbaud\u0101m lietojumprogrammas p\u0113c migr\u0101cijas uz OpenShift 4.<\/h3>\n<p>\nPiesakieties OpenShift 4 klaster\u012b, atjaunojiet projektus un p\u0101rliecinieties, ka visas lietojumprogrammas un nosaukumtelpas ir k\u0101rt\u012bb\u0101. Veiciet migr\u0101cijas proced\u016bru cit\u0101m nosaukumtelp\u0101m, izveidojot jaunas aizsardz\u012bbas pl\u0101nus (Protection Plans) vai mainot jau eso\u0161\u0101s.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/0819a06d267a406c6f0bc98d458456a8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Palaidiet migr\u0113t\u0101s lietojumprogrammas uz OpenShift 4.<\/h3>\n<p>\nP\u0113c lietojumprogrammu migr\u0101cijas ar Appranix atjauno\u0161anas proced\u016bru svar\u012bgi neaizmirst konfigur\u0113t mar\u0161rutus \u2013 tiem j\u0101nor\u0101da uz OpenShift 4. Iesp\u0113jams, pirms piln\u012bgas produkcijas p\u0101rvieto\u0161anas no OpenShift 3, v\u0113l\u0113sieties veikt testu atjauno\u0161anu. Kad OpenShift 4 b\u016bs da\u017eas darbojo\u0161\u0101s lietojumprogrammas attiec\u012bgaj\u0101s nosaukumtelp\u0101s, rad\u012bsies nepiecie\u0161am\u012bba p\u0101rvietot ar\u012b p\u0101r\u0113j\u0101s lietojumprogrammas, izmantojot \u0161o procesu.<\/p>\n<p>P\u0113c visu nosaukumtelpu p\u0101rvieto\u0161anas j\u016bs var\u0113siet aizsarg\u0101t visus OpenShift klasterus nep\u0101rtrauktai katastrofu atjauno\u0161anai, aizsardz\u012bbai pret izspie\u0161anas programmat\u016bru, biznesa procesu nep\u0101rtraukt\u012bbas nodro\u0161in\u0101\u0161anai vai turpm\u0101kai migr\u0101cijai, jo Appranix Site Reliability Automation autom\u0101tiski tiek atjaunin\u0101ts l\u012bdz ar jauno OpenShift versiju izlai\u0161anu.<\/p>\n<p><img decoding=\"async\" alt=\"Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/c5e2cd72465d7ba096ab225bff1e3c42.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Kop\u0113j\u0101 summa<\/h3>\n<p>\nOpenShift 4 \u2013 ir liels solis uz priek\u0161u, pateicoties jaunajai nemain\u012bgajai arhitekt\u016brai un Operator platformas modelim, kas automatiz\u0113 sare\u017e\u0123\u012btu lietojumprogrammu un platformu konfigur\u0101ciju p\u0101rvald\u012bbu, str\u0101d\u0101jot klastera vid\u0113. Appranix pied\u0101v\u0101 OpenShift lietot\u0101jiem vienk\u0101r\u0161u un \u0113rtu veidu, k\u0101 p\u0101riet uz OpenShift 4, izmantojot savu m\u0101ko\u0146orient\u0113to risin\u0101jumu lietojumprogrammu av\u0101rijas atjauno\u0161anai Site Reliability Platform. <\/p>\n<p><b>Appranix risin\u0101jumu var izmantot tie\u0161i no <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 \/>Avots: <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\/lv\/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=\"lv_LV\" \/>\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\/lv\/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\udd47Atvieglojam migr\u0101ciju no OpenShift 3 uz OpenShift 4 | ProHoster","description":"T\u0101tad, notika ofici\u0101l\u0101 Red Hat OpenShift 4 platformas palai\u0161ana.","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\/lv\/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\/lv\/wp-json\/wp\/v2\/posts\/37204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=37204"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/37204\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/27897"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=37204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=37204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=37204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}