{"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":"M\u00eb fal, OpenShift, nuk t\u00eb kemi vler\u00ebsuar mjaftuesh\u00ebm dhe t\u00eb kemi marr\u00eb p\u00ebr t\u00eb dh\u00ebn\u00eb.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ky\u00e7ti \u00ebsht\u00eb shkruar pasi punonj\u00ebsit tan\u00eb kan\u00eb pasur shum\u00eb biseda me klient\u00ebt mbi zhvillimin e aplikacioneve n\u00eb Kubernetes dhe specifikat e k\u00ebtij zhvillimi n\u00eb OpenShift.<\/p>\n

\"M\u00eb
\n
\nNe zakonisht 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\u00eb prej k\u00ebtyre platformave ka avantazhet e veta, orientuar ndaj nj\u00eb audience t\u00eb caktuar. Pas k\u00ebsaj, biseda kalon n\u00eb krahasimin e forcave dhe dob\u00ebsive t\u00eb platformave specifike.
\n<\/a><\/noindex>
\nN\u00eb p\u00ebrgjith\u00ebsi, ne menduam t\u00eb shkruajm\u00eb k\u00ebt\u00eb postim me nj\u00eb p\u00ebrfundim si \"Doni, nuk ka r\u00ebnd\u00ebsi ku e ekzekutoni kodin, n\u00eb OpenShift, AKS, EKS, n\u00eb ndonj\u00eb Kubernetes t\u00eb personalizuar, madje n\u00eb \u00e7far\u00ebdo Kubernetes-i\" (p\u00ebr shkak t\u00eb shkurt\u00ebsis\u00eb, le ta quajm\u00eb KUK)<\/i> \u2013 \u00ebsht\u00eb n\u00eb t\u00eb v\u00ebrtet\u00eb e thjesht\u00eb, p\u00ebr t\u00eb dyja.<\/p>\n

M\u00eb pas planifikonim t\u00eb merrnim nj\u00eb \"Hello World\" t\u00eb thjesht\u00eb dhe n\u00eb shembullin e tij t\u00eb tregonin se \u00e7far\u00eb kan\u00eb t\u00eb p\u00ebrbashk\u00ebt dhe cilat jan\u00eb diferencat midis KUK dhe Red Hat OpenShift Container Platform (m\u00eb pas, OCP ose thjesht OpenShift).<\/p>\n

Megjithat\u00eb, gjat\u00eb shkrimit t\u00eb k\u00ebtij postimi, kuptuam se ishim m\u00ebsuar aq shum\u00eb me p\u00ebrdorimin e OpenShift, saq\u00eb nuk e kuptojm\u00eb se sa \u00ebsht\u00eb rritur dhe kthyer n\u00eb nj\u00eb platform\u00eb t\u00eb shk\u00eblqyer, e cila tani \u00ebsht\u00eb shum\u00eb m\u00eb tep\u00ebr sesa thjesht nj\u00eb distribucion Kubernetes. Jemi m\u00ebsuar ta perceptojm\u00eb pjekurin\u00eb dhe thjesht\u00ebsin\u00eb e OpenShift si di\u00e7ka t\u00eb natyrshme, duke humbur nga v\u00ebmendja shk\u00eblqimin e tij.<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, ka ardhur koha p\u00ebr nj\u00eb pendim aktiv, dhe tani do t\u00eb krahasojm\u00eb hap pas hapi testin ton\u00eb 'Hello World' n\u00eb KUK dhe n\u00eb OpenShift, duke e b\u00ebr\u00eb k\u00ebt\u00eb sa m\u00eb objektivisht t\u00eb jet\u00eb e mundur (ndoshta duke shprehur ndonj\u00ebher\u00eb mendimin ton\u00eb personal mbi tem\u00ebn). N\u00ebse jeni t\u00eb interesuar p\u00ebr mendimin e past\u00ebr subjektiv mbi k\u00ebt\u00eb \u00e7\u00ebshtje, mund ta lexoni k\u00ebtu (EN)<\/a><\/noindex>. N\u00eb k\u00ebt\u00eb postim do t\u00eb mbajm\u00eb q\u00ebndrim te faktet dhe vet\u00ebm te faktet.<\/p>\n

Kluster\u00ebt<\/h3>\n

\nPra, p\u00ebr 'Hello World' ton\u00eb na nevojiten kluster\u00eb. T\u00eb themi menj\u00ebher\u00eb 'jo' \u00e7do lloj cloud publik, p\u00ebr t\u00eb mos paguar p\u00ebr server\u00ebt, regjistrat, rrjetet, transferimin e t\u00eb dh\u00ebnave, etj. Prandaj, ne zgjedhim nj\u00eb kluster t\u00eb thjesht\u00eb me nj\u00eb nyje n\u00eb Minikube<\/a><\/noindex> (p\u00ebr KUK) dhe Code Ready Containers<\/a><\/noindex> (p\u00ebr klusterin OpenShift). T\u00eb dyja k\u00ebto variante jan\u00eb realisht t\u00eb lehta p\u00ebr t'u instaluar, por do t\u00eb k\u00ebrkojn\u00eb mjaft burime n\u00eb laptopin tuaj.<\/p>\n

\"M\u00eb<\/p>\n

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

\nPra rregullojm\u00eb.<\/p>\n

Hapi 1 \u2013 krijojm\u00eb imazhin ton\u00eb t\u00eb kontejnerit<\/h4>\n

\nS\u00eb pari do t\u00eb fillojm\u00eb duke e drejtuar 'Hello World' ton\u00eb n\u00eb minikube. P\u00ebr k\u00ebt\u00eb nevojiten:<\/p>\n

    \n
  1. 1. Docker i instaluar.<\/li>\n
  2. 2. Git i instaluar.<\/li>\n
  3. 3. Maven i instaluar (n\u00eb fakt, n\u00eb k\u00ebt\u00eb projekt p\u00ebrdoret binari mvnw, k\u00ebshtu q\u00eb mund t\u00eb kaloni pa k\u00ebt\u00eb).<\/li>\n
  4. 4. Burimi vet\u00eb, pra, kloni i depove github.com\/gcolman\/quarkus-hello-world.git<\/a><\/noindex><\/li>\n<\/ol>\n

    \nS\u00eb pari duhet t\u00eb krijoni nj\u00eb projekt Quarkus. Mos u friksoni n\u00ebse nuk keni punuar ndonj\u00ebher\u00eb me sitin Quarkus.io \u2013 \u00ebsht\u00eb e leht\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 vet\u00eb arketipin maven dhe do ta publikoj\u00eb gjith\u00e7ka n\u00eb github. Pra, ndonj\u00ebher\u00eb nj\u00eb klikim dhe \u00ebsht\u00eb gati. K\u00ebshtu q\u00eb e duam Quarkus.<\/p>\n

    \"M\u00eb<\/p>\n

    M\u00ebnyra m\u00eb e thjesht\u00eb p\u00ebr t\u00eb nd\u00ebrtuar 'Hello World' ton\u00eb n\u00eb imazhin e kontejnerit \u00ebsht\u00eb t\u00eb p\u00ebrdorni zgjerimet quarkus-maven p\u00ebr Docker-in, t\u00eb cilat do t\u00eb b\u00ebjn\u00eb t\u00eb gjith\u00eb pun\u00ebn e nevojshme. Me ardhjen e Quarkus, kjo \u00ebsht\u00eb b\u00ebr\u00eb v\u00ebrtet e leht\u00eb: 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 n\u00eb fund, realizojm\u00eb nd\u00ebrtimin e imazhit ton\u00eb duke p\u00ebrdorur Maven. Si rezultat, kodi yn\u00eb burimor shnd\u00ebrrohet n\u00eb nj\u00eb imazh t\u00eb gatsh\u00ebm p\u00ebr konteiner, i cili tashm\u00eb mund t\u00eb ekzekutohet n\u00eb nj\u00eb mjedis konteiner\u00ebsh.<\/p>\n
    \"M\u00eb<\/p>\n
    .\/mvnw -X clean package -Dquarkus.container-image.build=true\n<\/code><\/pre>\n
    \nJa, tani mund t\u00eb ekzekutojm\u00eb konteinerin me komand\u00ebn docker run, duke e mapuar sh\u00ebrbimin ton\u00eb n\u00eb portin 8080, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mund t\u00eb aksesohet.<\/p>\n
    docker run -i --rm -p 8080:8080 gcolman\/quarkus-hello-world\n<\/code><\/pre>\n
    \"M\u00eb<\/p>\n
    Pas aktivizimit t\u00eb instanc\u00ebs s\u00eb konteinerit, mbetet vet\u00ebm t\u00eb kontrollojm\u00eb me komand\u00ebn curl n\u00ebse sh\u00ebrbimi yn\u00eb funksionon:<\/p>\n
    \"M\u00eb<\/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 konteinerin ton\u00eb n\u00eb depozit\u00ebn e imazheve t\u00eb konteiner\u00ebve<\/h4>\n
    \nDerisa imazhi q\u00eb krijuam \u00ebsht\u00eb ruajtur lokal, n\u00eb magazin\u00ebn ton\u00eb lokale t\u00eb konteiner\u00ebve. N\u00ebse d\u00ebshirojm\u00eb t\u00eb p\u00ebrdorim k\u00ebt\u00eb imazh n\u00eb mjedisin ton\u00eb K8s, duhet ta ngarkojm\u00eb n\u00eb ndonj\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, (pothuajse) t\u00eb gjith\u00eb e b\u00ebjn\u00eb k\u00ebshtu.<\/p>\n
    Kjo \u00ebsht\u00eb gjithashtu shum\u00eb e thjesht\u00eb, dhe k\u00ebtu vet\u00ebm nj\u00eb llogari n\u00eb dockerhub \u00ebsht\u00eb e nevojshme.<\/p>\n
    Pra, ngarkojm\u00eb n\u00eb dockerhub dhe e d\u00ebrgojm\u00eb imazhin ton\u00eb aty.<\/p>\n
    \"M\u00eb<\/p>\n
    Hapi 3 \u2013 aktivizoni Kubernetes<\/h4>\n
    \nKa shum\u00eb m\u00ebnyra p\u00ebr t\u00eb mbledhur konfigurimin e kubernetes p\u00ebr t\u00eb aktivizuar \"Hello World\" ton\u00eb, por ne do t\u00eb p\u00ebrdorim m\u00ebnyr\u00ebn m\u00eb t\u00eb thjesht\u00eb, sepse kjo \u00ebsht\u00eb m\u00ebnyra jon\u00eb\u2026<\/p>\n
    N\u00eb fillim, aktivizoni 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 kthejm\u00eb kodin ton\u00eb dhe imazhin e kontejnerit n\u00eb konfigurimet e kubernetes. Me fjal\u00eb t\u00eb tjera, na nevojitet definicioni i pod-it dhe deployment-it me referenc\u00eb n\u00eb imazhin ton\u00eb n\u00eb dockerhub. 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 create deployment, duke treguar p\u00ebr imazhin ton\u00eb:<\/p>\n
    \"M\u00eb<\/p>\n
    kubectl create deployment hello-quarkus \u2014 image=gcolman\/quarkus-hello-world:1.0.0-SNAPSHOT\n<\/code><\/pre>\n
    \nMe k\u00ebt\u00eb komand\u00eb, ne i tham\u00eb KUK ton\u00eb t\u00eb krijoj\u00eb konfigurimin e deployment-it, 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 deployment q\u00eb do t\u00eb shkarkoj\u00eb imazhin ton\u00eb t\u00eb kontejnerit dhe do t\u00eb aktivizoj\u00eb pod-in n\u00eb klaster.<\/p>\n
    Hapi 5 \u2013 hapim qasjen n\u00eb sh\u00ebrbimin ton\u00eb<\/h4>\n
    \nTani q\u00eb kemi nj\u00eb imazh kontejneri t\u00eb zhvilluar, \u00ebsht\u00eb koha t\u00eb mendojm\u00eb se si t\u00eb konfigurojm\u00eb qasjen e jashtme n\u00eb k\u00ebt\u00eb sh\u00ebrbim Restful, i cili \u00ebsht\u00eb programuar n\u00eb kodin ton\u00eb.<\/p>\n
    Ka jan\u00eb shum\u00eb m\u00ebnyra. P\u00ebr shembull, mund t\u00eb p\u00ebrdorni komand\u00ebn expose p\u00ebr t\u00eb krijuar automatikisht komponent\u00ebt p\u00ebrkat\u00ebs Kubernetes, si\u00e7 jan\u00eb sh\u00ebrbimet dhe pik\u00ebt e hyrjes. N\u00eb fakt, k\u00ebshtu do t\u00eb veprojm\u00eb, duke ekzekutuar komand\u00ebn expose p\u00ebr objektin ton\u00eb deployment.<\/p>\n
    kubectl expose deployment hello-quarkus --type=NodePort --port=8080\n<\/code><\/pre>\n
    \nLe t\u00eb ndalemi p\u00ebr nj\u00eb moment te opsioni \"--type\" i komand\u00ebs expose.<\/p>\n
    Kur b\u00ebjm\u00eb expose dhe krijojm\u00eb komponent\u00ebt e nevojsh\u00ebm p\u00ebr t\u00eb drejtuar sh\u00ebrbimin ton\u00eb, na nevojitet q\u00eb t\u00eb jashtme t\u00eb mund t\u00eb lidhen me sh\u00ebrbimin hello-quarkus, i cili ndodhet brenda rrjetit ton\u00eb t\u00eb definuar me softuer. Dhe parametri type<\/b> na lejon t\u00eb krijojm\u00eb dhe lidhim gj\u00ebra si\u00e7 jan\u00eb balancuesit e ngarkes\u00ebs p\u00ebr t\u00eb riorientuar trafikun n\u00eb k\u00ebt\u00eb rrjet.<\/p>\n
    P\u00ebr shembull, duke specifikuar type=LoadBalancer<\/b>, ne automatikisht aktivizojm\u00eb balancuesin e ngarkes\u00ebs n\u00eb nj\u00eb re publike p\u00ebr t'u lidhur me klusterin ton\u00eb Kubernetes. Kjo \u00ebsht\u00eb, sigurisht, e shk\u00eblqyer, por duhet t\u00eb kuptohet se nj\u00eb konfigurim i till\u00eb do t\u00eb jet\u00eb i lidhur ngusht\u00eb me nj\u00eb re publike specifike dhe do t\u00eb jet\u00eb m\u00eb e v\u00ebshtir\u00eb t\u00eb transferosh midis instancave t\u00eb Kubernetes n\u00eb mjedise t\u00eb ndryshme.<\/p>\n
    N\u00eb shembullin ton\u00eb type=NodePort<\/b>, domethen, qoft\u00eb se adresimi n\u00eb sh\u00ebrbimin ton\u00eb b\u00ebhet n\u00ebp\u00ebrmjet IP-s\u00eb s\u00eb nod\u00ebs dhe numrit t\u00eb portit. Ky variant lejon q\u00eb t\u00eb mos p\u00ebrdoren asnj\u00eb cloud publik, por k\u00ebrkon disa hapa shtes\u00eb. S\u00eb pari, ne kemi nevoj\u00eb p\u00ebr balancimin e ngarkes\u00ebs ton\u00eb, k\u00ebshtu q\u00eb do t\u00eb vendosim nj\u00eb balancues ngarkese NGINX n\u00eb klasterin ton\u00eb.<\/p>\n
    Hapi 6 \u2013 vendosim balancuesin e ngarkes\u00ebs<\/h4>\n
    \nMinikube ka disa funksione platform\u00ebs q\u00eb thjeshtojn\u00eb krijimin e komponent\u00ebve t\u00eb nevojsh\u00ebm p\u00ebr qasje nga jasht\u00eb, si kontrollor\u00ebt e ingress. Minikube vjen me kontrollorin ingress Nginx, dhe ne thjesht duhet ta aktivizojm\u00eb dhe ta konfigurojm\u00eb.<\/p>\n
    minikube addons enable ingress\n<\/code><\/pre>\n
    \nTani, me nj\u00eb komand\u00eb, do t\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 Po funksionon 1 33m\n<\/code><\/pre>\n
    <\/p>\n
    Hapi 7 \u2013 Konfigurojm\u00eb ingress<\/h4>\n
    \nTani duhet t\u00eb konfigurojm\u00eb kontrollorin ingress Nginx p\u00ebr t\u00eb pranuar k\u00ebrkesat hello-quarkus.<\/p>\n
    \"M\u00eb<\/p>\n
    \"M\u00eb<\/p>\n
    Dhe, p\u00ebrfundimisht, duhet ta aplikojm\u00eb k\u00ebt\u00eb konfigurat\u00eb.<\/p>\n
    \"M\u00eb<\/p>\n
    kubectl apply -f ingress.yml\n<\/code><\/pre>\n
    \"M\u00eb<\/p>\n
    Duke qen\u00eb se po i b\u00ebjm\u00eb t\u00eb gjitha k\u00ebto n\u00eb kompjuterin ton\u00eb, thjesht shtojm\u00eb IP-n\u00eb e nod\u00ebs son\u00eb n\u00eb skedarin \/etc\/hosts, p\u00ebr t\u00eb drejtuar k\u00ebrkesat http ndaj minikube-ton\u00eb n\u00eb balancuesin e ngarkes\u00ebs NGINX.<\/p>\n
    192.168.99.100 hello-quarkus.info\n<\/code><\/pre>\n
    \nTani \u00ebsht\u00eb, tani sh\u00ebrbimi yn\u00eb minikube \u00ebsht\u00eb n\u00eb dispozicion nga jasht\u00eb p\u00ebrmes kontrolluesit ingress Nginx.<\/p>\n
    \"M\u00eb<\/p>\n
    Pra, ishte e leht\u00eb, apo jo? Apo jo shum\u00eb?<\/h3>\n
    \"M\u00eb<\/p>\n
    Iniciimi n\u00eb OpenShift (Code Ready Containers)<\/h3>\n
    \nTani do t\u00eb shohim si t\u00eb b\u00ebhet kjo n\u00eb Red Hat OpenShift Container Platform (OCP).<\/p>\n
    Si n\u00eb rastin e minikube, ne zgjedhim skem\u00ebn me klaster nj\u00eb-nodsh\u00ebm OpenShift n\u00eb form\u00ebn e Code Ready Containers (CRC). Deri tani ai quhej minishift dhe ishte i bazuar n\u00eb projektin OpenShift Origin, nd\u00ebrsa tani \u00ebsht\u00eb CRC dhe \u00ebsht\u00eb nd\u00ebrtuar mbi platform\u00ebn Red Hat\u2019ove OpenShift Container.<\/p>\n
    K\u00ebtu, na falni, nuk mund t\u00eb ndalemi dhe t\u00eb mos themi: \"OpenShift \u00ebsht\u00eb i mrekulluesh\u00ebm!\"<\/p>\n
    Fillimisht menduam t\u00eb shkruajm\u00eb se zhvillimi n\u00eb OpenShift nuk ndryshon nga zhvillimi n\u00eb Kubernetes. Dhe n\u00eb thelb \u00ebsht\u00eb k\u00ebshtu. Por gjat\u00eb shkrimit t\u00eb k\u00ebtij artikulli, na erdh\u00ebn n\u00eb mendje sa shum\u00eb hapa t\u00eb panevojsh\u00ebm duhet t\u00eb b\u00ebsh kur nuk ke OpenShift, dhe prandaj \u00ebsht\u00eb, p\u00ebrs\u00ebri, i mrekulluesh\u00ebm. Ne e duam kur gjith\u00e7ka b\u00ebhet leht\u00eb, dhe si\u00e7 \u00ebsht\u00eb leht\u00eb krahasuar me minikube q\u00eb shembulli yn\u00eb zbulohet dhe fillon n\u00eb OpenShift, realisht na frym\u00ebzoi p\u00ebr t\u00eb shkruar k\u00ebt\u00eb postim.<\/p>\n
    Le t\u00eb p\u00ebrshkojm\u00eb procesin dhe t\u00eb shohim \u00e7far\u00eb do t\u00eb na nevojitet t\u00eb b\u00ebjm\u00eb.<\/p>\n
    Pra, n\u00eb shembullin me minikube ne filluam me Docker... Prit, nuk \u00ebsht\u00eb m\u00eb e nevojshme q\u00eb n\u00eb makin\u00eb t\u00eb jet\u00eb instaluar Docker.<\/p>\n
    Dhe git lokal nuk na nevojitet.
    \nDhe Maven nuk \u00ebsht\u00eb i nevojsh\u00ebm.
    \nDhe nuk \u00ebsht\u00eb e nevojshme t\u00eb krijoni manualisht imazhin e kontejnerit.
    \nDhe nuk \u00ebsht\u00eb e nevojshme t\u00eb k\u00ebrkoni ndonj\u00eb depot t\u00eb imazheve t\u00eb kontenier\u00ebve.
    \nDhe nuk \u00ebsht\u00eb e nevojshme t\u00eb instaloni kontrollin e ingress.
    \nDhe as konfigurimi i ingress nuk \u00ebsht\u00eb i nevojsh\u00ebm.<\/b><\/p>\n
    E kuptuat, po? P\u00ebr t\u00eb vendosur dhe nisur aplikacionin ton\u00eb n\u00eb OpenShift, nuk kemi nevoj\u00eb p\u00ebr asnj\u00eb nga gj\u00ebrat e lartp\u00ebrmendura. Procesi vet\u00eb duket si m\u00eb posht\u00eb.<\/p>\n
    Hapi 1 \u2013 Nisni klasterin tuaj OpenShift<\/h4>\n
    \nNe p\u00ebrdorim Code Ready Containers nga Red Hat, i cili n\u00eb thelb \u00ebsht\u00eb i nj\u00ebjti Minikube, por me nj\u00eb klaster nj\u00eb-nod\u00ebsh t\u00eb plot\u00eb 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
    \nSakt\u00ebsisht n\u00eb k\u00ebt\u00eb hap, thjesht\u00ebsia dhe leht\u00ebsia e OpenShift shfaqen n\u00eb gjith\u00eb shk\u00eblqimin e saj. Ashtu si n\u00eb t\u00eb gjitha shp\u00ebrndarjet e Kubernetes, ne kemi shum\u00eb m\u00ebnyra p\u00ebr t\u00eb nisur aplikacionin n\u00eb klaster. Dhe, si n\u00eb rastin e KUK, ne zgjedhim ve\u00e7an\u00ebrisht metod\u00ebn m\u00eb t\u00eb thjesht\u00eb.<\/p>\n
    OpenShift gjithmon\u00eb \u00ebsht\u00eb nd\u00ebrtuar si nj\u00eb platform\u00eb p\u00ebr krijimin dhe nisjen e aplikacioneve n\u00eb kontejner\u00eb. Nd\u00ebrtimi i kontejner\u00ebve ka qen\u00eb gjithmon\u00eb nj\u00eb pjes\u00eb e pandashme e k\u00ebsaj platforme, prandaj k\u00ebtu ka shum\u00eb burime t\u00eb tjera Kubernetes p\u00ebr detyra t\u00eb caktuara.<\/p>\n
    \u041c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c OpenShift’\u043e\u0432\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0446\u0435\u0441\u0441 Source 2 Image (S2I), \u0443 \u043a\u043e\u0442\u043e\u0440\u043e\u0433\u043e \u0435\u0441\u0442\u044c \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u0441\u043f\u043e\u0441\u043e\u0431\u043e\u0432 \u0434\u043b\u044f \u0442\u043e\u0433\u043e, \u0447\u0442\u043e\u0431\u044b \u0432\u0437\u044f\u0442\u044c \u043d\u0430\u0448 \u0438\u0441\u0445\u043e\u0434\u043d\u0438\u043a (\u043a\u043e\u0434 \u0438\u043b\u0438 \u0434\u0432\u043e\u0438\u0447\u043d\u044b\u0435 \u0444\u0430\u0439\u043b\u044b) \u0438 \u043f\u0440\u0435\u0432\u0440\u0430\u0442\u0438\u0442\u044c \u0435\u0433\u043e \u0432 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043d\u044b\u0439 \u043e\u0431\u0440\u0430\u0437, \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0435\u043c\u044b\u0439 \u0432 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0435 OpenShift.<\/p>\n
    P\u00ebr k\u00ebt\u00eb na nevojiten dy gj\u00ebra:<\/p>\n