{"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\/cs\/blog\/administrirovanie\/chto-novogo-v-red-hat-openshift-4-2-i-4-3","title":{"rendered":"Co nov\u00e9ho v Red Hat OpenShift 4.2 a 4.3?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Co
\n\u010ctvrt\u00e1 verze OpenShift byla vyd\u00e1na pom\u011brn\u011b ned\u00e1vno. Aktu\u00e1ln\u00ed verze 4.3 je k dispozici od konce ledna a v\u0161echny zm\u011bny v n\u00ed jsou bu\u010f n\u011bco zcela nov\u00e9ho, co v t\u0159et\u00ed verzi nebylo, nebo velk\u00e9 aktualizace toho, co se objevilo ve verzi 4.1. V\u0161echno, co nyn\u00ed \u0159ekneme, je t\u0159eba zn\u00e1t, ch\u00e1pat a zohlednit t\u011bm, kte\u0159\u00ed pracuj\u00ed s OpenShift a pl\u00e1nuj\u00ed p\u0159echod na novou verzi.<\/p>\n

S vyd\u00e1n\u00edm verze OpenShift 4.2 Red Hat zjednodu\u0161il pr\u00e1ci s Kubernetes. Objevily se nov\u00e9 n\u00e1stroje a pluginy pro tvorbu kontejner\u016f, CI\/CD pipeline a serverless nasazen\u00ed. Novinky d\u00e1vaj\u00ed v\u00fdvoj\u00e1\u0159\u016fm mo\u017enost soust\u0159edit se na psan\u00ed k\u00f3du, nikoli na vy\u0159izov\u00e1n\u00ed z\u00e1le\u017eitost\u00ed s Kubernetes.<\/p>\n

Co nov\u00e9ho je ve verz\u00edch OpenShift 4.2 a 4.3?
\n<\/a><\/noindex><\/p>\n

Sm\u011b\u0159ov\u00e1n\u00ed k hybridn\u00edm cloud\u016fm <\/h2>\n

\nP\u0159i pl\u00e1nov\u00e1n\u00ed nov\u00e9 IT infrastruktury nebo p\u0159i rozvoji st\u00e1vaj\u00edc\u00edho IT prost\u0159ed\u00ed spole\u010dnosti st\u00e1le \u010dast\u011bji zva\u017euj\u00ed cloudov\u00fd p\u0159\u00edstup k poskytov\u00e1n\u00ed IT zdroj\u016f, k \u010demu\u017e realizuj\u00ed soukrom\u00e1 cloudov\u00e1 \u0159e\u0161en\u00ed, nebo vyu\u017e\u00edvaj\u00ed kapacity ve\u0159ejn\u00fdch cloudov\u00fdch poskytovatel\u016f. Modern\u00ed IT infrastruktury se tedy st\u00e1le \u010dast\u011bji buduj\u00ed podle \"hybridn\u00edho\" cloudov\u00e9ho modelu, ve kter\u00e9m se pou\u017e\u00edvaj\u00ed jak on-premises zdroje, tak ve\u0159ejn\u00e9 cloudov\u00e9 zdroje se spole\u010dn\u00fdm syst\u00e9mem \u0159\u00edzen\u00ed. Red Hat OpenShift 4.2 byl speci\u00e1ln\u011b navr\u017een tak, aby usnadnil p\u0159echod na model hybridn\u00edho cloudu a umo\u017enil snadn\u00e9 p\u0159ipojen\u00ed zdroj\u016f od poskytovatel\u016f jako AWS, Azure a Google Cloud Platform vedle pou\u017e\u00edv\u00e1n\u00ed soukrom\u00fdch cloud\u016f na VMware a OpenStack.<\/p>\n

Nov\u00fd p\u0159\u00edstup k instalaci<\/h2>\n

\nVe \u010dtvrt\u00e9 verzi se zm\u011bnil p\u0159\u00edstup k instalaci OpenShift. Red Hat poskytuje speci\u00e1ln\u00ed n\u00e1stroj pro nasazen\u00ed clusteru OpenShift \u2013 openshift-install. Tento n\u00e1stroj je jedin\u00fd bin\u00e1rn\u00ed soubor napsan\u00fd v Go. Openshift-installer p\u0159ipravuje yaml soubor s konfigurac\u00ed pot\u0159ebnou pro nasazen\u00ed. <\/p>\n

P\u0159i instalaci s vyu\u017eit\u00edm cloudov\u00fdch zdroj\u016f je t\u0159eba uv\u00e9st minim\u00e1ln\u00ed informace o budouc\u00edm clusteru: DNS z\u00f3nu, po\u010det pracovn\u00edk\u016f uzl\u016f, specifick\u00e1 nastaven\u00ed pro cloudov\u00e9ho poskytovatele a \u00fadaje \u00fa\u010dtu pro p\u0159\u00edstup k cloudov\u00e9mu poskytovateli. Po p\u0159\u00edprav\u011b konfigura\u010dn\u00edho souboru m\u016f\u017ee b\u00fdt cluster nasazen jedn\u00edm p\u0159\u00edkazem.<\/p>\n

V p\u0159\u00edpad\u011b instalace na vlastn\u00edch v\u00fdpo\u010detn\u00edch prost\u0159edc\u00edch, nap\u0159\u00edklad p\u0159i pou\u017eit\u00ed soukrom\u00e9ho cloudu (podporov\u00e1ny jsou vSphere a OpenStack) nebo p\u0159i instalaci na servery bare metal, bude vy\u017eadov\u00e1no ru\u010dn\u00ed nastaven\u00ed infrastruktury \u2013 p\u0159ipravit minim\u00e1ln\u00ed po\u010det virtu\u00e1ln\u00edch stroj\u016f nebo fyzick\u00fdch server\u016f pot\u0159ebn\u00fdch pro vytvo\u0159en\u00ed Control Plane clusteru a nakonfigurovat s\u00ed\u0165ov\u00e9 slu\u017eby. Po tomto nastaven\u00ed lze cluster OpenShift vytvo\u0159it jedn\u00edm p\u0159\u00edkazem utilitky openshift-installer.<\/p>\n

Aktualizace v infrastruktu\u0159e<\/h2>\n

<\/p>\n

Integrace s CoreOS<\/h4>\n

\nKl\u00ed\u010dov\u00e1 aktualizace \u2013 to je integrace s Red Hat CoreOS. Nyn\u00ed mohou master-nody Red Hat OpenShift fungovat pouze<\/strong> na nov\u00e9 opera\u010dn\u00edm syst\u00e9mu. Je to bezplatn\u00fd opera\u010dn\u00ed syst\u00e9m od Red Hat, kter\u00fd je ur\u010den speci\u00e1ln\u011b pro kontejnerov\u00e1 \u0159e\u0161en\u00ed. Red Hat CoreOS p\u0159edstavuje zjednodu\u0161en\u00fd Linux, optimalizovan\u00fd pro provoz kontejner\u016f.<\/p>\n

Pokud v 3.11 existoval opera\u010dn\u00ed syst\u00e9m a OpenShift odd\u011blen\u011b, pak ve verzi 4.2 je neodd\u011bliteln\u011b spojen s OpenShift. Nyn\u00ed je to jednotn\u00fd appliance \u2013 immutable infrastructure.<\/strong><\/p>\n

\"Co
\nPro clustery, kter\u00e9 pou\u017e\u00edvaj\u00ed RHCOS na v\u0161ech uzlech, je aktualizace OpenShift Container Platform jednoduch\u00fdm a dob\u0159e automatizovan\u00fdm procesem. <\/p>\n

D\u0159\u00edve bylo nutn\u00e9 nejprve aktualizovat z\u00e1kladn\u00ed opera\u010dn\u00ed syst\u00e9m, na kter\u00e9m byl produkt spu\u0161t\u011bn (tehdy to byla Red Hat Enterprise Linux), a teprve pot\u00e9 bylo mo\u017en\u00e9 postupn\u011b aktualizovat OpenShift, uzel po uzlu. O jak\u00e9koli automatizaci procesu nemohlo b\u00fdt ani \u0159e\u010di. <\/p>\n

Nyn\u00ed, proto\u017ee OpenShift Container Platform pln\u011b kontroluje syst\u00e9my a slu\u017eby na ka\u017ed\u00e9m uzlu, v\u010detn\u011b opera\u010dn\u00edho syst\u00e9mu, lze tuto \u00falohu vy\u0159e\u0161it stisknut\u00edm tla\u010d\u00edtka z webov\u00e9ho rozhran\u00ed. Pot\u00e9 se spust\u00ed speci\u00e1ln\u00ed oper\u00e1tor v r\u00e1mci clusteru OpenShift, kter\u00fd \u0159\u00edd\u00ed cel\u00fd proces aktualizace. <\/p>\n

Nov\u00fd CSI<\/h4>\n

\nDruh\u00e1 \u2013 nov\u00fd CSI \u2013 kontrol\u00e9r storage-interface, kter\u00fd umo\u017e\u0148uje p\u0159ipojit r\u016fzn\u00e9 extern\u00ed \u00falo\u017ei\u0161t\u011b k clusteru OpenShift. Podporov\u00e1no je velk\u00e9 mno\u017estv\u00ed poskytovatel\u016f storage-drivery pro OpenShift na z\u00e1klad\u011b storage-driver\u016f, kter\u00e9 p\u00ed\u0161\u00ed samotn\u00ed v\u00fdrobci \u00falo\u017ei\u0161\u0165. Kompletn\u00ed seznam podporovan\u00fdch CSI driver\u016f lze naj\u00edt v tomto dokumentu: https:\/\/kubernetes-csi.github.io\/docs\/drivers.html<\/a><\/noindex>. Tento seznam zahrnuje v\u0161echny hlavn\u00ed modely diskov\u00fdch pol\u00ed p\u0159edn\u00edch v\u00fdrobc\u016f (Dell\/EMC, IBM, NetApp, Hitachi, HPE, PureStorage), \u0159e\u0161en\u00ed SDS (Ceph) a cloudov\u00e9 \u00falo\u017ei\u0161t\u011b (AWS, Azure, Google). OpenShift 4.2 podporuje pr\u00e1ci s CSI ovlada\u010di specifikace CSI verze 1.1.<\/p>\n

RedHat OpenShift Service Mesh<\/h4>\n

\nZalo\u017een\u00fd na projektech Istio, Kiali a Jaeger \u2014 Red Hat OpenShift Service Mesh, krom\u011b b\u011b\u017en\u00fdch \u00faloh sm\u011brov\u00e1n\u00ed po\u017eadavk\u016f mezi slu\u017ebami, umo\u017e\u0148uje jejich trasov\u00e1n\u00ed a vizualizaci. To pom\u00e1h\u00e1 v\u00fdvoj\u00e1\u0159\u016fm zjednodu\u0161it interakci, sledov\u00e1n\u00ed a spr\u00e1vu aplikace nasazen\u00e9 uvnit\u0159 Red Hat OpenShift. <\/p>\n

\"Co
\nVizualizace aplikace s mikroslu\u017ebovou architekturou pomoc\u00ed Kiali<\/i><\/p>\n

Aby se co nejv\u00edce zjednodu\u0161ily procesy instalace, slu\u017eby a spr\u00e1vy \u017eivotn\u00edho cyklu Service Mesh, Red Hat OpenShift poskytuje administr\u00e1tor\u016fm speci\u00e1ln\u00edho oper\u00e1tora \u2013 Service Mesh Operator. Tento oper\u00e1tor Kubernetes umo\u017e\u0148uje nasadit na clusteru rekonfigurovan\u00e9 bal\u00ed\u010dky Istio, Kiali a Jaeger a minimalizuje administrativn\u00ed z\u00e1t\u011b\u017e spr\u00e1vy aplikac\u00ed.<\/p>\n

CRI-O m\u00edsto Dockeru<\/h4>\n

\nV\u00fdchoz\u00ed kontejnerov\u00fd runtime Docker byl nahrazen CRI-O. Vyu\u017eit\u00ed CRI-O bylo mo\u017en\u00e9 ji\u017e ve verzi 3.11, ale ve verzi 4.2 se stal hlavn\u00edm. Nen\u00ed to dobr\u00e9 ani \u0161patn\u00e9, ale je dobr\u00e9 to m\u00edt na pam\u011bti p\u0159i pou\u017e\u00edv\u00e1n\u00ed produktu.<\/p>\n

Oper\u00e1to\u0159i a nasazen\u00ed aplikac\u00ed<\/h2>\n

\nOper\u00e1to\u0159i \u2014 nov\u00e1 entita pro RedHat OpenShift, kter\u00e1 se objevila ve \u010dtvrt\u00e9 verzi. Je to metoda balen\u00ed, nasazen\u00ed a spr\u00e1vy aplikac\u00ed Kubernetes. M\u016f\u017eete to p\u0159edstavit jako plugin pro aplikace nasazen\u00e9 v kontejnerech \u0159\u00edzen\u00fd pomoc\u00ed API Kubernetes a n\u00e1stroj\u016f kubectl.<\/p>\n

Oper\u00e1to\u0159i Kubernetes pom\u00e1haj\u00ed automatizovat jak\u00e9koli \u00fakoly souvisej\u00edc\u00ed s administrac\u00ed a spr\u00e1vou \u017eivotn\u00edho cyklu aplikace, kterou nasazujete ve sv\u00e9m clusteru. Nap\u0159\u00edklad m\u016f\u017ee oper\u00e1tor automatizovat aktualizace, z\u00e1lohov\u00e1n\u00ed a \u0161k\u00e1lov\u00e1n\u00ed aplikace, m\u011bnit konfiguraci atd. \u00dapln\u00fd seznam oper\u00e1tor\u016f lze zobrazit na https:\/\/operatorhub.io\/<\/a><\/noindex>.<\/p>\n

OperatorHub je k dispozici p\u0159\u00edmo z webov\u00e9ho rozhran\u00ed \u0159\u00eddic\u00ed konzole. P\u0159edstavuje katalog aplikac\u00ed pro OpenShift, podporovan\u00fd Red Hat. Tedy v\u0161echny oper\u00e1tory schv\u00e1len\u00e9 Red Hat budou m\u00edt podporu od dodavatele.<\/p>\n

\"Co
\nPort\u00e1l OperatorHub v konzoli \u0159\u00edzen\u00ed OpenShift<\/i><\/p>\n

Univerz\u00e1ln\u00ed z\u00e1kladn\u00ed obraz<\/h4>\n

\nJedn\u00e1 se o standardizovanou sadu obraz\u016f opera\u010dn\u00edho syst\u00e9mu RHEL, kter\u00e9 lze pou\u017e\u00edt k vytv\u00e1\u0159en\u00ed va\u0161ich aplikac\u00ed v kontejnerech. Existuj\u00ed minim\u00e1ln\u00ed, standardn\u00ed a kompletn\u00ed sady. Tyto sady zaberou velmi m\u00e1lo m\u00edsta, podporuj\u00ed v\u0161echny pot\u0159ebn\u00e9 instalovan\u00e9 bal\u00ed\u010dky a programovac\u00ed jazyky.<\/p>\n

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

\nV RedHat OpenShift 4.2 se objevila mo\u017enost zvolit mezi Jenkins a OpenShift Pipelines zalo\u017een\u00fdmi na Tekton Pipelines. <\/p>\n

OpenShift Pipelines je zalo\u017een na Tektonu, kter\u00fd l\u00e9pe podporuje p\u0159\u00edstupy Pipeline as Code a GitOps. V konvoj\u00edch OpenShift se ka\u017ed\u00fd krok prov\u00e1d\u00ed v samostatn\u00e9m kontejneru, tak\u017ee zdroje se vyu\u017e\u00edvaj\u00ed pouze b\u011bhem prov\u00e1d\u011bn\u00ed kroku. To d\u00e1v\u00e1 v\u00fdvoj\u00e1\u0159\u016fm plnou kontrolu nad doru\u010dovac\u00edmi konvoji modul\u016f, pluginy a kontrolou p\u0159\u00edstupu bez centr\u00e1ln\u00edho serveru CI\/CD pro \u0159\u00edzen\u00ed.<\/p>\n

OpenShift Pipelines je v sou\u010dasnosti ve f\u00e1zi Preview pro v\u00fdvoj\u00e1\u0159e a je dostupn\u00fd jako operator na cloudu OpenShift 4. Samoz\u0159ejm\u011b, u\u017eivatel\u00e9 OpenShift st\u00e1le mohou pou\u017e\u00edvat Jenkins v RedHat OpenShift 4.<\/p>\n

Aktualizace v \u0159\u00edzen\u00ed pro v\u00fdvoj\u00e1\u0159e<\/h2>\n

\nVe verzi 4.2 OpenShift pro\u0161el kompletn\u00ed obnovou webov\u00e9ho rozhran\u00ed jak pro v\u00fdvoj\u00e1\u0159e, tak pro spr\u00e1vce.<\/p>\n

V p\u0159edchoz\u00edch verz\u00edch OpenShift v\u0161ichni pracovali ve t\u0159ech konzol\u00edch: katalog slu\u017eby, konzole spr\u00e1vce a pracovn\u00ed konzole. Nyn\u00ed je cluster rozd\u011blen pouze na dv\u011b \u010d\u00e1sti \u2014 konzole spr\u00e1vce a konzole v\u00fdvoj\u00e1\u0159e.<\/p>\n

Konzole v\u00fdvoj\u00e1\u0159e z\u00edskala v\u00fdznamn\u00e1 zlep\u0161en\u00ed u\u017eivatelsk\u00e9ho rozhran\u00ed. Nyn\u00ed l\u00e9pe zobrazuje topologie aplikac\u00ed a jejich sestaven\u00ed. To usnad\u0148uje v\u00fdvoj\u00e1\u0159\u016fm vytv\u00e1\u0159et, nasazovat a vizualizovat kontejnerov\u00e9 aplikace a clusterov\u00e9 zdroje. Umo\u017e\u0148uje se soust\u0159edit na to, co je pro n\u011b d\u016fle\u017eit\u00e9.<\/p>\n

\"Co
\nPort\u00e1l v\u00fdvoj\u00e1\u0159e v konzole \u0159\u00edzen\u00ed OpenShift<\/i><\/p>\n

Odo<\/h4>\n

\nOdo je n\u00e1stroj p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku zam\u011b\u0159en\u00fd na v\u00fdvoj\u00e1\u0159e, kter\u00fd usnad\u0148uje v\u00fdvoj aplikac\u00ed v OpenShift. D\u00edky interakci ve stylu git push pom\u00e1h\u00e1 tento CLI v\u00fdvoj\u00e1\u0159\u016fm, kte\u0159\u00ed nejsou obezn\u00e1meni s Kubernetes, vytv\u00e1\u0159et aplikace v OpenShift.<\/p>\n

Integrace s v\u00fdvojov\u00fdmi prost\u0159ed\u00edmi<\/h4>\n

\nV\u00fdvoj\u00e1\u0159i nyn\u00ed mohou vytv\u00e1\u0159et, ladit a nasazovat sv\u00e9 aplikace v OpenShift, ani\u017e by opustili sv\u00e9 obl\u00edben\u00e9 v\u00fdvojov\u00e9 prost\u0159ed\u00ed k\u00f3du, nap\u0159\u00edklad Microsoft Visual Studio, JetBrains (v\u010detn\u011b IntelliJ), Eclipse Desktop atd.<\/p>\n

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

\nBylo vyd\u00e1no roz\u0161\u00ed\u0159en\u00ed Red Hat OpenShift Deployment pro Microsoft Azure DevOps. Nyn\u00ed mohou u\u017eivatel\u00e9 t\u00e9to sady n\u00e1stroj\u016f DevOps nasazovat sv\u00e9 aplikace do Azure Red Hat OpenShift nebo jak\u00e9hokoli jin\u00e9ho clustru OpenShift p\u0159\u00edmo z Microsoft Azure DevOps.<\/p>\n

P\u0159echod z t\u0159et\u00ed verze na \u010dtvrtou<\/h2>\n

\nJeliko\u017e se jedn\u00e1 o nov\u00e9 vyd\u00e1n\u00ed, nikoli o aktualizaci, nen\u00ed mo\u017en\u00e9 prost\u011b nainstalovat \u010dtvrtou verzi jako p\u0159ekryv t\u0159et\u00ed. Aktualizace z t\u0159et\u00ed na \u010dtvrtou verzi nebude podporov\u00e1na<\/strong>. <\/p>\n

Ale je zde tak\u00e9 dobr\u00e1 zpr\u00e1va: Red Hat poskytuje n\u00e1stroje pro migraci projekt\u016f z 3.7 do 4.2. M\u016f\u017eete migrovat pracovn\u00ed z\u00e1t\u011b\u017ee aplikac\u00ed pomoc\u00ed n\u00e1stroje Cluster Application Migration (CAM). CAM umo\u017e\u0148uje \u0159\u00eddit migraci a minimalizovat prostoje aplikace.<\/p>\n

OpenShift 4.3<\/h2>\n

\nHlavn\u00ed novinky popsan\u00e9 v tomto \u010dl\u00e1nku se objevily ve verzi 4.2. V ned\u00e1vno vydan\u00e9 4.3 nejsou zm\u011bny tak z\u00e1sadn\u00ed, ale st\u00e1le existuje n\u011bco nov\u00e9ho. Seznam zm\u011bn je dost rozs\u00e1hl\u00fd, zde uv\u00e1d\u00edme ty nejv\u00fdznamn\u011bj\u0161\u00ed podle na\u0161eho n\u00e1zoru:<\/p>\n

Aktualizace verze Kubernetes na 1.16. <\/h4>\n

\nVerze byla upgradov\u00e1na o dva kroky, v OpenShift 4.2 byla 1.14.<\/p>\n

\u0160ifrov\u00e1n\u00ed dat v etcd<\/h4>\n

\nOd verze 4.3 je k dispozici mo\u017enost \u0161ifrov\u00e1n\u00ed dat v datab\u00e1zi etcd. Po aktivaci \u0161ifrov\u00e1n\u00ed bude mo\u017en\u00e9 \u0161ifrovat n\u00e1sleduj\u00edc\u00ed zdroje OpenShift API a Kubernetes API: Secrets, ConfigMaps, Routes, tokeny pro p\u0159\u00edstup a autorizaci OAuth.<\/p>\n

Helm<\/h4>\n

\nByla p\u0159id\u00e1na podpora Helm 3 \u2013 popul\u00e1rn\u00edho spr\u00e1vce bal\u00ed\u010dk\u016f pro Kubernetes. Zat\u00edm m\u00e1 podpora status TECHNOLOGY PREVIEW. V budouc\u00edch verz\u00edch OpenShift bude podpora Helmu roz\u0161\u00ed\u0159ena na plnou. N\u00e1stroj helm cli je dod\u00e1v\u00e1n s OpenShift a lze jej st\u00e1hnout z webov\u00e9 konzole pro spr\u00e1vu clustru. <\/p>\n

Aktualizace Project Dashboard<\/h4>\n

\nV nov\u00e9 verzi Project Dashboard poskytuje dal\u0161\u00ed informace na str\u00e1nce projektu: stav projektu, vyu\u017eit\u00ed zdroj\u016f a kv\u00f3ty pro projekt.<\/p>\n

Zobrazen\u00ed zranitelnost\u00ed pro quay v Web-console<\/h4>\n

\nDo administra\u010dn\u00ed konzole byla p\u0159id\u00e1na funkce zobrazen\u00ed zn\u00e1m\u00fdch zranitelnost\u00ed pro obrazy v repozit\u00e1\u0159\u00edch Quay. Podporuje se zobrazen\u00ed zranitelnost\u00ed pro m\u00edstn\u00ed a extern\u00ed repozit\u00e1\u0159e.<\/p>\n

Zjednodu\u0161en\u00ed vytvo\u0159en\u00ed offline operatorhub<\/h4>\n

\nV p\u0159\u00edpad\u011b nasazen\u00ed cloudu OpenShift v izolovan\u00e9 s\u00edti, kde je p\u0159\u00edstup k internetu omezen\u00fd nebo zcela chyb\u00ed, se usnadnilo vytv\u00e1\u0159en\u00ed \u201ezrcadla\u201c pro registr OperatorHub. Nyn\u00ed to bude mo\u017en\u00e9 ud\u011blat pouze t\u0159emi p\u0159\u00edkazy.<\/p>\n

Auto\u0159i: <\/i>
\nViktor Pu\u010dkov, Jurij Semenjuk<\/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\udd47Co je nov\u00e9ho v Red Hat OpenShift 4.2 a 4.3? | ProHoster","description":"\u010ctvrt\u00e1 verze OpenShift byla vyd\u00e1na relativn\u011b ned\u00e1vno.","canonical_url":"https:\/\/prohoster.info\/cs\/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":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/74086","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=74086"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/74086\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/74087"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=74086"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=74086"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=74086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}