{"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\/sq\/blog\/administrirovanie\/chto-novogo-v-red-hat-openshift-4-2-i-4-3","title":{"rendered":"\u00c7far\u00eb ka t\u00eb re n\u00eb Red Hat OpenShift 4.2 dhe 4.3?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"\u00c7far\u00eb
\nVersioni e kat\u00ebrt e OpenShift u publikua relativisht koh\u00ebt e fundit. Versioni aktual, 4.3, \u00ebsht\u00eb n\u00eb dispozicion q\u00eb nga fundi i janarit dhe t\u00eb gjitha ndryshimet e saj jan\u00eb ose di\u00e7ka krejt\u00ebsisht e re q\u00eb nuk ishte n\u00eb versionin e tret\u00eb, ose nj\u00eb p\u00ebrdit\u00ebsim i madh i asaj q\u00eb u paraqit n\u00eb versionin 4.1. Gjith\u00e7ka q\u00eb do t\u00eb diskutojm\u00eb tani \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb dihet, t\u00eb kuptohet dhe t\u00eb merret parasysh nga ata q\u00eb punojn\u00eb me OpenShift dhe planifikojn\u00eb t\u00eb kalojn\u00eb n\u00eb versionin e ri.<\/p>\n

Me publikimin e versionit OpenShift 4.2, Red Hat e leht\u00ebsoi pun\u00ebn me Kubernetes. U paraqit\u00ebn mjete dhe plug-ins t\u00eb reja p\u00ebr krijimin e kontejner\u00ebve, pipeline-ve CI\/CD dhe implementimeve serverless. Risi t\u00eb tilla i japin zhvilluesve mund\u00ebsin\u00eb t\u00eb p\u00ebrqendrohen n\u00eb shkrimin e kodit, dhe jo n\u00eb p\u00ebrballjen me Kubernetes.<\/p>\n

\u00c7far\u00eb ka t\u00eb re n\u00eb versionet OpenShift 4.2 dhe 4.3?
\n<\/a><\/noindex><\/p>\n

L\u00ebvizja drejt mjeteve hibrid <\/h2>\n

\nGjate planifikimit t\u00eb nj\u00eb infrastrukture IT-t\u00eb re ose n\u00eb zhvillimin e peizazhit ekzistues t\u00eb IT-s\u00eb, kompanit\u00eb gjithnj\u00eb e m\u00eb shum\u00eb shqyrtojn\u00eb qasjen cloud n\u00eb ofrimin e burimeve IT, p\u00ebr t\u00eb cilat realizojn\u00eb zgjidhje shume private ose p\u00ebrdorin kapacitetet e ofruesve publik\u00eb t\u00eb cloud. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, infrastruktura moderne IT gjithnj\u00eb e m\u00eb shum\u00eb nd\u00ebrtohet mbi modelin \u2018hibrid\u2019 cloud, ku p\u00ebrdoren si burime on-premises ashtu edhe burime publike cloud me nj\u00eb sistem t\u00eb p\u00ebrbashk\u00ebt menaxhimi. Red Hat OpenShift 4.2 \u00ebsht\u00eb projektuar posa\u00e7\u00ebrisht p\u00ebr t\u00eb thjeshtuar kalimin n\u00eb modelin e cloud-it hibrid dhe lejon lidhjen e leht\u00eb t\u00eb burimeve nga ofrues t\u00eb till\u00eb si AWS, Azure dhe Google Cloud Platform p\u00ebrve\u00e7 p\u00ebrdorimit t\u00eb cloud-\u00ebve privat\u00eb n\u00eb VMware dhe OpenStack.<\/p>\n

Qasja e re n\u00eb instalim<\/h2>\n

\nN\u00eb versionin 4, qasja n\u00eb instalimet OpenShift ka ndryshuar. Red Hat ofron nj\u00eb utilitar t\u00eb ve\u00e7ant\u00eb p\u00ebr vendosjen e klasterit OpenShift \u2013 openshift-install. Ky utilitar \u00ebsht\u00eb nj\u00eb skedar binar i vet\u00ebm i shkruar n\u00eb Go. Openshift-installer p\u00ebrgatit nj\u00eb skedar yaml me konfigurimin e nevojsh\u00ebm p\u00ebr vendosjen. <\/p>\n

N\u00eb rastin e instalimit duke p\u00ebrdorur burime cloud, do t\u00eb k\u00ebrkohet t\u00eb jepet informata minimale n\u00eb lidhje me klasterin e ardhsh\u00ebm: zona DNS, numri i nod\u00ebve punonj\u00ebs, p\u00ebrshtatje specifike p\u00ebr ofruesin e cloud dhe t\u00eb dh\u00ebnat e llogaris\u00eb p\u00ebr aksesin n\u00eb ofruesin e cloud. Pasi t\u00eb p\u00ebrgatitet skedari i konfigurimit, klasteri mund t\u00eb vendoset me nj\u00eb komand\u00eb.<\/p>\n

N\u00eb rastin e instalimit n\u00eb burime t\u00eb veta kompjuterike, p\u00ebr shembull, duke p\u00ebrdorur nj\u00eb cloud privat (p\u00ebrkrah vSphere dhe OpenStack) ose n\u00eb servera bare metal, do t\u00eb jet\u00eb e nevojshme t\u00eb konfigurohet manualisht infrastruktura - p\u00ebr t\u00eb p\u00ebrgatitur numrin minimal t\u00eb makinave virtuelle ose server\u00ebve fizik\u00eb t\u00eb nevojsh\u00ebm p\u00ebr krijimin e klasterit Control Plane dhe p\u00ebr t\u00eb konfiguruar sh\u00ebrbimet rrjet. Pas nj\u00eb konfigurations t\u00eb till\u00eb, klasteri OpenShift mund t\u00eb krijohet ashtu si\u00e7 \u00ebsht\u00eb nj\u00eb komand\u00eb e utils openshift-installer.<\/p>\n

P\u00ebrdit\u00ebsimet n\u00eb infrastruktur\u00eb<\/h2>\n

<\/p>\n

Integrimi me CoreOS<\/h4>\n

\nP\u00ebrdit\u00ebsimi ky\u00e7 \u00ebsht\u00eb integrimi me Red Hat CoreOS. Tani master-nodet e Red Hat OpenShift mund t\u00eb funksionojn\u00eb t\u00eb<\/strong> n\u00eb nj\u00eb sistem t\u00eb ri operativ. Ky \u00ebsht\u00eb nj\u00eb sistem operativ falas nga Red Hat, i cili \u00ebsht\u00eb krijuar posa\u00e7\u00ebrisht p\u00ebr zgjidhjet e konteiner\u00ebve. Red Hat CoreOS \u00ebsht\u00eb nj\u00eb Linux i leht\u00ebsuar, i optimizuar p\u00ebr t\u00eb ekzekutuar konteiner\u00eb.<\/p>\n

N\u00eb versionin 3.11, sistemi operativ dhe OpenShift ekzistonin ndaras, por n\u00eb 4.2 ato jan\u00eb t\u00eb lidhura n\u00eb m\u00ebnyr\u00eb t\u00eb pandashme me OpenShift. Tani \u00ebsht\u00eb nj\u00eb pajisje e vetme - infrastruktura e pandryshueshme.<\/strong><\/p>\n

\"\u00c7far\u00eb
\nP\u00ebr klaster\u00ebt q\u00eb p\u00ebrdorin RHCOS p\u00ebr t\u00eb gjitha nodet, p\u00ebrdit\u00ebsimi i OpenShift Container Platform \u00ebsht\u00eb nj\u00eb proces i leht\u00eb dhe i automatizuar mir\u00eb. <\/p>\n

M\u00eb par\u00eb, p\u00ebr t\u00eb p\u00ebrdit\u00ebsuar OpenShift, ishte e nevojshme s\u00eb pari t\u00eb p\u00ebrdit\u00ebsohej sistemi themelor operativ, mbi t\u00eb cilin prodhimi ishte nisur (n\u00eb at\u00eb koh\u00eb ky ishte Red Hat Enterprise Linux). Vet\u00ebm pas k\u00ebsaj mund t\u00eb p\u00ebrdit\u00ebsohej OpenShift gradualisht, nod nga nod. Nuk kishte asnj\u00eb automatizim t\u00eb procesit. <\/p>\n

Tani, p\u00ebrsa koh\u00eb q\u00eb OpenShift Container Platform kontrollon plot\u00ebsisht sistemet dhe sh\u00ebrbimet n\u00eb \u00e7do nod, duke p\u00ebrfshir\u00eb sistemin operativ, kjo detyr\u00eb zgjidhet me nj\u00eb klik n\u00eb nd\u00ebrfaqen e internetit. Pas k\u00ebsaj, fillon nj\u00eb operator special brenda klasterit OpenShift, i cili menaxhon t\u00eb gjith\u00eb procesin e p\u00ebrdit\u00ebsimit. <\/p>\n

CSI i ri<\/h4>\n

\nE dyta \u00ebsht\u00eb CSI i ri - kontrolluesi i interfes\u00ebs storage, i cili lejon lidhjen e ndryshme t\u00eb sistemit t\u00eb ruajtjes me klasterin OpenShift. Mb\u00ebshtetet nj\u00eb num\u00ebr i madh ofruesish t\u00eb drivrave storage p\u00ebr OpenShift, bazuar n\u00eb drivar\u00ebt storage q\u00eb shkruhen nga vet\u00eb prodhuesit e sistemeve t\u00eb ruajtjes. Lista e plot\u00eb e drivar\u00ebve CSI t\u00eb mb\u00ebshtetur mund t\u00eb gjendet n\u00eb k\u00ebt\u00eb dokument: https:\/\/kubernetes-csi.github.io\/docs\/drivers.html<\/a><\/noindex>. N\u00eb k\u00ebt\u00eb list\u00eb mund t\u00eb gjeni t\u00eb gjitha modelet kryesore t\u00eb grupeve t\u00eb disqeve t\u00eb prodhuesve kryesor\u00eb (Dell\/EMC, IBM, NetApp, Hitachi, HPE, PureStorage), zgjidhjeve SDS (Ceph) dhe ruajtjeve n\u00eb re (AWS, Azure, Google). OpenShift 4.2 mb\u00ebshtet pun\u00ebn me drejtuesit CSI sipas specifikacionit CSI versioni 1.1.<\/p>\n

RedHat OpenShift Service Mesh<\/h4>\n

\nE bazuar n\u00eb projektet Istio, Kiali dhe Jaeger \u2014 Red Hat OpenShift Service Mesh, p\u00ebrve\u00e7 detyrave t\u00eb zakonshme t\u00eb orientimit t\u00eb k\u00ebrkesave midis sh\u00ebrbimeve, lejon gjithashtu gjurmimin dhe vizualizimin e tyre. Kjo ndihmon zhvilluesit t\u00eb thjeshtojn\u00eb nd\u00ebrlidhjen, v\u00ebzhgimin dhe menaxhimin e aplikacioneve t\u00eb implementuara brenda Red Hat OpenShift. <\/p>\n

\"\u00c7far\u00eb
\nVizualizimi i nj\u00eb aplikacioni me arkitektur\u00eb mikrosh\u00ebrbimesh me p\u00ebrdorimin e Kiali<\/i><\/p>\n

P\u00ebr t\u00eb thjesht\u00ebsuar maksimalisht proceset e instalimit, sh\u00ebrbimit dhe menaxhimit t\u00eb ciklit t\u00eb jet\u00ebs s\u00eb Service Mesh, Red Hat OpenShift u ofron administrator\u00ebve nj\u00eb operator special \u2013 Service Mesh Operator. Ky \u00ebsht\u00eb nj\u00eb operator Kubernetes q\u00eb lejon implementimin n\u00eb klaster paketash t\u00eb rikonfiguruara Istio, Kiali dhe Jaeger, duke e reduktuar sa m\u00eb shum\u00eb ngarkes\u00ebn administrative n\u00eb menaxhimin e aplikacioneve.<\/p>\n

CRI-O n\u00eb vend t\u00eb Docker<\/h4>\n

\nRuntime-container default Docker u z\u00ebvend\u00ebsua me CRI-O. CRI-O mund t\u00eb p\u00ebrdorej q\u00eb n\u00eb versionin 3.11, por n\u00eb 4.2 ai u b\u00eb kryesor. Nuk \u00ebsht\u00eb mir\u00eb dhe as keq, por merret parasysh gjat\u00eb p\u00ebrdorimit t\u00eb produktit.<\/p>\n

Operator\u00ebt dhe implementimi i aplikacioneve<\/h2>\n

\nOperator\u00ebt \u2014 nj\u00eb entitet i ri p\u00ebr RedHat OpenShift, q\u00eb u shfaq n\u00eb versionin e kat\u00ebrt. Ky \u00ebsht\u00eb nj\u00eb metod\u00eb p\u00ebr paketimin, implementimin dhe menaxhimin e aplikacioneve Kubernetes. Mund t\u00eb p\u00ebrfytyrohet si nj\u00eb plugin p\u00ebr aplikacionet e implementuara n\u00eb kontejner\u00eb, i menaxhuar me API-n\u00eb e Kubernetes dhe mjetet kubectl.<\/p>\n

Operator\u00ebt Kubernetes ndihmojn\u00eb n\u00eb automatizimin e \u00e7do detyre q\u00eb lidhet me administrimin dhe menaxhimin e ciklit t\u00eb jet\u00ebs s\u00eb aplikacionit q\u00eb ju implementoni n\u00eb klasterin tuaj. P\u00ebr shembull, nj\u00eb operator mund t\u00eb automatizoj\u00eb p\u00ebrdit\u00ebsimet, kopjimin dhe shkall\u00ebzimin e aplikacionit, t\u00eb ndryshoj\u00eb konfigurimin etj. Lista e plot\u00eb e operator\u00ebve mund t\u00eb shikohet n\u00eb https:\/\/operatorhub.io\/<\/a><\/noindex>.<\/p>\n

OperatorHub \u00ebsht\u00eb n\u00eb dispozicion direkt nga nd\u00ebrfaqja e internetit t\u00eb konsol\u00ebs s\u00eb menaxhimit. Ai paraqet nj\u00eb katalog aplikacionesh p\u00ebr OpenShift, t\u00eb mb\u00ebshtetur nga Red Hat. Dometh\u00ebn\u00eb, t\u00eb gjitha operator\u00ebt e miratuar nga Red Hat do t\u00eb mbulohen nga mb\u00ebshtetje e furnizuesit.<\/p>\n

\"\u00c7far\u00eb
\nPortal i OperatorHub n\u00eb konsol\u00ebn e menaxhimit t\u00eb OpenShift<\/i><\/p>\n

Imazhi universal i baz\u00ebs<\/h4>\n

\nKy \u00ebsht\u00eb nj\u00eb set standardizimi i imazheve t\u00eb OS RHEL, t\u00eb cilat mund t\u00eb p\u00ebrdoren p\u00ebr t\u00eb krijuar aplikacionet tuaja n\u00eb kontejner\u00eb. Ka grupe minimale, standarde dhe t\u00eb plota. Ato z\u00ebn\u00eb shum\u00eb pak hap\u00ebsir\u00eb, suportojn\u00eb t\u00eb gjitha paketat e nevojshme t\u00eb instaluara dhe gjuh\u00ebt e programimit.<\/p>\n

Mjetet CI\/CD<\/h4>\n

\nN\u00eb RedHat OpenShift 4.2 u shtua mund\u00ebsia p\u00ebr t\u00eb zgjedhur midis Jenkins dhe OpenShift Pipelines t\u00eb bazuara n\u00eb Tekton Pipelines. <\/p>\n

OpenShift Pipelines bazohet n\u00eb Tekton, q\u00eb e mb\u00ebshtet m\u00eb mir\u00eb qasjen Pipeline as Code dhe GitOps. N\u00eb tubat OpenShift, \u00e7do hap ekzekutohet n\u00eb nj\u00eb kontejner t\u00eb ve\u00e7ant\u00eb, k\u00ebshtu q\u00eb burimet p\u00ebrdoren vet\u00ebm gjat\u00eb ekzekutimit t\u00eb hapit. Kjo u jep zhvilluesve kontroll t\u00eb plot\u00eb mbi tubat e dor\u00ebzimit t\u00eb moduleve, plugin\u00ebt dhe kontrollin e aksesit pa nj\u00eb server qendror CI\/CD p\u00ebr menaxhim.<\/p>\n

OpenShift Pipelines aktualisht \u00ebsht\u00eb n\u00eb faz\u00ebn Preview p\u00ebr zhvilluesit dhe \u00ebsht\u00eb e disponueshme si nj\u00eb operator n\u00eb klasterin OpenShift 4. Natyrisht, p\u00ebrdoruesit e OpenShift ende mund t\u00eb p\u00ebrdorin Jenkins n\u00eb RedHat OpenShift 4.<\/p>\n

P\u00ebrdit\u00ebsimet n\u00eb menaxhim p\u00ebr zhvilluesit<\/h2>\n

\nN\u00eb 4.2, OpenShift u p\u00ebrmir\u00ebsua plot\u00ebsisht nd\u00ebrfaqja p\u00ebr p\u00ebrdoruesit si p\u00ebr zhvilluesit ashtu edhe p\u00ebr administrator\u00ebt.<\/p>\n

N\u00eb versionet e m\u00ebparshme t\u00eb OpenShift, t\u00eb gjith\u00eb punonin n\u00eb tre konsola: katalogu i sh\u00ebrbimeve, konsola e administratorit dhe konsola e pun\u00ebs. Tani klasteri \u00ebsht\u00eb i ndar\u00eb vet\u00ebm n\u00eb dy pjes\u00eb \u2014 konsol\u00ebn e administratorit dhe konsol\u00ebn e zhvilluesit.<\/p>\n

Konsola e zhvilluesit ka marr\u00eb p\u00ebrmir\u00ebsime t\u00eb konsiderueshme n\u00eb nd\u00ebrfaqen e p\u00ebrdoruesit. Tani ajo tregon m\u00eb mir\u00eb topologjit\u00eb e aplikacioneve dhe nd\u00ebrtimet e tyre. Kjo e leht\u00ebson p\u00ebr zhvilluesit krijimin, shp\u00ebrndarjen dhe vizualizimin e aplikacioneve n\u00eb kontejner dhe burimeve t\u00eb klasterit. Lejon q\u00eb ata t\u00eb p\u00ebrqendrohen n\u00eb at\u00eb q\u00eb \u00ebsht\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ta.<\/p>\n

\"\u00c7far\u00eb
\nPortali i zhvilluesve n\u00eb konsol\u00ebn e menaxhimit OpenShift<\/i><\/p>\n

Odo<\/h4>\n

\nOdo \u00ebsht\u00eb nj\u00eb utilitar i komandave t\u00eb orientuar ndaj zhvilluesve, q\u00eb e thjeshton zhvillimin e aplikacioneve n\u00eb OpenShift. Duke p\u00ebrdorur nd\u00ebrveprimin n\u00eb stilin git push, ky CLI ndihmon zhvilluesit q\u00eb nuk jan\u00eb t\u00eb njohur me Kubernetes p\u00ebr t\u00eb krijuar aplikacione n\u00eb OpenShift.<\/p>\n

Integrimi me mjediset e zhvillimit<\/h4>\n

\nZhvilluesit tani mund t\u00eb krijojn\u00eb, debugin dhe shp\u00ebrndajn\u00eb aplikacionet e tyre n\u00eb OpenShift, pa e l\u00ebn\u00eb mjedisin e tyre t\u00eb preferuar t\u00eb zhvillimit t\u00eb kodit, si Microsoft Visual Studio, JetBrains (p\u00ebrfshir\u00eb IntelliJ), Eclipse Desktop, etj.<\/p>\n

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

\nKa ndodhur nj\u00eb zgjerim t\u00eb Red Hat OpenShift Deployment p\u00ebr Microsoft Azure DevOps. Tani p\u00ebrdoruesit e k\u00ebtij grupi mjetesh DevOps mund t\u00eb implementojn\u00eb aplikacionet e tyre n\u00eb Azure Red Hat OpenShift ose n\u00eb \u00e7do grup tjet\u00ebr OpenShift direkt nga Microsoft Azure DevOps.<\/p>\n

Kalim nga versione e tret\u00eb n\u00eb t\u00eb kat\u00ebrt\u00ebn<\/h2>\n

\nP\u00ebr shkak se b\u00ebhet fjal\u00eb p\u00ebr nj\u00eb publikim t\u00eb ri, e jo p\u00ebr nj\u00eb p\u00ebrdit\u00ebsim, nuk mund ta vendosni thjesht versionin kat\u00ebr mbi versionin tre. P\u00ebrdit\u00ebsimi nga versioni i tret\u00eb n\u00eb at\u00eb t\u00eb kat\u00ebrt nuk do t\u00eb mb\u00ebshtetet<\/strong>. <\/p>\n

Por ka edhe nj\u00eb lajm t\u00eb mir\u00eb: Red Hat ofron mjete p\u00ebr t\u00eb transferuar projektet nga 3.7 n\u00eb 4.2. Mund t\u00eb trasferoni ngarkesat e aplikacioneve duke p\u00ebrdorur mjetin Cluster Application Migration (CAM). CAM lejon t\u00eb kontrolloni migrimin dhe t\u00eb minimizoni koh\u00ebn e ndalimit t\u00eb aplikacionit.<\/p>\n

OpenShift 4.3<\/h2>\n

\nInovacionet kryesore, t\u00eb p\u00ebrshkruara n\u00eb k\u00ebt\u00eb artikull, u shfaq\u00ebn n\u00eb versionin 4.2. N\u00eb versionin e sapo l\u00ebshuar 4.3 ndryshimet nuk jan\u00eb aq t\u00eb m\u00ebdha, por ka disa gj\u00ebra t\u00eb reja. Lista e ndryshimeve \u00ebsht\u00eb mjaft e gjer\u00eb, do t\u00eb paraqitemi m\u00eb t\u00eb r\u00ebnd\u00ebsishmet sipas mendimit ton\u00eb:<\/p>\n

P\u00ebrdit\u00ebsimi i versionit t\u00eb Kubernetes n\u00eb 1.16. <\/h4>\n

\nVersioni \u00ebsht\u00eb p\u00ebrmir\u00ebsuar me dy hapa, n\u00eb OpenShift 4.2 ishte 1.14.<\/p>\n

Aft\u00ebsia p\u00ebr t\u00eb enkriptuar t\u00eb dh\u00ebnat n\u00eb etcd<\/h4>\n

\nDeri n\u00eb versionin 4.3, ka ardhur mund\u00ebsia p\u00ebr t\u00eb enkriptuar t\u00eb dh\u00ebnat n\u00eb baz\u00ebn etcd. Pas aktivizimit t\u00eb enkriptimit, do t\u00eb jet\u00eb e mundur t\u00eb enkriptoni burime t\u00eb tjera OpenShift API dhe Kubernetes API: Secrets, ConfigMaps, Routes, tokenet e aksesit dhe autorizimit OAuth.<\/p>\n

Helm<\/h4>\n

\nShtuar mb\u00ebshtetje p\u00ebr versionin Helm 3 \u2013 menaxheri i njohur i paketave p\u00ebr Kubernetes. Aktualisht, mb\u00ebshtetje ka statusin TRAJTIM TEKNOLOGJIE. N\u00eb versionet e ardhshme t\u00eb OpenShift, mb\u00ebshtetja p\u00ebr Helm do t\u00eb zgjerohet n\u00eb plot\u00ebsimin e saj. Mjeti helm cli vjen s\u00eb bashku me OpenShift dhe mund t\u00eb shkarkohet nga Web-konsola e menaxhimit t\u00eb grupeve. <\/p>\n

P\u00ebrdit\u00ebsimi i Project Dashboard<\/h4>\n

\nN\u00eb versionin e ri, Project Dashboard ofron informacion shtes\u00eb n\u00eb faqen e projektit: statusin e projektit, p\u00ebrdorimin e burimeve dhe kuotat p\u00ebr projektin.<\/p>\n

Shfaqja e dob\u00ebsive p\u00ebr quay n\u00eb Web-konsol\u00eb<\/h4>\n

\nFunksioni i shfaqjes s\u00eb dob\u00ebsive t\u00eb njohura p\u00ebr imazhet n\u00eb depozitat Quay \u00ebsht\u00eb shtuar n\u00eb konsol\u00ebn e menaxhimit. Mb\u00ebshtetet shfaqja e dob\u00ebsive p\u00ebr depozitat lokale dhe ato t\u00eb jashtme.<\/p>\n

P\u00ebrmir\u00ebsuar krijimin e operator\u00ebve offline<\/h4>\n

\nP\u00ebr rastin e zhvillimit t\u00eb nj\u00eb klasteri OpenShift n\u00eb nj\u00eb rrjet t\u00eb izoluar, ku qasja n\u00eb internet \u00ebsht\u00eb e kufizuar ose e mungon, krijimi i nj\u00eb \"pasqyre\" p\u00ebr regjistrin OperatorHub \u00ebsht\u00eb leht\u00ebsuar. Tani kjo mund t\u00eb realizohet me vet\u00ebm tre komanda.<\/p>\n

Autor\u00ebt: <\/i>
\nViktor Puchkov, Yuri Semenyuk<\/i>
\n
Burimi: 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\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 \u00c7far\u00eb \u00ebsht\u00eb e re n\u00eb Red Hat OpenShift 4.2 dhe 4.3? | ProHoster","description":"Versioni i kat\u00ebrt i OpenShift doli n\u00eb m\u00ebnyr\u00eb relativisht.","canonical_url":"https:\/\/prohoster.info\/sq\/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":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/74086","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=74086"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/74086\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/74087"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=74086"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=74086"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=74086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}