{"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\/et\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","title":{"rendered":"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Nii et, Red Hat OpenShift 4 platvormi ametlik k\u00e4ivitamine on toimunud. T\u00e4na r\u00e4\u00e4gime, kuidas \u00fcle minna OpenShift Container Platform 3-lt v\u00f5imalikult kiiresti ja lihtsalt.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/f7411df89b507a9a7e5825c1b5d3fbf5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMeid huvitavad peamiselt uued OpenShift 4 klastrid, mis kasutavad RHEL CoreOS-i p\u00f5hjal loodud nutikat ja muutumatut (immutable \u2013 k\u00f5igis juurutuskeskkondades identset) infrastruktuuri ja automatiseerimisvahendeid. Allpool n\u00e4itame, kuidas minna OpenShift 4-le murede vabalt \u00fcle.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nUute ja vanade versioonide erinevustest saab l\u00e4hemalt lugeda <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\">siit<\/a><\/noindex>.<\/p>\n<h3>Klastrite migreerimine OpenShift 3-lt OpenShift 4-le sertifitseeritud platvormi Red Hat Appranix abil<\/h3>\n<p>\nAppranix ja Red Hat on sihikindlalt t\u00f6\u00f6tanud selle nimel, et lihtsustada klastrite ressursside migreerimist OpenShift 3-lt OpenShift 4-le, kasutades spetsiaalset teenust, mis t\u00f6\u00f6tab Appranix Site Reliability Automationi peal Kubernetes'e jaoks.<\/p>\n<p>Appranix lahendus (mida leiab aadressilt <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>) v\u00f5imaldab luua OpenShift 3 klastrite varukoopiaid ja taastada neid OpenShift 4-le vaid paari kliki kaugusel.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/5ed42cbbe2cead8c793b4c9fc69ccb0e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Appranixiga migreerimine OpenShift 4-le on suurep\u00e4rane valik<\/h3>\n<p><\/p>\n<ul>\n<li>Kiire sisseseade. Kuna Appranixi lahendus p\u00f5hineb SaaS-printsipidel, ei ole vaja seadistada mingit infrastruktuuri ega konfigureerida ega kasutada eraldi spetsialiseeritud lahendusi migreerimiseks.<\/li>\n<li>Appranixi skaleeritavus lihtsustab suurte klastrite migreerimist.<\/li>\n<li>Automaatne keeruliste klastrikonfiguratsioonide OpenShift 3 varundamine koos edasise \u00fcleviimisega OpenShift 4-le teeb migreerimisprotsessi lihtsamaks.<\/li>\n<li>V\u00f5imalus testida, kuidas OpenShift 3 ettev\u00f5tte infrastruktuuri rakendused toimivad OpenShift 4 platvormil AWS-is.<\/li>\n<li>RBAC-juurdep\u00e4\u00e4su seadete migreerimine koos klastrite ressurssidega.<\/li>\n<li>Valikuline v\u00f5i t\u00e4ielik k\u00f5igi projektide migreerimine uutele OpenShift 4 klastritele.<\/li>\n<li>Valikuline \u2013 mitme taseme talitluskindluse organisatsioon konteinerirakendustele, kui on olemas vastav tellimus.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/efea466d37f85d204ff868ceb2eddfca.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Mitme taseme talitluskindlus (resiliency) OpenShifti rakenduste jaoks.<\/h3>\n<p>\nP\u00e4rast migreerimist OpenShift 3-lt OpenShift 4-le saab Appranixi lahendust kasutada rakenduste pideva talitluskindluse (Continuous App Resilience) tagamiseks, mis v\u00f5imaldab kolme varianti. <b>Tase 1<\/b> tasakaalu (Level 1 Resiliency) v\u00f5imaldab taastekita rakendusi ilma regiooni ja pilvepakkujat vahetamata. Seda saab kasutada rakenduste tagasiviimiseks v\u00f5i taastamiseks p\u00e4rast kohalikku t\u00f5rget regiooni tasandil, n\u00e4iteks juhul, kui rakenduse juurutamine eba\u00f5nnestub, v\u00f5i olukorras, kus on vajalik kiiresti luua testkeskkond samas regioonis, kuid eraldi OpenShifti klastris.<\/p>\n<p><b>Tase 2<\/b> v\u00f5imaldab rakendusi teise regiooni viia ilma pakkujat vahetamata. Selle k\u00e4igus saab peamise (primary) andmekeskuse infrastruktuuri s\u00e4ilitada p\u00f5hi-regioonis, kuid k\u00e4ivitada rakendusi teises klastris teises regioonis. See valik on kasulik olukordades, kus pilve regioon v\u00f5i tsoon eba\u00f5nnestub v\u00f5i on vaja rakendusi k\u00fcberr\u00fcnnaku t\u00f5ttu teise regiooni viia. Ja l\u00f5puks, <b>Tase 3<\/b> v\u00f5imaldab vahetada mitte ainult regiooni, vaid ka pilvepakkujat.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/b336f68bb81ad007025e1a10e9b83a59.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><b>Kuidas t\u00f6\u00f6tab Appranix SRA<\/b><br \/>\nOpenShift'i rakenduste mitme taseme talitlush\u00e4irete v\u00e4ltimine Appranixis saavutatakse \"ajaloo masina\" funktsionaalsuse abil, mis loob automaatselt rakenduskeskkonna koopiaid. Selle funktsionaalsuse aktiveerimiseks ja rakenduste kaitstuse suurendamiseks piisab DevOps'i torustikku lisada vaid \u00fcks koodirida.<br \/>\nKuna pilveteenuse pakkujate infrastruktuuriteenustes tekivad samuti probleemid, on oluline v\u00f5imalus kiiresti \u00fcle minna teisele pakkujale, et v\u00e4ltida s\u00f5ltuvust ainsast teenusepakkujast.<\/p>\n<p><b>Nagu alloleval joonisel on n\u00e4ha<\/b>, saavad Appranixis rakenduskeskkonna varukoopiad luua mitte ainult automaatselt m\u00e4\u00e4ratud sagedusega, vaid ka CI\/CD pideva integratsiooni ja kohaletoimetamise torustiku kaudu. Selle puhul tagab \"ajaloo masin\":<\/p>\n<ul>\n<li>Inkrementaalne, GitHubi t\u00fc\u00fcpi nimeruumi ja rakenduskeskkonna logimine.<\/li>\n<li>Lihtne rakenduste tagasi t\u00f5mbamine.<\/li>\n<li>Pilvestrateegiate ja konteinerite konfiguratsioonide versioonihalduse.<\/li>\n<li>Automatiseeritud andmeeluts\u00fckli haldamine.<\/li>\n<li>Automatiseeritud infrastruktuuri haldamine kui kood (IaC).<\/li>\n<li>Automatiseeritud IaC olekute haldamine.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/f22fdab2ecf9535511f203bebae3d647.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranixi abil on v\u00f5imalik korraldada rakenduste tasandi kaitset ja taastamist mitmesugustes stsenaariumides, nagu kaose inseneri, h\u00e4daabi taastamine, lunavarar\u00fcnnakute kaitse ja \u00e4ritegevuse katkematu j\u00e4tkumise tagamine. Me ei peatuda sellel \u00fcksikasjalikult, vaid vaatame, kuidas kasutada Appranixi OpenShift 3-lt OpenShift 4-le migreerimiseks.<\/p>\n<h3>Kuidas toimub OpenShift 3 migreerimine OpenShift 4-le Appranix Site Reliability Platformi abil<\/h3>\n<p>\nProtsess sisaldab kolme etappi:<\/p>\n<ol>\n<li>Seame OpenShift 3 ja OpenShift 4 automaatseks avastamiseks k\u00f5iki migreeritavaid komponente.<\/li>\n<li>Loome poliitikad ja m\u00e4\u00e4rame migreerimise nimed.<\/li>\n<li>Taastame k\u00f5ik nimed OpenShift 4-s \u00fche kl\u00f5psuga.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/005a7d892f21324a57b13e57ad0fd474.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Seame OpenShift 3 ja 4 klastrid automaatseks avastamiseks<\/h3>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/6913f438b885652cc1e99314f2a90e6a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix eeldab, et teil on juba t\u00f6\u00f6korras OpenShift 3 ja OpenShift 4 klastrid. Kui OpenShift 4 klastri pole, looge need, j\u00e4rgides <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 Hati dokumentatsiooni OpenShift 4 juurutamiseks<\/a><\/noindex>. Peamise (primary) ja sihtklastri (target) seadistamine Appranixis toimub samamoodi ning h\u00f5lmab vaid m\u00f5nda sammu.<\/p>\n<h3>Paigaldame Appranix Controller Agenti klastrite avastamiseks<\/h3>\n<p>\nKlastriressursside avastamiseks on vajalik v\u00e4ike sidecar-kontrolleri agent. Selle juurutamiseks piisab vastava curl-k\u00e4sku kopeerimisest ja kleepimisest. <b>nagu allpool n\u00e4idatud<\/b>. P\u00e4rast seda, kui agent on OpenShift 3 ja OpenShift 4-s installitud, avastab Appranix automaatselt k\u00f5ik migreerimisele kuuluvad klastriressursid, sealhulgas nimed, juurutused, podid, teenused ning hostid teiste ressurssidega.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/20caf8a39d0c99a6ff86d3f53b1cffbf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Suure jaotatud rakenduste migreerimine<br \/>\nPraegu vaatame, kuidas vaevata viia jaotatud mikroteenuse rakendus SockShop OpenShift 3-lt OpenShift 4-le (link \u2013 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.google.com\/url?q=https:\/\/github.com\/microservices-demo&amp;sa=D&amp;ust=1562087733751000\">k detailne kirjeldus sellest rakendusest ja selle mikroteenuste arhitektuurist<\/a><\/noindex>). Nagu n\u00e4ha <b>allolevalt jooniselt<\/b>, sisaldab SockShop'i arhitektuur mitmeid komponente.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/6c9e65a9cd23869175aa736e03c71798.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Appranix avastab k\u00f5ik ressursid, mille kaitsmine ja migreerimine OpenShift 4-le on vajalik, sealhulgas podid, juurutused, teenused ja klastri konfiguratsioonid.<\/p>\n<h3>OpenShift 3 t\u00f6\u00f6tava rakendusega SockShop<\/h3>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/5340aacbea58e3d80d73a3b581f9ef08.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/eeb107cb553ccfd1f5bffbfb4e745acf.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Loome kaitsepoliitikad migreerimiseks<\/h3>\n<p>\nPoliitikaid saab paindlikult seada, s\u00f5ltuvalt sellest, kuidas migreerimine peaks toimuma. N\u00e4iteks mitmete kriteeriumite alusel v\u00f5i varundamine kord tunnis.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/7c62333127d08fe469222562146df10b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Teostame mitme OpenShift 3 klastrite migreerimist kaitseplaanide (Protection Plans) abil.<\/h3>\n<p>\nS\u00f5ltuvalt rakenduse v\u00f5i nimede ruumi erip\u00e4radest saab OpenShift 3 klastritele rakendada poliitikaid, mis k\u00e4ivad \u00fcle kord tunnis, kord n\u00e4dalas v\u00f5i isegi kord kuus.<\/p>\n<p>Appranix v\u00f5imaldab migreerida k\u00f5ik klastriruumi nimed OpenShift 4 v\u00f5i valida ainult teatud nimed.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/e1acfff015e8d6b57d316c2a21bb5cea.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Teostame migreerimise OpenShift 4-s \u00fche klikiga.<\/h3>\n<p>\nMigreerimine on valitud nimede taastamine sihtklastris OpenShift 4. See tegevus toimub \u00fche klikiga. Appranix kogub k\u00f5ik konfiguratsiooni- ja ressursside andmed algselt ning taastab need seej\u00e4rel iseseisvalt OpenShift 4 platvormil.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/a6de0780bbcd4fb05663ca48f0da58ee.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/d32618d1dbeb74a96af1b8fce362352e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Kontrollime rakendusi p\u00e4rast migreerimist OpenShift 4-le.<\/h3>\n<p>\nLogige sisse OpenShift 4 klastrisse, v\u00e4rskendage projekte ja kontrollige, et k\u00f5ik rakendused ja nimem\u00e4rgid oleksid korras. Korrake migreerimisseadet teiste nimem\u00e4rkide jaoks, luues selleks uued Protection Plans v\u00f5i muutes juba olemasolevaid.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/0819a06d267a406c6f0bc98d458456a8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>K\u00e4ivitame migreeritud rakendused OpenShift 4-s<\/h3>\n<p>\nP\u00e4rast rakenduste migreerimist Appranixi taastamisprotseduuri abil on oluline mitte unustada marsruutide seadistamist \u2013 need peavad suunama OpenShift 4. Enne kui soovite t\u00e4ielikult tootmise OpenShift 3-st \u00fcle viia, v\u00f5ib teile tunduda, et tasub teha katse taastamine. Kui OpenShift 4-s ilmuvad mitu t\u00f6\u00f6tavat rakendust vastavatesse nimem\u00e4rkidesse, tekib vajadus \u00fcle kanda ka \u00fclej\u00e4\u00e4nud rakendused, kasutades seda protsessi.<\/p>\n<p>P\u00e4rast k\u00f5igi nimem\u00e4rkide \u00fcleviimist saate kaitsta k\u00f5iki OpenShift klastreid pideva \u00e4\u00e4rmusliku taastamise, lunavarade kaitse, \u00e4riprotsesside j\u00e4tkusuutlikkuse tagamise v\u00f5i edasise migreerimise jaoks, kuna Appranix Site Reliability Automation uuendatakse automaatsetes v\u00e4\u00e4rtustes vastavalt OpenShift uute versioonide v\u00e4ljalaskmisele.<\/p>\n<p><img decoding=\"async\" alt=\"Lihtsustame migreerimist OpenShift 3-lt OpenShift 4-le\" src=\"\/wp-content\/uploads\/2019\/08\/c5e2cd72465d7ba096ab225bff1e3c42.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Kokku<\/h3>\n<p>\nOpenShift 4 on suur samm edasi, eelk\u00f5ige t\u00e4nu uuele muutumatule arhitektuurile ja Operator-p\u00f5hisele mudelile, mis automatiseerib keeruliste rakenduste ja platvormide konfigureerimist klastrikeskkondades. Appranix pakub OpenShift kasutajatele lihtsat ja mugavat viisi OpenShift 4-le \u00fcleminekuks oma pilvep\u00f5hise rakenduse taastamise platvormiga. <\/p>\n<p><b>Appranixi lahendust saab kasutada otse <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 \/>Allikas: <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 4.9.10 - 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. \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\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\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. \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\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/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\udd47Lihtsustatud migreerimine OpenShift 3-lt OpenShift 4-le | ProHoster","description":"Nii, Red Hat OpenShift 4 platvorm on ametlikult turule toodud. T\u00e4na r\u00e4\u00e4gime, kuidas sellele liikuda OpenShift Container Platform 3-st v\u00f5imalikult kiiresti ja lihtsalt. Selle artikli kontekstis keskendume peamiselt uutele OpenShift 4 klastritele, mis kasutavad nutikat ja muutumatut (immutable \u2013 k\u00f5ikides juurutamiskeskkondades \u00fchesugust) infrastruktuuri, mis p\u00f5hineb RHEL CoreOS-il.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/uproshhaem-migratsiyu-s-openshift-3-na-openshift-4","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\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. \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","og:url":"https:\/\/prohoster.info\/et\/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"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/37204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=37204"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/37204\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/27897"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=37204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=37204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=37204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}