{"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\/ro\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","title":{"rendered":"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Astfel, a avut loc lansarea oficial\u0103 a platformei Red Hat OpenShift 4. Ast\u0103zi v\u0103 vom ar\u0103ta cum s\u0103 trece\u021bi la ea de la OpenShift Container Platform 3 c\u00e2t mai rapid \u0219i simplu.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/f7411df89b507a9a7e5825c1b5d3fbf5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u00cen cadrul acestui articol, suntem mai ales interesa\u021bi de noile clustere OpenShift 4, care utilizeaz\u0103 avantajele unei infrastructuri inteligente \u0219i imuabile (immutable \u2013 identice pentru toate mediile de implementare) bazate pe RHEL CoreOS \u0219i instrumente de automatizare. Mai jos v\u0103 vom ar\u0103ta cum s\u0103 trece\u021bi la OpenShift 4 f\u0103r\u0103 probleme suplimentare.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nPentru a afla mai multe despre diferen\u021bele dintre noua versiune \u0219i cea veche, pute\u021bi <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\">aici<\/a><\/noindex>.<\/p>\n<h3>Migrarea clustereelor de la OpenShift 3 la OpenShift 4 cu ajutorul platformei certificate Red Hat Appranix<\/h3>\n<p>\nAppranix \u0219i Red Hat au colaborat \u00eendeaproape pentru a simplifica migrarea resurselor cluster de la OpenShift 3 la OpenShift 4 prin intermediul unui serviciu special care func\u021bioneaz\u0103 pe Appranix Site Reliability Automation pentru Kubernetes.<\/p>\n<p>Solu\u021bia Appranix (o pute\u021bi g\u0103si \u00een <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>) permite crearea de backup-uri pentru toate clusterele OpenShift 3 \u0219i restaurarea lor pe OpenShift 4 cu doar c\u00e2teva clicuri.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/5ed42cbbe2cead8c793b4c9fc69ccb0e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Ce este benefic \u00een migrarea utiliz\u00e2nd Appranix pentru OpenShift 4<\/h3>\n<p><\/p>\n<ul>\n<li>Start rapid. Deoarece solu\u021bia Appranix este construit\u0103 pe principii SaaS, nu este necesar s\u0103 configura\u021bi nicio infrastructur\u0103 sau s\u0103 utiliza\u021bi solu\u021bii specializate pentru migrare.<\/li>\n<li>Scalabilitatea Appranix faciliteaz\u0103 migrarea pentru clustere mari.<\/li>\n<li>Backup-ul automat al configura\u021biilor complexe de clustere OpenShift 3, urmat de transferul lor pe OpenShift 4, simplific\u0103 procesul de migrare.<\/li>\n<li>Posibilitatea de a testa cum se comport\u0103 aplica\u021biile din infrastructura corporativ\u0103 OpenShift 3 pe platforma OpenShift 4 \u00een cloud-ul AWS.<\/li>\n<li>Migrarea set\u0103rilor RBAC de acces \u00eempreun\u0103 cu resursele clusterului.<\/li>\n<li>Migrarea selectiv\u0103 sau complet\u0103 a tuturor proiectelor la noile clustere OpenShift 4.<\/li>\n<li>Op\u021bional \u2013 organizarea mai multor niveluri de rezisten\u021b\u0103 la defec\u021biune pentru aplica\u021biile containerizate, av\u00e2nd la dispozi\u021bie o subscrip\u021bie corespunz\u0103toare.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/efea466d37f85d204ff868ceb2eddfca.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Rezisten\u021b\u0103 la defec\u021biune \u00een mai multe niveluri (resiliency) pentru aplica\u021biile OpenShift<\/h3>\n<p>\nDup\u0103 migrarea de la versiunea 3 la versiunea 4 a OpenShift, solu\u021bia Appranix poate fi folosit\u0103 pentru a asigura continuitatea rezilien\u021bei aplica\u021biilor (Continuous App Resilience), pentru care sunt posibile trei variante. <b>Nivelul 1<\/b> rezilien\u021ba (Nivel 1 Rezilien\u021b\u0103) permite restaurarea aplica\u021biilor f\u0103r\u0103 schimbarea regiunii \u0219i a furnizorului de servicii cloud. Poate fi utilizat\u0103 pentru a reveni la aplica\u021bii sau pentru a restaura dup\u0103 o defec\u021biune local\u0103 la nivel regional, de exemplu, \u00een cazul unei desf\u0103\u0219ur\u0103ri nereu\u0219ite a aplica\u021biei, sau \u00eentr-o situa\u021bie \u00een care este necesar s\u0103 se creeze rapid un mediu de testare \u00een aceea\u0219i regiune, dar \u00eentr-un cluster OpenShift separat.<\/p>\n<p><b>Nivelul 2<\/b> permet transferul aplica\u021biilor \u00eentr-o alt\u0103 regiune f\u0103r\u0103 a schimba furnizorul. \u00cen acest caz, pute\u021bi men\u021bine infrastructura principal\u0103 (primary) a datelor \u00een regiunea principal\u0103, dar s\u0103 lansa\u021bi aplica\u021biile \u00eentr-un alt cluster dintr-o alt\u0103 regiune. Aceast\u0103 op\u021biune este util\u0103 atunci c\u00e2nd un domeniu cloud sau o zon\u0103 devin indisponibile sau c\u00e2nd este necesar s\u0103 muta\u021bi aplica\u021biile \u00eentr-o alt\u0103 regiune din cauza unui atac cibernetic. \u0218i, \u00een sf\u00e2r\u0219it, <b>Nivelul 3<\/b> permet schimbarea nu doar a regiunii, ci \u0219i a furnizorului de cloud.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/b336f68bb81ad007025e1a10e9b83a59.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><b>Cum func\u021bioneaz\u0103 Appranix SRA<\/b><br \/>\nRezisten\u021ba la defecte a aplica\u021biilor OpenShift \u00een Appranix se ob\u021bine prin func\u021bionalitatea de \u201ema\u0219in\u0103 a timpului\u201d, care creeaz\u0103 automat copii ale mediului aplica\u021biilor. Pentru a activa aceast\u0103 func\u021bionalitate \u0219i a spori securitatea aplica\u021biilor, este suficient s\u0103 ad\u0103uga\u021bi o singur\u0103 linie de cod \u00een pipeline-ul DevOps.<br \/>\n\u00cen serviciile de infrastructur\u0103 ale furnizorilor de cloud apar \u0219i probleme, astfel \u00eenc\u00e2t capacitatea de a comuta rapid la alt furnizor este util\u0103 pentru a evita dependen\u021ba de un singur furnizor de servicii.<\/p>\n<p><b>A\u0219a cum este prezentat \u00een imaginea de mai jos<\/b>, copiile de rezerv\u0103 ale mediilor aplica\u021biilor pot fi create \u00een Appranix nu doar automat cu o periodicitate stabilit\u0103, ci \u0219i la comand\u0103 din pipeline-ul de integrare \u0219i livrare continu\u0103 CI\/CD. \u00cen acest caz, \u201ema\u0219ina timpului\u201d asigur\u0103:<\/p>\n<ul>\n<li>Jurnalizarea incrementat\u0103, de tip GitHub, a spa\u021biilor de nume \u0219i a mediilor aplica\u021biilor.<\/li>\n<li>Rollback simplu al aplica\u021biilor.<\/li>\n<li>Gestionarea versiunilor configura\u021biilor mediilor cloud \u0219i containerelor.<\/li>\n<li>Gestionarea automatizat\u0103 a ciclului de via\u021b\u0103 al datelor.<\/li>\n<li>Automatizarea gestion\u0103rii infrastructurii ca \u0219i cod (IaC).<\/li>\n<li>Gestionare automatizat\u0103 a st\u0103rilor IaC.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/f22fdab2ecf9535511f203bebae3d647.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Cu Appranix, pute\u021bi organiza protec\u021bia \u0219i recuperarea la nivel de aplica\u021bie \u00een \u00eentregime pentru scenarii precum inginerie a haosului, recuperare \u00een caz de dezastru, protec\u021bie \u00eempotriva ransomware \u0219i asigurarea continuit\u0103\u021bii proceselor de afaceri. Nu ne vom opri aici asupra detaliilor \u0219i vom explora cum s\u0103 utiliz\u0103m Appranix pentru migrarea de la OpenShift 3 la OpenShift 4.<\/p>\n<h3>Cum se efectueaz\u0103 migrarea de la OpenShift 3 la OpenShift 4 folosind Appranix Site Reliability Platform<\/h3>\n<p>\nProcesul include trei etape:<\/p>\n<ol>\n<li>Configur\u0103m OpenShift 3 \u0219i OpenShift 4 pentru autodetectarea tuturor componentelor care urmeaz\u0103 s\u0103 fie migrat.<\/li>\n<li>Cre\u0103m politici \u0219i definim spa\u021biile de nume pentru migrare.<\/li>\n<li>Recuper\u0103m toate spa\u021biile de nume pe OpenShift 4 dintr-o singur\u0103 ac\u021biune.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/005a7d892f21324a57b13e57ad0fd474.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Configur\u0103m clusterele OpenShift 3 \u0219i 4 pentru autodetectare<\/h3>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/6913f438b885652cc1e99314f2a90e6a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix presupune c\u0103 deja ave\u021bi clustere func\u021bionale OpenShift 3 \u0219i OpenShift 4. Dac\u0103 nu ave\u021bi clustere OpenShift 4, crea\u021bi-le folosind <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\">documenta\u021bia Red Hat pentru implementarea OpenShift 4<\/a><\/noindex>. Configurarea clusterului principal \u0219i a celui \u021bint\u0103 \u00een Appranix se face \u00een mod similar \u0219i implic\u0103 doar c\u00e2\u021biva pa\u0219i.<\/p>\n<h3>Instal\u0103m Appranix Controller Agent pentru detectarea clusterelor<\/h3>\n<p>\nPentru detectarea resurselor clusterului este nevoie de un mic agent sidecar-controller. Pentru implementarea acestuia, este suficient s\u0103 copia\u021bi \u0219i s\u0103 lipi\u021bi comanda curl corespunz\u0103toare, <b>dup\u0103 cum este ilustrat mai jos<\/b>. Dup\u0103 ce agentul este instalat \u00een OpenShift 3 \u0219i OpenShift 4, Appranix va detecta automat toate resursele de cluster care urmeaz\u0103 s\u0103 fie migrate, inclusiv spa\u021biile de nume, desf\u0103\u0219ur\u0103rile, podurile, serviciile, precum \u0219i gazdele cu alte resurse.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/20caf8a39d0c99a6ff86d3f53b1cffbf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Migrarea aplica\u021biilor distribuite mari<br \/>\nAcum vom examina un exemplu despre cum se poate realiza f\u0103r\u0103 dificult\u0103\u021bi migrarea de la OpenShift 3 la OpenShift 4 a unei aplica\u021bii microservicii distribuite, SockShop (la link \u2013 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/github.com\/microservices-demo&amp;sa=D&amp;ust=1562087733751000\">o descriere detaliat\u0103 a acestei aplica\u021bii \u0219i arhitecturii sale microservicii<\/a><\/noindex>). A\u0219a cum se poate observa din <b>ilustra\u021bia de mai jos<\/b>, arhitectura SockShop con\u021bine numeroase componente.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/6c9e65a9cd23869175aa736e03c71798.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix detecteaz\u0103 toate resursele pentru care trebuie asigurat\u0103 protec\u021bia \u0219i migrarea la OpenShift 4, inclusiv, podurile, desf\u0103\u0219ur\u0103rile, serviciile \u0219i configura\u021biile clusterului.<\/p>\n<h3>OpenShift 3 cu aplica\u021bia SockShop func\u021bional\u0103<\/h3>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/5340aacbea58e3d80d73a3b581f9ef08.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/eeb107cb553ccfd1f5bffbfb4e745acf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Cre\u0103m politici de protec\u021bie pentru migrare<\/h3>\n<p>\nPoliticile pot fi stabilite flexibil \u00een func\u021bie de modul \u00een care trebuie realizat\u0103 migrarea. De exemplu, pe baza mai multor criterii sau backup o dat\u0103 pe or\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/7c62333127d08fe469222562146df10b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Execut\u0103m migrarea mai multor clustere OpenShift 3 cu ajutorul planurilor de protec\u021bie (Protection Plans)<\/h3>\n<p>\n\u00cen func\u021bie de caracteristicile aplica\u021biei sau de spa\u021biul de nume, se pot aplica politici la clusterele OpenShift 3, care se execut\u0103 o dat\u0103 pe or\u0103, o dat\u0103 pe s\u0103pt\u0103m\u00e2n\u0103 sau chiar o dat\u0103 pe lun\u0103.<\/p>\n<p>Appranix permite transferul tuturor spa\u021biilor de nume ale clusterului pe OpenShift 4 sau doar a celor selectate.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/e1acfff015e8d6b57d316c2a21bb5cea.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Execut\u0103m migrarea pe OpenShift 4 dintr-o singur\u0103 ac\u021biune<\/h3>\n<p>\nMigrarea reprezint\u0103 restaurarea spa\u021biilor de nume selectate pe clusterul \u021bint\u0103 OpenShift 4. Aceast\u0103 opera\u021biune se realizeaz\u0103 dintr-o singur\u0103 ac\u021biune. Appranix se ocup\u0103 automat de colectarea datelor despre configura\u021bia \u0219i resursele mediului de origine \u0219i apoi le restaureaz\u0103 pe platforma OpenShift 4.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/a6de0780bbcd4fb05663ca48f0da58ee.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/d32618d1dbeb74a96af1b8fce362352e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Verific\u0103m aplica\u021biile dup\u0103 migrarea pe OpenShift 4<\/h3>\n<p>\nConecta\u021bi-v\u0103 la clusterul OpenShift 4, actualiza\u021bi proiectele \u0219i verifica\u021bi dac\u0103 toate aplica\u021biile \u0219i spa\u021biile de nume sunt \u00een regul\u0103. Repeta\u021bi procedura de migrare pentru alte spa\u021bii de nume, cre\u00e2nd pentru aceasta noi planuri Protection Plans sau modific\u00e2nd deja existente.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/0819a06d267a406c6f0bc98d458456a8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Lans\u0103m aplica\u021biile migratoare pe OpenShift 4<\/h3>\n<p>\nDup\u0103 migrarea aplica\u021biilor prin procedura de restaurare Appranix, este important s\u0103 nu uita\u021bi s\u0103 configura\u021bi rutele \u2013 acestea trebuie s\u0103 indice OpenShift 4. Este posibil ca, \u00eenainte de a transferi complet produc\u021bia de pe OpenShift 3, s\u0103 dori\u021bi s\u0103 face\u021bi o restaurare de test. C\u00e2nd pe OpenShift 4 apar mai multe aplica\u021bii func\u021bionale \u00een spa\u021biile de nume corespunz\u0103toare, va fi necesar s\u0103 transfera\u021bi \u0219i celelalte aplica\u021bii prin acest proces.<\/p>\n<p>Dup\u0103 transferul tuturor spa\u021biilor de nume, ve\u021bi putea proteja toate clusterele OpenShift pentru recuperare continu\u0103 \u00een caz de dezastru, protec\u021bie \u00eempotriva ransomware-ului, asigurarea continuit\u0103\u021bii proceselor de afaceri sau pentru migrarea ulterioar\u0103, deoarece Appranix Site Reliability Automation se actualizeaz\u0103 automat pe m\u0103sur\u0103 ce noi versiuni OpenShift devin disponibile.<\/p>\n<p><img decoding=\"async\" alt=\"Simplific\u0103m migrarea de la OpenShift 3 la OpenShift 4\" src=\"\/wp-content\/uploads\/2019\/08\/c5e2cd72465d7ba096ab225bff1e3c42.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>\u00cen concluzie<\/h3>\n<p>\nOpenShift 4 reprezint\u0103 un pas semnificativ \u00eenainte, \u00een principal datorit\u0103 noii arhitecturi immutabile \u0219i modelului Operator-platform\u0103 pentru automatizarea configura\u021biilor complexe ale aplica\u021biilor \u0219i platformelor care func\u021bioneaz\u0103 \u00een medii de tip cluster. Appranix ofer\u0103 utilizatorilor OpenShift o modalitate simpl\u0103 \u0219i convenabil\u0103 de a trece la OpenShift 4, prin intermediul solu\u021biei sale orientate pe cloud pentru recuperarea aplica\u021biilor \u00een caz de dezastru Site Reliability Platform. <\/p>\n<p><b>Solu\u021bia Appranix poate fi utilizat\u0103 direct din <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 \/>Sursa: <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.2.1 - 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\/ro\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/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\udd47Facilit\u0103m migrarea de la OpenShift 3 la OpenShift 4 | ProHoster","description":"A\u0219adar, lansarea oficial\u0103 a platformei Red Hat OpenShift 4 a avut loc.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/37204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=37204"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37204\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27897"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=37204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=37204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=37204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}