{"id":97254,"date":"2020-10-17T02:42:32","date_gmt":"2020-10-17T00:42:32","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/prosti-openshift-my-nedostatochno-czenili-tebya-i-prinimali-kak-dolzhnoe"},"modified":"2020-10-17T02:42:32","modified_gmt":"2020-10-17T00:42:32","slug":"prosti-openshift-my-nedostatochno-czenili-tebya-i-prinimali-kak-dolzhnoe","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/prosti-openshift-my-nedostatochno-czenili-tebya-i-prinimali-kak-dolzhnoe","title":{"rendered":"Na falenderojm\u00eb, OpenShift, nuk t\u00eb vler\u00ebsuam sa duhej dhe t\u00eb mor\u00ebm si t\u00eb mir\u00ebqen\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ky ky \u043f\u043e\u0441\u0442 \u00ebsht\u00eb shkruar sepse punonj\u00ebsit tan\u00eb kan\u00eb pasur shum\u00eb biseda me klient\u00ebt rreth zhvillimit t\u00eb aplikacioneve n\u00eb Kubernetes dhe karakteristikave t\u00eb k\u00ebtij zhvillimi n\u00eb OpenShift.<\/p>\n

\"Na
\n
\nNe zakonisht e fillojm\u00eb me tez\u00ebn se Kubernetes \u00ebsht\u00eb thjesht Kubernetes, nd\u00ebrsa OpenShift \u00ebsht\u00eb nj\u00eb platform\u00eb Kubernetes, si Microsoft AKS ose Amazon EKS. \u00c7do nj\u00ebri nga k\u00ebto platforma ka avantazhet e veta, t\u00eb fokusuara n\u00eb audienc\u00ebn p\u00ebrkat\u00ebse. Pas k\u00ebsaj, biseda kalon n\u00eb krahasimin e forcave dhe dob\u00ebsive t\u00eb platformave t\u00eb caktuara.
\n<\/a><\/noindex>
\nN\u00eb p\u00ebrgjith\u00ebsi, mendonim t\u00eb shkruanim k\u00ebt\u00eb post me p\u00ebrfundimin se \"D\u00ebgjoni, nuk ka r\u00ebnd\u00ebsi ku e drejtoni kodin, n\u00eb OpenShift, AKS, EKS, ose ndonj\u00eb Kubernetes tjet\u00ebr, madje n\u00eb \u00e7far\u00ebdo Kubernetes-i,\" (p\u00ebr shkak t\u00eb shkurtimit le t\u00eb th\u00ebrrasim at\u00eb KUK)<\/i> \u2013 \u00ebsht\u00eb e v\u00ebrtet\u00eb thjesht, dhe aty dhe aty.<\/p>\n

M\u00eb pas, planifikonim t\u00eb merrnim nj\u00eb \"Hello World\" t\u00eb thjesht\u00eb dhe me shembullin e tij t\u00eb tregojm\u00eb se \u00e7far\u00eb kan\u00eb t\u00eb p\u00ebrbashk\u00ebt dhe \u00e7far\u00eb dallimesh ka midis KUK dhe Red Hat OpenShift Container Platform (n\u00eb vazhdim, OCP ose thjesht OpenShift).<\/p>\n

Megjithat\u00eb, gjat\u00eb procesit t\u00eb shkruarjes s\u00eb k\u00ebtij posti, kuptuam se ishim aq t\u00eb zakonsh\u00ebm me p\u00ebrdorimin e OpenShift, saq\u00eb thjesht nuk e kuptojm\u00eb sesi ai \u00ebsht\u00eb rritur dhe shnd\u00ebrruar n\u00eb nj\u00eb platform\u00eb t\u00eb mrekullueshme, e cila \u00ebsht\u00eb b\u00ebr\u00eb shum\u00eb m\u00eb tep\u00ebr se thjesht nj\u00eb distribucion Kubernetes. Ne e kemi marr\u00eb mosh\u00ebn dhe thjesht\u00ebsin\u00eb e OpenShift p\u00ebr t\u00eb mir\u00ebqen\u00eb, duke l\u00ebn\u00eb m\u00ebnjan\u00eb madh\u00ebshtin\u00eb e tij.<\/p>\n

K\u00ebshtu, ka ardhur koha p\u00ebr nj\u00eb pendim aktiv, dhe tani do t\u00eb krahasojm\u00eb hap pas hapi aktivizimin e \"Hello World\" ton\u00eb n\u00eb KUK dhe n\u00eb OpenShift, duke e b\u00ebr\u00eb k\u00ebt\u00eb sa m\u00eb objektivisht (me p\u00ebrjashtim t\u00eb ndonj\u00ebher\u00eb kur shprehim nj\u00eb q\u00ebndrim personal p\u00ebr subjektin). N\u00ebse ju intereson nj\u00eb mendim thjesht subjektiv mbi k\u00ebt\u00eb \u00e7\u00ebshtje, mund ta lexoni k\u00ebtu (EN)<\/a><\/noindex>. N\u00eb k\u00ebt\u00eb post do t\u00eb ndjekim fakte dhe vet\u00ebm fakte.<\/p>\n

Klastrat<\/h3>\n

\nPra, p\u00ebr \"Hello World\" ton\u00eb na duhen klastra. T\u00eb themi \"jo\" \u00e7do titulli publik t\u00eb cloud-it, q\u00eb t\u00eb mos paguajm\u00eb p\u00ebr servera, regjistra, rrjete, transmetime t\u00eb t\u00eb dh\u00ebnave etj. K\u00ebshtu, ne zgjedhim nj\u00eb klas\u00ebr t\u00eb thjesht\u00eb nj\u00eb-nod\u00ebsh n\u00eb Minikube<\/a><\/noindex> (p\u00ebr KUK) dhe Code Ready Containers<\/a><\/noindex> (p\u00ebr klastrin OpenShift). T\u00eb dy k\u00ebto mund\u00ebsi jan\u00eb v\u00ebrtet t\u00eb thjeshta p\u00ebr instalim, por k\u00ebrkojn\u00eb shum\u00eb burime n\u00eb laptopin tuaj.<\/p>\n

\"Na<\/p>\n

Nd\u00ebrtimi n\u00eb KUK<\/h3>\n

\nPra, le t\u00eb fillojm\u00eb.<\/p>\n

Hapi 1 \u2013 ne nd\u00ebrrtojm\u00eb imazhin ton\u00eb t\u00eb kontejnerit<\/h4>\n

\nLe t\u00eb fillojm\u00eb duke e aktivizuar \"Hello World\" ton\u00eb n\u00eb minikube. P\u00ebr k\u00ebt\u00eb k\u00ebrkohet:<\/p>\n

    \n
  1. 1. Docker i instaluar.<\/li>\n
  2. 2. Git i instaluar.<\/li>\n
  3. 3. Maven q\u00eb \u00ebsht\u00eb vendosur (n\u00eb fakt, n\u00eb k\u00ebt\u00eb projekt p\u00ebrdoret binari mvnw, k\u00ebshtu q\u00eb mund ta kaloni k\u00ebt\u00eb hap).<\/li>\n
  4. 4. N\u00eb fakt, vet\u00eb burimi, dmth, kloni i depozit\u00ebs github.com\/gcolman\/quarkus-hello-world.git<\/a><\/noindex><\/li>\n<\/ol>\n

    \nHapi i par\u00eb \u00ebsht\u00eb krijimi i nj\u00eb projekti Quarkus. Mos u frik\u00ebsoni n\u00ebse nuk keni punuar ndonj\u00ebher\u00eb me faqen Quarkus.io \u2013 \u00ebsht\u00eb e thjesht\u00eb. Thjesht zgjidhni komponent\u00ebt q\u00eb d\u00ebshironi t\u00eb p\u00ebrdorni n\u00eb projekt (RestEasy, Hibernate, Amazon SQS, Camel, etj.), dhe m\u00eb pas Quarkus do ta konfiguroj\u00eb automatikisht arketipin maven dhe do ta ngrej\u00eb gjith\u00e7ka n\u00eb github. Dometh\u00ebn\u00eb, me nj\u00eb klik t\u00eb vet\u00ebm t\u00eb mausit \u2013 dhe \u00ebsht\u00eb gati. Ky \u00ebsht\u00eb arsyeja pse e duam Quarkus.<\/p>\n

    \"Na<\/p>\n

    M\u00ebnyra m\u00eb e thjesht\u00eb p\u00ebr t\u00eb nd\u00ebrtuar 'Hello World' n\u00eb nj\u00eb imazh kontejneri \u00ebsht\u00eb t\u00eb p\u00ebrdorim zgjerimet quarkus-maven p\u00ebr Docker, t\u00eb cilat do t\u00eb kryejn\u00eb t\u00eb gjith\u00eb pun\u00ebn e nevojshme. Me ardhjen e Quarkus, kjo \u00ebsht\u00eb b\u00ebr\u00eb v\u00ebrtet e leht\u00eb dhe e thjesht\u00eb: thjesht shtoni zgjerimin container-image-docker dhe mund t\u00eb krijoni imazhe me komandat maven.<\/p>\n

    . \/mvnw quarkus:add-extension -Dextensions=\"container-image-docker\"\n<\/code><\/pre>\n
    \nDhe, p\u00ebrfundimisht, kryejm\u00eb nd\u00ebrtimin e imazhit ton\u00eb duke p\u00ebrdorur Maven. Si rezultat, kodi yn\u00eb burimor kthehet n\u00eb nj\u00eb imazh kontejneri t\u00eb gatsh\u00ebm p\u00ebr t'u ekzekutuar n\u00eb ambientin e ekzekutimit t\u00eb kontejner\u00ebve.<\/p>\n
    \"Na<\/p>\n
    . \/mvnw -X clean package -Dquarkus.container-image.build=true\n<\/code><\/pre>\n
    \nK\u00ebtu, n\u00eb fakt, \u00ebsht\u00eb gjith\u00e7ka, tani mund t\u00eb nisim kontejnerin me komand\u00ebn docker run, duke i vendosur sh\u00ebrbimin ton\u00eb n\u00eb portin 8080 p\u00ebr t'u qasur mbi t\u00eb.<\/p>\n
    docker run -i \u2014 rm -p 8080:8080 gcolman\/quarkus-hello-world\n<\/code><\/pre>\n
    \"Na<\/p>\n
    Pasi instanca e kontejnerit \u00ebsht\u00eb nisur, mbetet vet\u00ebm t\u00eb kontrolloni me komand\u00ebn curl q\u00eb sh\u00ebrbimi yn\u00eb po punon:<\/p>\n
    \"Na<\/p>\n
    Pra, gjith\u00e7ka funksionon, dhe ishte v\u00ebrtet e leht\u00eb dhe e thjesht\u00eb.<\/p>\n
    Hapi 2 \u2013 d\u00ebrgojm\u00eb kontejnerin ton\u00eb n\u00eb depozit\u00ebn e imazheve t\u00eb kontejner\u00ebve<\/h4>\n
    \nDerisa, imazhi q\u00eb krijuam ruhet lokalisht, n\u00eb ruajtjen ton\u00eb lokale t\u00eb kontejner\u00ebve. N\u00ebse d\u00ebshirojm\u00eb ta p\u00ebrdorim k\u00ebt\u00eb imazh n\u00eb mjedisin ton\u00eb K8s, duhet ta ngrem\u00eb n\u00eb nj\u00eb depo tjet\u00ebr. N\u00eb Kubernetes nuk ka funksione t\u00eb tilla, prandaj do t\u00eb p\u00ebrdorim dockerhub. Sepse, s\u00eb pari, \u00ebsht\u00eb falas, dhe s\u00eb dyti, (m\u00eb t\u00ebr\u00eb) t\u00eb gjith\u00eb e b\u00ebjn\u00eb k\u00ebshtu.<\/p>\n
    Kjo \u00ebsht\u00eb gjithashtu shum\u00eb e thjesht\u00eb, dhe k\u00ebtu ne na duhen vet\u00ebm nj\u00eb llogari n\u00eb dockerhub.<\/p>\n
    Pra, le t'i vendosim dockerhub dhe ta d\u00ebrgojm\u00eb atje imazhin ton\u00eb.<\/p>\n
    \"Na<\/p>\n
    Hapi 3 \u2013 nisim Kubernetes<\/h4>\n
    \nKa shum\u00eb m\u00ebnyra p\u00ebr t\u00eb nd\u00ebrtuar konfigurimin e Kubernetes p\u00ebr t\u00eb nisur 'Hello World' ton\u00eb, por do t\u00eb p\u00ebrdorim m\u00eb t\u00eb thjesht\u00ebn, sepse k\u00ebshtu jemi ne...<\/p>\n
    Fillimisht nisim klasterin minikube:<\/p>\n
    minikube start\n<\/code><\/pre>\n
    <\/p>\n
    Hapi 4 \u2013 zhvillojm\u00eb imazhin ton\u00eb t\u00eb kontejnerit<\/h4>\n
    \nTani duhet t\u00eb konvertojm\u00eb kodin ton\u00eb dhe imazhin e kontejnerit n\u00eb konfigurimet e Kubernetes. Me fjal\u00eb t\u00eb tjera, na nevojiten definita t\u00eb pod-it dhe deploy-it me referenc\u00eb n\u00eb imazhin ton\u00eb n\u00eb Docker Hub. Nj\u00eb nga m\u00ebnyrat m\u00eb t\u00eb thjeshta p\u00ebr ta b\u00ebr\u00eb k\u00ebt\u00eb \u00ebsht\u00eb t\u00eb ekzekutojm\u00eb komand\u00ebn e krijimit t\u00eb deploy-it, duke iu referuar imazhit ton\u00eb:<\/p>\n
    \"Na<\/p>\n
    kubectl create deployment hello-quarkus --image=gcolman\/quarkus-hello-world:1.0.0-SNAPSHOT\n<\/code><\/pre>\n
    \nMe k\u00ebt\u00eb komand\u00eb i tham\u00eb Kubernetesit ton\u00eb t\u00eb krijoj\u00eb nj\u00eb konfigurim deploy-i, i cili duhet t\u00eb p\u00ebrmbaj\u00eb specifikimin e pod-it p\u00ebr imazhin ton\u00eb t\u00eb kontejnerit. Kjo komand\u00eb gjithashtu do ta aplikoj\u00eb k\u00ebt\u00eb konfigurim n\u00eb klasterin ton\u00eb minikube dhe do t\u00eb krijoj\u00eb nj\u00eb deploy q\u00eb do t\u00eb shkarkoj\u00eb imazhin ton\u00eb t\u00eb kontejnerit dhe do t\u00eb nis\u00eb pod-in n\u00eb klaster.<\/p>\n
    Hapi 5 \u2013 hapim qasjen n\u00eb sh\u00ebrbimin ton\u00eb<\/h4>\n
    \nTani, kur kemi imazhin e kontejnerit t\u00eb zhvilluar, \u00ebsht\u00eb koha t\u00eb mendojm\u00eb p\u00ebr m\u00ebnyr\u00ebn e konfigurimit t\u00eb qasjes eksterrne n\u00eb k\u00ebt\u00eb sh\u00ebrbim Restful, i cili, n\u00eb fakt, \u00ebsht\u00eb programuar n\u00eb kodin ton\u00eb.<\/p>\n
    Ka shum\u00eb m\u00ebnyra p\u00ebr ta b\u00ebr\u00eb k\u00ebt\u00eb. P\u00ebr shembull, mund t\u00eb p\u00ebrdorim komand\u00ebn expose p\u00ebr t\u00eb krijuar automatikisht komponent\u00ebt p\u00ebrkat\u00ebs t\u00eb Kubernetes, si sh\u00ebrbimet dhe endpointet. N\u00eb fakt, k\u00ebshtu do ta b\u00ebjm\u00eb, duke ekzekutuar komand\u00ebn expose p\u00ebr objektin ton\u00eb t\u00eb deploy-it:<\/p>\n
    kubectl expose deployment hello-quarkus --type=NodePort --port=8080\n<\/code><\/pre>\n
    \nLe t\u00eb ndalemi p\u00ebr nj\u00eb moment mbi opsionin \"--type\" t\u00eb komand\u00ebs expose.<\/p>\n
    Kur b\u00ebjm\u00eb expose dhe krijojm\u00eb komponent\u00ebt e nevojsh\u00ebm p\u00ebr t\u00eb nisur sh\u00ebrbimin ton\u00eb, nd\u00ebr t\u00eb tjera, na nevojitet q\u00eb t\u00eb jashtme t\u00eb jet\u00eb e mundur t\u00eb lidhet me sh\u00ebrbimin hello-quarkus, i cili ndodhet brenda rrjetit ton\u00eb t\u00eb programuesh\u00ebm. Dhe parametri lloji<\/b> na lejon t\u00eb krijojm\u00eb dhe lidhemi me elemente si balancuesit e ngarkes\u00ebs p\u00ebr t\u00eb drejtuar trafikun n\u00eb k\u00ebt\u00eb rrjet.<\/p>\n
    P\u00ebr shembull, duke shkruar type=LoadBalancer<\/b>, ne automatikisht inicojm\u00eb nj\u00eb balancues ngarkese n\u00eb re t\u00eb hapur p\u00ebr t\u00eb u lidhur me klasterin ton\u00eb Kubernetes. Kjo, sigurisht, \u00ebsht\u00eb mrekullueshme, por duhet t\u00eb kuptojm\u00eb se nj\u00eb konfigurim i till\u00eb do t\u00eb jet\u00eb i lidhur ngusht\u00ebsisht me nj\u00eb re t\u00eb caktuar dhe do t\u00eb jet\u00eb m\u00eb e v\u00ebshtir\u00eb p\u00ebr t'u migruar midis instancave t\u00eb Kubernetes n\u00eb mjedise t\u00eb ndryshme.<\/p>\n
    N\u00eb shembullin ton\u00eb type=NodePort<\/b>, q\u00eb do t\u00eb thot\u00eb se k\u00ebrkesa p\u00ebr sh\u00ebrbimin ton\u00eb b\u00ebhet p\u00ebrmes adres\u00ebs IP t\u00eb nod\u00ebs dhe numrit t\u00eb port\u00ebs. Ky variant lejon q\u00eb t\u00eb mos p\u00ebrdorim asnj\u00eb cloud publik, por k\u00ebrkon disa hapa shtes\u00eb. S\u00eb pari, na nevojitet nj\u00eb balancues ngarkese privat, prandaj do t\u00eb krijojm\u00eb n\u00eb klasterin ton\u00eb balancuesin e ngarkes\u00ebs NGINX.<\/p>\n
    Hapi 6 \u2013 vendosja e balancuesit t\u00eb ngarkes\u00ebs<\/h4>\n
    \nMinikube ka nj\u00eb s\u00ebr\u00eb funksionesh t\u00eb platform\u00ebs q\u00eb leht\u00ebsojn\u00eb krijimin e komponenteve t\u00eb nevojshme p\u00ebr qasje nga jasht\u00eb, si\u00e7 jan\u00eb kontrollor\u00ebt ingress. Minikube vjen me kontrollorin ingress Nginx, dhe na mbetet vet\u00ebm ta aktivizojm\u00eb dhe ta konfigurajm\u00eb.<\/p>\n
    minikube addons enable ingress\n<\/code><\/pre>\n
    \nTani me nj\u00eb komand\u00eb krijojm\u00eb kontrollorin ingress Nginx, i cili do t\u00eb funksionoj\u00eb brenda klasterit ton\u00eb minikube:<\/p>\n
    ingress-nginx-controller-69ccf5d9d8-j5gs9 1\/1 Duke funksionuar 1 33m\n<\/code><\/pre>\n
    <\/p>\n
    Hapi 7 \u2013 Konfigurimi i ingress<\/h4>\n
    \nTani duhet t\u00eb konfigurojm\u00eb kontrollorin ingress Nginx, q\u00eb t\u00eb pranoj\u00eb k\u00ebrkesat hello-quarkus.<\/p>\n
    \"Na<\/p>\n
    \"Na<\/p>\n
    Dhe, p\u00ebrfundimisht, duhet t\u00eb aplikojm\u00eb k\u00ebt\u00eb konfigurim.<\/p>\n
    \"Na<\/p>\n
    kubectl apply -f ingress.yml\n<\/code><\/pre>\n
    \"Na<\/p>\n
    Duke qen\u00eb se i b\u00ebjm\u00eb gjith\u00eb k\u00ebt\u00eb n\u00eb kompjuterin ton\u00eb, thjesht shtojm\u00eb adres\u00ebn IP t\u00eb nod\u00ebs son\u00eb n\u00eb skedarin \/etc\/hosts, p\u00ebr t\u00eb drejtuar k\u00ebrkesat http drejt minikube ton\u00eb n\u00eb balancuesin e ngarkes\u00ebs NGINX.<\/p>\n
    192.168.99.100 hello-quarkus.info\n<\/code><\/pre>\n
    \nGjith\u00e7ka, tani sh\u00ebrbimi yn\u00eb minikube \u00ebsht\u00eb i aksesuesh\u00ebm nga jasht\u00eb p\u00ebrmes kontrollorit ingress Nginx.<\/p>\n
    \"Na<\/p>\n
    Ajo ishte e leht\u00eb, apo jo? Ose jo aq shum\u00eb?<\/h3>\n
    \"Na<\/p>\n
    Ekzekutimi n\u00eb OpenShift (Code Ready Containers)<\/h3>\n
    \nTani le t\u00eb shohim se si b\u00ebhet gjith\u00eb kjo n\u00eb Red Hat OpenShift Container Platform (OCP).<\/p>\n
    Si n\u00eb rastin e minikube, ne zgjedhim skem\u00ebn me nj\u00eb klaster t\u00eb vet\u00ebm OpenShift n\u00eb form\u00ebn e Code Ready Containers (CRC). M\u00eb par\u00eb kjo quhej minishift dhe \u00ebsht\u00eb bazuar n\u00eb projektin OpenShift Origin, dhe tani \u00ebsht\u00eb CRC, e nd\u00ebrtuar mbi platform\u00ebn Red Hat OpenShift Container.<\/p>\n
    K\u00ebtu, na falni, nuk mund t\u00eb p\u00ebrmbaheshim pa th\u00ebn\u00eb: 'OpenShift \u00ebsht\u00eb madh\u00ebshtor!'<\/p>\n
    Fillimisht menduam t\u00eb shkruajm\u00eb se zhvillimi n\u00eb OpenShift nuk \u00ebsht\u00eb ndryshe nga zhvillimi n\u00eb Kubernetes. Dhe n\u00eb thelb, k\u00ebshtu \u00ebsht\u00eb. Por gjat\u00eb shkrimit t\u00eb k\u00ebtij postimi, na erdhi n\u00eb mendje se sa shum\u00eb nd\u00ebrlikime ka kur s'ke OpenShift, dhe prandaj, po e p\u00ebrs\u00ebrisim, \u00ebsht\u00eb madh\u00ebshtor. Ne i duam gj\u00ebrat t\u00eb thjeshta, dhe m\u00ebnyra se si leht\u00eb zvog\u00eblohet shembulli yn\u00eb n\u00eb OpenShift krahasuar me minikube, n\u00eb fakt, na nxiti t\u00eb shkruajm\u00eb k\u00ebt\u00eb post.<\/p>\n
    Le t\u00eb kalojm\u00eb n\u00eb proces dhe t\u00eb shohim \u00e7far\u00eb na nevojitet t\u00eb b\u00ebjm\u00eb.<\/p>\n
    K\u00ebshtu, n\u00eb shembullin e minikube filluam me Docker\u2026 Prit, nuk na nevojitet m\u00eb q\u00eb n\u00eb makin\u00eb t\u00eb jet\u00eb instaluar Docker.<\/p>\n
    Dhe git lokal nuk na nevojitet.
    \nAs Maven nuk \u00ebsht\u00eb i nevojsh\u00ebm.
    \nAs nuk nevojitet t\u00eb krijojm\u00eb manualisht imazhin e kontejnerit.
    \nAs nuk nevojitet t\u00eb k\u00ebrkojm\u00eb nj\u00eb repository p\u00ebr imazhet e kontejner\u00ebve.
    \nAs nuk nevojitet t\u00eb instalojm\u00eb nj\u00eb kontrollues ingress.
    \nAs nuk nevojitet t\u00eb konfigurojm\u00eb ingress.<\/b><\/p>\n
    E kuptuat, apo jo? P\u00ebr t\u00eb vendosur dhe drejtuar aplikacionin ton\u00eb n\u00eb OpenShift, nuk duhen nga ato q\u00eb p\u00ebrmend\u00ebm m\u00eb lart. Procesi vet\u00eb duket si m\u00eb posht\u00eb.<\/p>\n
    Hapi 1 \u2013 Nisim klasterin ton\u00eb OpenShift<\/h4>\n
    \nNe p\u00ebrdorim Code Ready Containers nga Red Hat, i cili n\u00eb thelb \u00ebsht\u00eb i nj\u00ebjti si Minikube, por me nj\u00eb klaster t\u00eb plot\u00eb nj\u00eb-nod i Openshift.<\/p>\n
    crc start\n<\/code><\/pre>\n
    <\/p>\n
    Hapi 2 \u2013 Kryejm\u00eb nd\u00ebrtimin dhe vendosjen e aplikacionit n\u00eb klasterin OpenShift<\/h4>\n
    \nN\u00eb k\u00ebt\u00eb hap, thjesht\u00ebsia dhe leht\u00ebsia e OpenShift shfaqen n\u00eb mbar\u00eb hapsir\u00ebn. Si n\u00eb t\u00eb gjitha shp\u00ebrndarjet e Kubernetes, kemi shum\u00eb m\u00ebnyra p\u00ebr t\u00eb vendosur aplikacionin n\u00eb klaster. Dhe, si n\u00eb rastin e KUK, ne zgjedhim q\u00ebllimisht at\u00eb m\u00eb t\u00eb leht\u00eb.<\/p>\n
    OpenShift gjithmon\u00eb \u00ebsht\u00eb nd\u00ebrtuar si nj\u00eb platform\u00eb p\u00ebr krijimin dhe drejtp\u00ebrdrejtimin e aplikacioneve t\u00eb kontejner\u00ebve. Nd\u00ebrtimi i konteiner\u00ebve ka qen\u00eb gjithmon\u00eb nj\u00eb pjes\u00eb e pandar\u00eb e k\u00ebsaj platforme, ndaj k\u00ebtu ka shum\u00eb burime shtes\u00eb Kubernetes p\u00ebr detyra p\u00ebrkat\u00ebse.<\/p>\n
    Ne do t\u00eb p\u00ebrdorim procesin Source 2 Image (S2I) t\u00eb OpenShift, i cili ka disa m\u00ebnyra t\u00eb ndryshme p\u00ebr t\u00eb marr\u00eb kodin ton\u00eb (ose skedar\u00ebt binar\u00eb) dhe p\u00ebr ta shnd\u00ebrruar at\u00eb n\u00eb nj\u00eb imazh konteineri, p\u00ebr t'u ekzekutuar n\u00eb klasterin OpenShift.<\/p>\n
    P\u00ebr k\u00ebt\u00eb, do na nevojiten dy gj\u00ebra:<\/p>\n