{"id":74086,"date":"2020-03-14T02:42:31","date_gmt":"2020-03-13T23:42:31","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/chto-novogo-v-red-hat-openshift-4-2-i-4-3"},"modified":"2020-03-14T02:42:31","modified_gmt":"2020-03-13T23:42:31","slug":"chto-novogo-v-red-hat-openshift-4-2-i-4-3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/chto-novogo-v-red-hat-openshift-4-2-i-4-3","title":{"rendered":"\u010co je nov\u00e9 v Red Hat OpenShift 4.2 a 4.3?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"\u010co
\n\u0160tvrt\u00e1 verzia OpenShift bola vydan\u00e1 relat\u00edvne ned\u00e1vno. Aktu\u00e1lna verzia 4.3 je dostupn\u00e1 od konca janu\u00e1ra a v\u0161etky zmeny v nej s\u00fa bu\u010f nie\u010do \u00faplne nov\u00e9, \u010do v tretej verzii neexistovalo, alebo ve\u013ek\u00e1 aktualiz\u00e1cia toho, \u010do sa objavilo vo verzii 4.1. V\u0161etko, \u010do teraz poviem, je potrebn\u00e9 vedie\u0165, ch\u00e1pa\u0165 a zoh\u013eadni\u0165 pre t\u00fdch, ktor\u00ed pracuj\u00fa s OpenShift a pl\u00e1nuj\u00fa prechod na nov\u00fa verziu.<\/p>\n

S vydan\u00edm verzie OpenShift 4.2 Red Hat zjednodu\u0161ila pr\u00e1cu s Kubernetes. Objavili sa nov\u00e9 n\u00e1stroje a pluginy na vytv\u00e1ranie kontajnerov, CI\/CD tokov a serverless nasaden\u00ed. Tieto novinky d\u00e1vaj\u00fa v\u00fdvoj\u00e1rom mo\u017enos\u0165 s\u00fastredi\u0165 sa na p\u00edsanie k\u00f3du, a nie na vysporiadanie sa s Kubernetes.<\/p>\n

\u010co vlastne je nov\u00e9 vo verzi\u00e1ch OpenShift 4.2 a 4.3?
\n<\/a><\/noindex><\/p>\n

Pohyb smerom k hybridn\u00fdm cloudom <\/h2>\n

\nPri pl\u00e1novan\u00ed novej IT infra\u0161trukt\u00fary alebo pri rozvoji existuj\u00facej IT krajiny spolo\u010dnosti \u010doraz \u010dastej\u0161ie zva\u017euj\u00fa cloudov\u00fd pr\u00edstup pri poskytovan\u00ed IT zdrojov, na \u010do realizuj\u00fa s\u00fakromn\u00e9 cloudov\u00e9 rie\u0161enia, alebo vyu\u017e\u00edvaj\u00fa kapacity verejn\u00fdch cloudov\u00fdch poskytovate\u013eov. Takto sa modern\u00e9 IT infra\u0161trukt\u00fary \u010doraz \u010dastej\u0161ie buduj\u00fa na \u201ehybridnom\u201c cloudovom modeli, kde sa pou\u017e\u00edvaj\u00fa ako on-premises zdroje, tak aj verejn\u00e9 cloudov\u00e9 zdroje s jedn\u00fdm syst\u00e9mom spr\u00e1vy. Red Hat OpenShift 4.2 je navrhnut\u00fd tak, aby u\u013eah\u010dil prechod na model hybridn\u00e9ho cloudu a umo\u017e\u0148uje jednoducho pripoji\u0165 k klastru zdroje od poskytovate\u013eov ako AWS, Azure a Google Cloud Platform spolu s pou\u017e\u00edvan\u00edm s\u00fakromn\u00fdch cloudov na VMware a OpenStack.<\/p>\n

Nov\u00fd pr\u00edstup k in\u0161tal\u00e1cii<\/h2>\n

\nVo \u0161tvrtej verzii sa zmenil pr\u00edstup k in\u0161tal\u00e1cii OpenShift. Red Hat poskytuje \u0161peci\u00e1lny n\u00e1stroj na nasadenie klastrov OpenShift \u2013 openshift-install. N\u00e1stroj je jedin\u00fd bin\u00e1rny s\u00fabor nap\u00edsan\u00fd v Go. Openshift-in\u0161tal\u00e1tor pripravuje yaml s\u00fabor s konfigur\u00e1ciou potrebnou na nasadenie. <\/p>\n

Pri in\u0161tal\u00e1cii s pou\u017eit\u00edm cloudov\u00fdch zdrojov bude potrebn\u00e9 uvies\u0165 minim\u00e1lne inform\u00e1cie o bud\u00facom klastre: DNS z\u00f3nu, po\u010det worker uzlov, \u0161pecifick\u00e9 nastavenia pre cloudov\u00e9ho poskytovate\u013ea, \u00fadaje o \u00fa\u010dte na pr\u00edstup k poskytovate\u013eovi cloudu. Po pr\u00edprave konfigura\u010dn\u00e9ho s\u00faboru m\u00f4\u017ee by\u0165 klaster nasaden\u00fd jedn\u00fdm pr\u00edkazom.<\/p>\n

Ak in\u0161talujete na vlastn\u00fdch v\u00fdpo\u010dtov\u00fdch zdrojoch, napr\u00edklad pri pou\u017eit\u00ed priv\u00e1tneho cloudu (podporovan\u00e9 s\u00fa vSphere a OpenStack) alebo pri in\u0161tal\u00e1cii na servery bare metal, bude potrebn\u00e9 manu\u00e1lne nastavi\u0165 infra\u0161trukt\u00faru - pripravi\u0165 minim\u00e1lny po\u010det virtu\u00e1lnych strojov alebo fyzick\u00fdch serverov potrebn\u00fdch na vytvorenie Control Plane klastra a nastavi\u0165 sie\u0165ov\u00e9 slu\u017eby. Po tejto konfigur\u00e1cii bude mo\u017en\u00e9 klastra OpenShift vytvori\u0165 rovnak\u00fdm sp\u00f4sobom jedn\u00fdm pr\u00edkazom n\u00e1stroja openshift-installer.<\/p>\n

Aktualiz\u00e1cie v infra\u0161trukt\u00fare<\/h2>\n

<\/p>\n

Integr\u00e1cia s CoreOS<\/h4>\n

\nK\u013e\u00fa\u010dov\u00e1 aktualiz\u00e1cia - to je integr\u00e1cia s Red Hat CoreOS. Teraz m\u00f4\u017eu master uzly Red Hat OpenShift fungova\u0165 iba<\/strong> na novej OS. Ide o bezplatn\u00fd opera\u010dn\u00fd syst\u00e9m od Red Hat, ktor\u00fd je \u0161peci\u00e1lne ur\u010den\u00fd pre kontajnerov\u00e9 rie\u0161enia. Red Hat CoreOS predstavuje zjednodu\u0161en\u00fd Linux, optimalizovan\u00fd pre sp\u00fa\u0161\u0165anie kontajnerov.<\/p>\n

Ak v 3.11 bola opera\u010dn\u00e1 s\u00fastava a OpenShift oddelen\u00e9, v 4.2 s\u00fa neoddelite\u013ene spojen\u00e9 s OpenShift. Teraz ide o jednotn\u00fd appliance - immutable infrastructure.<\/strong><\/p>\n

\"\u010co
\nPre klastra, ktor\u00e9 pou\u017e\u00edvaj\u00fa RHCOS pre v\u0161etky uzly, je aktualiz\u00e1cia OpenShift Container Platform jednoduch\u00fd a dobre automatizovan\u00fd proces. <\/p>\n

Predt\u00fdm, aby sa aktualizoval OpenShift, bolo potrebn\u00e9 najprv aktualizova\u0165 z\u00e1kladn\u00fa opera\u010dn\u00fa s\u00fastavu, na ktorej bol produkt spusten\u00fd (v tom \u010dase to bola Red Hat Enterprise Linux). A\u017e potom sa mohol OpenShift postupne aktualizova\u0165 uzol po uzle. O \u017eiadnej automatiz\u00e1cii procesu nebolo ani re\u010di. <\/p>\n

Teraz, ke\u010f OpenShift Container Platform \u00faplne kontroluje syst\u00e9my a slu\u017eby na ka\u017edom uzle, vr\u00e1tane OS, sa t\u00e1to \u00faloha rie\u0161i stla\u010den\u00edm tla\u010didla z webov\u00e9ho rozhrania. Potom sa sp\u00fa\u0161\u0165a \u0161peci\u00e1lny oper\u00e1tor vn\u00fatri klastra OpenShift, ktor\u00fd riadi cel\u00fd proces aktualiz\u00e1cie. <\/p>\n

Nov\u00fd CSI<\/h4>\n

\nDruh\u00e9 - nov\u00fd CSI - ovl\u00e1da\u010d storage rozhrania, ktor\u00fd umo\u017e\u0148uje pripoji\u0165 r\u00f4zne extern\u00e9 \u00falo\u017eisk\u00e1 k klastra OpenShift. Podporuje sa ve\u013ek\u00e9 mno\u017estvo poskytovate\u013eov storage ovl\u00e1da\u010dov pre OpenShift na z\u00e1klade storage ovl\u00e1da\u010dov, ktor\u00e9 p\u00ed\u0161u sami v\u00fdrobcovia \u00falo\u017en\u00fdch syst\u00e9mov. \u00dapln\u00fd zoznam podporovan\u00fdch CSI ovl\u00e1da\u010dov m\u00f4\u017eete n\u00e1js\u0165 v tomto dokumente: https:\/\/kubernetes-csi.github.io\/docs\/drivers.html<\/a><\/noindex>. V tomto zozname n\u00e1jdete v\u0161etky hlavn\u00e9 modely diskov\u00fdch pol\u00ed popredn\u00fdch v\u00fdrobcov (Dell\/EMC, IBM, NetApp, Hitachi, HPE, PureStorage), rie\u0161en\u00ed SDS (Ceph) a cloudov\u00fdch \u00falo\u017e\u00edsk (AWS, Azure, Google). OpenShift 4.2 podporuje pr\u00e1cu s CSI ovlada\u010dmi \u0161pecifik\u00e1cie CSI verzie 1.1.<\/p>\n

RedHat OpenShift Service Mesh<\/h4>\n

\nZalo\u017een\u00e1 na projektoch Istio, Kiali a Jaeger \u2014 Red Hat OpenShift Service Mesh umo\u017e\u0148uje, okrem be\u017en\u00fdch \u00faloh smerovania po\u017eiadaviek medzi slu\u017ebami, aj ich trasovanie a vizualiz\u00e1ciu. To pom\u00e1ha v\u00fdvoj\u00e1rom zjednodu\u0161i\u0165 spolupr\u00e1cu, monitorovanie a spr\u00e1vu aplik\u00e1cie nasadenej v Red Hat OpenShift. <\/p>\n

\"\u010co
\nVizualiz\u00e1cia aplik\u00e1cie s mikroslu\u017ebovou architekt\u00farou pomocou Kiali<\/i><\/p>\n

Aby sa procesy in\u0161tal\u00e1cie, slu\u017eby a spr\u00e1vy \u017eivotn\u00e9ho cyklu Service Mesh \u010do najviac zjednodu\u0161ili, Red Hat OpenShift poskytuje administr\u00e1torom \u0161peci\u00e1lneho oper\u00e1tora \u2013 Service Mesh Operator. Ide o oper\u00e1tora Kubernetes, ktor\u00fd umo\u017e\u0148uje nasadi\u0165 na klastre prekonavfigurovan\u00e9 bal\u00edky Istio, Kiali a Jaeger, \u010d\u00edm sa maxim\u00e1lne zni\u017euje administrat\u00edvna z\u00e1\u0165a\u017e spr\u00e1vy aplik\u00e1ci\u00ed.<\/p>\n

CRI-O namiesto Docker<\/h4>\n

\nPredvolen\u00fd kontajnerov\u00fd runtime Docker bol nahraden\u00fd CRI-O. Vyu\u017ei\u0165 CRI-O bolo mo\u017en\u00e9 u\u017e vo verzii 3.11, ale vo verzii 4.2 sa stal hlavn\u00fdm. Nie je to dobr\u00e9 ani zl\u00e9, ale je dobr\u00e9 ma\u0165 to na pam\u00e4ti pri pou\u017e\u00edvan\u00ed produktu.<\/p>\n

Oper\u00e1tori a nasadzovanie aplik\u00e1ci\u00ed<\/h2>\n

\nOper\u00e1tori s\u00fa novou entitou pre RedHat OpenShift, ktor\u00e1 sa objavila vo \u0161tvrtej verzii. Je to sp\u00f4sob balenia, nasadzovania a spr\u00e1vy aplik\u00e1cie Kubernetes. M\u00f4\u017ee to by\u0165 predstaven\u00e9 ako plugin pre aplik\u00e1cie, spravovan\u00fd pomocou API Kubernetes a n\u00e1strojov kubectl, pre aplik\u00e1cie nasaden\u00e9 v kontajneroch.<\/p>\n

Oper\u00e1tori Kubernetes pom\u00e1haj\u00fa automatizova\u0165 ak\u00e9ko\u013evek \u00falohy t\u00fdkaj\u00face sa administr\u00e1cie a spr\u00e1vy \u017eivotn\u00e9ho cyklu aplik\u00e1cie, ktor\u00fa nasadzujete vo svojom klastri. Napr\u00edklad, oper\u00e1tor m\u00f4\u017ee automatizova\u0165 aktualiz\u00e1cie, z\u00e1lohovanie a \u0161k\u00e1lovanie aplik\u00e1cie, meni\u0165 konfigur\u00e1ciu a pod. Kompletn\u00fd zoznam oper\u00e1torov si m\u00f4\u017eete pozrie\u0165 na https:\/\/operatorhub.io\/<\/a><\/noindex>.<\/p>\n

OperatorHub je dostupn\u00fd priamo z webov\u00e9ho rozhrania konzoly spr\u00e1vy. Predstavuje katal\u00f3g aplik\u00e1ci\u00ed pre OpenShift, podporovan\u00fd spolo\u010dnos\u0165ou Red Hat. T.j. v\u0161etky oper\u00e1tory schv\u00e1len\u00e9 spolo\u010dnos\u0165ou Red Hat bud\u00fa pokryt\u00e9 dod\u00e1vate\u013eskou podporou.<\/p>\n

\"\u010co
\nPort\u00e1l OperatorHub v konzole spr\u00e1vy OpenShift<\/i><\/p>\n

Univerz\u00e1lny z\u00e1kladn\u00fd obraz<\/h4>\n

\nToto je \u0161tandardizovan\u00fd s\u00fabor obrazov opera\u010dn\u00e9ho syst\u00e9mu RHEL, ktor\u00fd m\u00f4\u017eete pou\u017ei\u0165 na vytv\u00e1ranie svojich aplik\u00e1ci\u00ed v kontajneroch. Existuj\u00fa minim\u00e1lne, \u0161tandardn\u00e9 a \u00fapln\u00e9 sady. Zaberaj\u00fa ve\u013emi m\u00e1lo miesta, podporuj\u00fa v\u0161etky potrebn\u00e9 predin\u0161talovan\u00e9 bal\u00edky a programovacie jazyky.<\/p>\n

N\u00e1stroje CI\/CD<\/h4>\n

\nV RedHat OpenShift 4.2 sa objavila mo\u017enos\u0165 vybra\u0165 si medzi Jenkins a OpenShift Pipelines zalo\u017een\u00fdmi na Tekton Pipelines. <\/p>\n

OpenShift Pipelines je zalo\u017een\u00fd na Tekton, ktor\u00fd lep\u0161ie podporuje pr\u00edstupy Pipeline as Code a GitOps. V OpenShift pipelines ka\u017ed\u00e1 etapa prebieha v svojom vlastnom kontajneri, tak\u017ee zdroje sa pou\u017e\u00edvaj\u00fa iba po\u010das vykon\u00e1vania kroku. To poskytuje v\u00fdvoj\u00e1rom pln\u00fa kontrolu nad dod\u00e1vkov\u00fdmi kan\u00e1lmi modulov, pluginmi a spr\u00e1vou pr\u00edstupov bez centr\u00e1lneho servera CI\/CD.<\/p>\n

OpenShift Pipelines je moment\u00e1lne vo f\u00e1ze Preview pre v\u00fdvoj\u00e1rov a je dostupn\u00fd ako oper\u00e1tor na klastri OpenShift 4. Samozrejme, pou\u017e\u00edvatelia OpenShift m\u00f4\u017eu aj na\u010falej pou\u017e\u00edva\u0165 Jenkins v RedHat OpenShift 4.<\/p>\n

Aktualiz\u00e1cie v spr\u00e1ve pre v\u00fdvoj\u00e1rov<\/h2>\n

\nVo verzii 4.2 OpenShift plne obnovil webov\u00e9 rozhranie pre v\u00fdvoj\u00e1rov aj administr\u00e1torov.<\/p>\n

V predch\u00e1dzaj\u00facich verzi\u00e1ch OpenShift v\u0161etci pracovali v troch konzol\u00e1ch: servisn\u00fd katal\u00f3g, administr\u00e1torsk\u00e1 konzola a pracovn\u00e1 konzola. Teraz je klaster rozdelen\u00fd iba na dve \u010dasti - administr\u00e1torsk\u00fa konzolu a v\u00fdvojov\u00fa konzolu.<\/p>\n

V\u00fdvojov\u00e1 konzola z\u00edskala v\u00fdznamn\u00e9 vylep\u0161enia pou\u017e\u00edvate\u013esk\u00e9ho rozhrania. Teraz sa na nej pohodlnej\u0161ie zobrazuj\u00fa topol\u00f3gie aplik\u00e1ci\u00ed a ich zostaven\u00ed. To u\u013eah\u010duje v\u00fdvoj\u00e1rom vytv\u00e1ranie, nasadzovanie a vizualiz\u00e1ciu kontajnerov\u00fdch aplik\u00e1ci\u00ed a klastrov\u00fdch zdrojov. Umo\u017e\u0148uje im s\u00fastredi\u0165 sa na to, \u010do je pre nich d\u00f4le\u017eit\u00e9.<\/p>\n

\"\u010co
\nPort\u00e1l v\u00fdvoj\u00e1rov v konzole spr\u00e1vy OpenShift<\/i><\/p>\n

Odo<\/h4>\n

\nOdo je n\u00e1stroj pr\u00edkazov\u00e9ho riadku zameran\u00fd na v\u00fdvoj\u00e1rov, ktor\u00fd zjednodu\u0161uje v\u00fdvoj aplik\u00e1ci\u00ed v OpenShift. Pou\u017eit\u00edm interakcie v \u0161t\u00fdle git push tento CLI pom\u00e1ha v\u00fdvoj\u00e1rom, ktor\u00ed nie s\u00fa obozn\u00e1men\u00ed s Kubernetes, vytv\u00e1ra\u0165 aplik\u00e1cie v OpenShift.<\/p>\n

Integr\u00e1cia s prostrediami v\u00fdvoja<\/h4>\n

\nV\u00fdvoj\u00e1ri teraz m\u00f4\u017eu vytv\u00e1ra\u0165, ladenie a nasadzova\u0165 svoje aplik\u00e1cie v OpenShift bez opustenia svojho ob\u013e\u00faben\u00e9ho prostredia pre v\u00fdvoj k\u00f3du, ako s\u00fa Microsoft Visual Studio, JetBrains (vr\u00e1tane IntelliJ), Eclipse Desktop a \u010fal\u0161ie.<\/p>\n

Red Hat OpenShift Deployment extension for Microsoft Azure DevOps<\/h4>\n

\nObjavil se je raz\u0161iritev Red Hat OpenShift Deployment za Microsoft Azure DevOps. Zdaj lahko uporabniki tega sklopa orodij DevOps razporedijo svoje aplikacije v Azure Red Hat OpenShift ali katerikoli drug OpenShift grozd neposredno iz Microsoft Azure DevOps.<\/p>\n

Prehod s tretje na \u010detrto razli\u010dico<\/h2>\n

\nKer gre za novo razli\u010dico in ne za nadgradnjo, ni mogo\u010de preprosto nadgraditi \u010detrte razli\u010dice nad tretjo. Nadgradnja s tretje na \u010detrto razli\u010dico ne bo podprta.<\/strong>. <\/p>\n

Vendar pa je dobra novica: Red Hat nudi orodja za prenos projektov iz 3.7 v 4.2. S pomo\u010djo orodja Cluster Application Migration (CAM) lahko prenesete delovne obremenitve aplikacij. CAM omogo\u010da nadzor migracije in minimizira \u010das nedelovanja aplikacije.<\/p>\n

OpenShift 4.3<\/h2>\n

\nGlavne novosti, opisane v tem \u010dlanku, so se pojavile v razli\u010dici 4.2. V nedavno izdani 4.3 spremembe niso tako pomembne, a kljub temu so prisotne nekatere novosti. Seznam sprememb je precej obse\u017een, predstavili bomo najve\u010dje, kot jih vidimo:<\/p>\n

Posodobitev razli\u010dice Kubernetes na 1.16. <\/h4>\n

\nRazli\u010dica se je nadgradila kar za dva koraka, v OpenShift 4.2 je bila 1.14.<\/p>\n

\u0160ifriranje podatkov v etcd<\/h4>\n

\nZa\u010den\u0161i z razli\u010dico 4.3, je postala mogo\u010da \u0161ifra podatkov v bazi etcd. Po aktivaciji \u0161ifriranja bo mogo\u010de \u0161ifriranje naslednjih virov OpenShift API in Kubernetes API: Secrets, ConfigMaps, Routes, dostopni in OAuth avtentikacijski \u017eetoni.<\/p>\n

Helm<\/h4>\n

\nDodana je podpora za Helm 3 \u2013 priljubljen upravitelj paketov za Kubernetes. Zaenkrat ima podpora status TECHNOLOGY PREVIEW. V prihodnjih razli\u010dicah OpenShift bo podpora za Helm raz\u0161irjena na polno. Orodje helm cli je vklju\u010deno v OpenShift in ga je mogo\u010de prenesti iz spletne nadzorne plo\u0161\u010de za upravljanje grozda. <\/p>\n

Posodobitev Project Dashboard<\/h4>\n

\nV novi razli\u010dici Project Dashboard nudi dodatne informacije na strani projekta: status projekta, porabo virov in kvote za projekt.<\/p>\n

Prikaz ranljivosti za quay v spletni konzoli<\/h4>\n

\nV nadzorno plo\u0161\u010do je dodana funkcija za prikaz znanih ranljivosti za slike v repozitorijih Quay. Podpira prikaz ranljivosti za lokalne in zunanje repozitorije.<\/p>\n

Poenostavljeno ustvarjanje offline operatorhub<\/h4>\n

\nPre pr\u00edpad nasadenia klastrov OpenShift v izolovanej sieti, ktor\u00e9ho pr\u00edstup na internet je obmedzen\u00fd alebo neexistuje, sa u\u013eah\u010dilo vytv\u00e1ranie \u201ezrkadla\u201c pre registr\u00e1ciu OperatorHub. Teraz to bude mo\u017en\u00e9 vykona\u0165 iba tromi pr\u00edkazmi.<\/p>\n

Autori: <\/i>
\nViktor Pu\u010dkov, Jurij Semenjukov<\/i>
\n
Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0427\u0435\u0442\u0432\u0435\u0440\u0442\u0430\u044f \u0432\u0435\u0440\u0441\u0438\u044f OpenShift \u0432\u044b\u0448\u043b\u0430 \u0441\u0440\u0430\u0432\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u043d\u0435\u0434\u0430\u0432\u043d\u043e. \u0410\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u0430\u044f \u043d\u0430 \u0442\u0435\u043a\u0443\u0449\u0438\u0439 \u043c\u043e\u043c\u0435\u043d\u0442 \u0432\u0435\u0440\u0441\u0438\u044f 4.3 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0430 \u0441 \u043a\u043e\u043d\u0446\u0430 \u044f\u043d\u0432\u0430\u0440\u044f \u0438 \u0432\u0441\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0432 \u043d\u0435\u0439 \u2014 \u044d\u0442\u043e \u0438\u043b\u0438 \u043d\u0435\u0447\u0442\u043e \u0441\u043e\u0432\u0435\u0440\u0448\u0435\u043d\u043d\u043e \u043d\u043e\u0432\u043e\u0435, \u0447\u0435\u0433\u043e \u0432 \u0442\u0440\u0435\u0442\u044c\u0435\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u043d\u0435 \u0431\u044b\u043b\u043e, \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0442\u043e\u0433\u043e, \u0447\u0442\u043e \u043f\u043e\u044f\u0432\u0438\u043b\u043e\u0441\u044c \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 4.1. \u0412\u0441\u0435, \u0447\u0442\u043e \u043c\u044b \u0441\u0435\u0439\u0447\u0430\u0441 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u043c, \u043d\u0443\u0436\u043d\u043e \u0437\u043d\u0430\u0442\u044c, \u043f\u043e\u043d\u0438\u043c\u0430\u0442\u044c \u0438 \u0443\u0447\u0438\u0442\u044b\u0432\u0430\u0442\u044c \u0442\u0435\u043c, \u043a\u0442\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":74087,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-74086","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47\u010co je nov\u00e9 v Red Hat OpenShift 4.2 a 4.3? | ProHoster","description":"\u0160tvrt\u00e1 verzia OpenShift bola vydan\u00e1 relat\u00edvne ned\u00e1vno.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/chto-novogo-v-red-hat-openshift-4-2-i-4-3","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\u0427\u0442\u043e \u043d\u043e\u0432\u043e\u0433\u043e \u0432 Red Hat OpenShift 4.2 \u0438 4.3? | ProHoster","og:description":"\u0427\u0435\u0442\u0432\u0435\u0440\u0442\u0430\u044f \u0432\u0435\u0440\u0441\u0438\u044f OpenShift \u0432\u044b\u0448\u043b\u0430 \u0441\u0440\u0430\u0432\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u043e.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/chto-novogo-v-red-hat-openshift-4-2-i-4-3","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-03-13T23:42:31+00:00","article:modified_time":"2020-03-13T23:42:31+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"74086","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 18:21:22","updated":"2022-09-29 21:21:26","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\/74086","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=74086"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/74086\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/74087"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=74086"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=74086"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=74086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}