{"id":92048,"date":"2020-08-22T07:42:57","date_gmt":"2020-08-22T05:42:57","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/sovremennye-prilozheniya-na-openshift-chast-3-openshift-kak-sreda-razrabotki-i-konvejery-openshift-pipelines"},"modified":"2020-08-22T07:42:57","modified_gmt":"2020-08-22T05:42:57","slug":"sovremennye-prilozheniya-na-openshift-chast-3-openshift-kak-sreda-razrabotki-i-konvejery-openshift-pipelines","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/sovremennye-prilozheniya-na-openshift-chast-3-openshift-kak-sreda-razrabotki-i-konvejery-openshift-pipelines","title":{"rendered":"Modern\u00ed aplikace na OpenShift, \u010d\u00e1st 3: OpenShift jako v\u00fdvojov\u00e9 prost\u0159ed\u00ed a potrub\u00ed OpenShift Pipelines","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ahoj v\u0161em v tomto blogu! Dnes m\u00e1te p\u0159ed sebou t\u0159et\u00ed p\u0159\u00edsp\u011bvek ze s\u00e9rie, ve kter\u00e9 ukazujeme, jak nasazovat modern\u00ed webov\u00e9 aplikace na Red Hat OpenShift.<\/p>\n

\"Modern\u00ed
\n
\nV p\u0159edchoz\u00edch dvou p\u0159\u00edsp\u011bvc\u00edch jsme se pod\u00edvali na to, jak nasadit modern\u00ed webov\u00e9 aplikace b\u011bhem n\u011bkolika m\u00e1lo krok\u016f a jak pou\u017e\u00edvat nov\u00fd obraz S2I v kombinaci s hotov\u00fdm HTTP serverem, nap\u0159\u00edklad NGINX, s pomoc\u00ed propojen\u00fdch sestaven\u00ed chained builds pro organizaci produk\u010dn\u00edho nasazen\u00ed.<\/p>\n

Dnes uk\u00e1\u017eeme, jak spustit na platform\u011b OpenShift v\u00fdvojov\u00fd server pro svou aplikaci a synchronizovat ho s m\u00edstn\u00edm souborov\u00fdm syst\u00e9mem, a tak\u00e9 si pov\u00edme o tom, co jsou OpenShift Pipelines a jak je pou\u017e\u00edvat jako alternativu k propojen\u00fdm sestaven\u00edm.
\n<\/a><\/noindex><\/p>\n

OpenShift jako v\u00fdvojov\u00e9 prost\u0159ed\u00ed<\/h3>\n

<\/p>\n

V\u00fdvojov\u00fd pracovn\u00ed postup (development workflow)<\/h4>\n

\nJak u\u017e bylo zm\u00edn\u011bno v prvn\u00edm p\u0159\u00edsp\u011bvku<\/a><\/noindex>, standardn\u00ed proces v\u00fdvoje pro modern\u00ed webov\u00e9 aplikace je vlastn\u011b jen n\u011bjak\u00fd 'v\u00fdvojov\u00fd server', kter\u00fd sleduje zm\u011bny v m\u00edstn\u00edch souborech. Kdy\u017e se tyto zm\u011bny objev\u00ed, spust\u00ed se sestaven\u00ed aplikace, a ta se pak aktualizuje v prohl\u00ed\u017ee\u010di.<\/p>\n

V\u011bt\u0161ina modern\u00edch r\u00e1mc\u016f m\u00e1 takov\u00fd 'v\u00fdvojov\u00fd server' zabudovan\u00fd ve sv\u00fdch p\u0159\u00edslu\u0161n\u00fdch p\u0159\u00edkazov\u00fdch n\u00e1stroj\u00edch.<\/p>\n

Lok\u00e1ln\u00ed p\u0159\u00edklad<\/h4>\n

\nNejd\u0159\u00edve se pod\u00edv\u00e1me, jak to funguje v p\u0159\u00edpad\u011b m\u00edstn\u00edho spu\u0161t\u011bn\u00ed aplikac\u00ed. Jako p\u0159\u00edklad pou\u017eijeme aplikaci React<\/a><\/noindex> z p\u0159edchoz\u00edch \u010dl\u00e1nk\u016f, a\u010dkoliv stejn\u00e9 koncepty pracovn\u00edho postupu se uplat\u0148uj\u00ed i ve v\u0161ech ostatn\u00edch modern\u00edch r\u00e1mc\u00edch.
\nTak\u017ee, abychom spustili 'v\u00fdvojov\u00fd server' v na\u0161em p\u0159\u00edkladu s React, zadejte n\u00e1sleduj\u00edc\u00ed p\u0159\u00edkaz:<\/p>\n

$ npm run start\n<\/code><\/pre>\n
\nPak v okn\u011b termin\u00e1lu uvid\u00edme p\u0159ibli\u017en\u011b toto:<\/p>\n
\"Modern\u00ed<\/p>\n
A na\u0161e aplikace se otev\u0159e v prohl\u00ed\u017ee\u010di podle v\u00fdchoz\u00edho nastaven\u00ed:<\/p>\n
\"Modern\u00ed<\/p>\n
Nyn\u00ed, pokud provedeme zm\u011bny v souboru, aplikace by se m\u011bla v prohl\u00ed\u017ee\u010di aktualizovat.<\/p>\n
OK, o v\u00fdvoji v m\u00edstn\u00edm re\u017eimu je v\u0161e jasn\u00e9, ale jak dos\u00e1hnout n\u011b\u010deho podobn\u00e9ho na OpenShift?<\/p>\n
V\u00fdvojov\u00fd server na OpenShift<\/h4>\n
\nPokud si pamatujete, v p\u0159edchoz\u00edm p\u0159\u00edsp\u011bvku<\/a><\/noindex>, jsme prob\u00edrali takzvanou f\u00e1zi spu\u0161t\u011bn\u00ed (run phase) obrazu S2I a vid\u011bli jsme, \u017ee na\u0161emu webov\u00e9mu aplikaci standardn\u011b obsluhuje modul serve.<\/p>\n
Pokud se v\u0161ak pod\u00edv\u00e1te pozorn\u011bji run script<\/a><\/noindex> z toho p\u0159\u00edkladu, existuje prom\u011bnn\u00e1 prost\u0159ed\u00ed $NPM_RUN, kter\u00e1 umo\u017e\u0148uje spu\u0161t\u011bn\u00ed vlastn\u00edho p\u0159\u00edkazu.<\/p>\n
Nap\u0159\u00edklad m\u016f\u017eete pou\u017e\u00edt modul nodeshift k nasazen\u00ed na\u0161\u00ed aplikace:<\/p>\n
$ npx nodeshift --deploy.env NPM_RUN=\"yarn start\" --dockerImage=nodeshift\/ubi8-s2i-web-app\n<\/code><\/pre>\n
\nPozn\u00e1mka: v\u00fd\u0161e uveden\u00fd p\u0159\u00edklad je uveden ve zjednodu\u0161en\u00e9 podob\u011b, aby ilustroval celkovou my\u0161lenku.<\/i><\/p>\n
Zde jsme do na\u0161eho nasazen\u00ed p\u0159idali prom\u011bnnou prost\u0159ed\u00ed NPM_RUN, kter\u00e1 \u0159\u00edk\u00e1 prov\u00e1d\u011bc\u00edmu kroku, \u017ee by m\u011bl spustit p\u0159\u00edkaz yarn start, kter\u00fd spust\u00ed v\u00fdvojov\u00fd server React uvnit\u0159 na\u0161eho OpenShift podu.<\/p>\n
Pokud se pod\u00edv\u00e1me na log b\u011b\u017e\u00edc\u00edho podu, bude to p\u0159ibli\u017en\u011b n\u00e1sleduj\u00edc\u00ed:<\/p>\n
\"Modern\u00ed<\/p>\n
Samoz\u0159ejm\u011b, to v\u0161echno nebude m\u00edt smysl, dokud nebudeme schopni synchronizovat m\u00edstn\u00ed k\u00f3d s k\u00f3dem, kter\u00fd je tak\u00e9 kontrolov\u00e1n na zm\u011bny, ale \u017eije na vzd\u00e1len\u00e9m serveru.<\/p>\n
Synchronizace vzd\u00e1len\u00e9ho a m\u00edstn\u00edho k\u00f3du<\/h4>\n
\nNa\u0161t\u011bst\u00ed s synchronizac\u00ed snadno pom\u016f\u017ee nodeshift a pro sledov\u00e1n\u00ed zm\u011bn m\u016f\u017eeme pou\u017e\u00edt p\u0159\u00edkaz watch.<\/p>\n
Tak\u017ee po proveden\u00ed p\u0159\u00edkazu pro nasazen\u00ed v\u00fdvojov\u00e9ho serveru pro na\u0161i aplikaci m\u016f\u017eeme bez obav pou\u017e\u00edt tento p\u0159\u00edkaz:<\/p>\n
$ npx nodeshift watch\n<\/code><\/pre>\n
\nV d\u016fsledku toho se p\u0159ipoj\u00ed k b\u011b\u017e\u00edc\u00edmu podu, kter\u00fd jsme vytvo\u0159ili o n\u011bco d\u0159\u00edve, aktivuje synchronizaci na\u0161ich m\u00edstn\u00edch soubor\u016f se vzd\u00e1len\u00fdm klastrem a soubory na na\u0161em m\u00edstn\u00edm syst\u00e9mu za\u010dnou b\u00fdt sledov\u00e1ny na zm\u011bny.<\/p>\n
Proto, pokud nyn\u00ed aktualizujeme soubor src\/App.js, syst\u00e9m na tyto zm\u011bny zareaguje, zkop\u00edruje je na vzd\u00e1len\u00fd klastr a spust\u00ed v\u00fdvojov\u00fd server, kter\u00fd pot\u00e9 aktualizuje na\u0161i aplikaci v prohl\u00ed\u017ee\u010di.<\/p>\n
Pro \u00faplnost uk\u00e1\u017eeme, jak tyto p\u0159\u00edkazy vypadaj\u00ed v celku:<\/p>\n
$ npx nodeshift --strictSSL=false --dockerImage=nodeshift\/ubi8-s2i-web-app --build.env YARN_ENABLED=true --expose --deploy.env NPM_RUN=\"yarn start\" --deploy.port 3000\n\n$ npx nodeshift watch --strictSSL=false\n<\/code><\/pre>\n
\nP\u0159\u00edkaz watch je abstrakc\u00ed nad p\u0159\u00edkazem oc rsync, podrobnosti o tom, jak to funguje, se m\u016f\u017eete dozv\u011bd\u011bt. zde<\/a><\/noindex>.<\/p>\n
To byl p\u0159\u00edklad pro React, ale stejnou metodu lze pou\u017e\u00edt i s jin\u00fdmi frameworky, sta\u010d\u00ed spr\u00e1vn\u011b zapsat prom\u011bnnou prost\u0159ed\u00ed NPM_RUN.
\n\u2003<\/p>\n
Pipelines Openshift<\/h3>\n
\"Modern\u00ed<\/p>\n
D\u00e1le si pov\u00edme o n\u00e1stroji OpenShift Pipelines a o tom, jak ho lze vyu\u017e\u00edt jako alternativu k souvisej\u00edc\u00edm sestaven\u00edm chained build.<\/p>\n
Co jsou OpenShift Pipelines<\/h4>\n
\nOpenShift Pipelines je cloudov\u011b orientovan\u00fd CI\/CD syst\u00e9m pro kontinu\u00e1ln\u00ed integraci a dod\u00e1n\u00ed, ur\u010den\u00fd k organizaci pipeline s vyu\u017eit\u00edm Tektonu. Tekton je flexibiln\u00ed Kubernetes-nativn\u00ed CI\/CD r\u00e1mec s otev\u0159en\u00fdm k\u00f3dem, kter\u00fd umo\u017e\u0148uje automatizaci nasazen\u00ed na r\u016fzn\u00fdch platform\u00e1ch (Kubernetes, serverless, virtu\u00e1ln\u00ed stroje atd.) t\u00edm, \u017ee abstrahuje od z\u00e1kladn\u00ed \u00farovn\u011b.<\/p>\n
Pro porozum\u011bn\u00ed tomuto \u010dl\u00e1nku jsou pot\u0159ebn\u00e9 ur\u010dit\u00e9 znalosti o Pipelines, proto d\u016frazn\u011b doporu\u010dujeme nejprve se sezn\u00e1mit s ofici\u00e1ln\u00edm v\u00fdukov\u00fdm materi\u00e1lem<\/a><\/noindex>.<\/p>\n
Nastaven\u00ed pracovn\u00edho prost\u0159ed\u00ed<\/h4>\n
\nAbychom si mohli vyzkou\u0161et p\u0159\u00edklady z tohoto \u010dl\u00e1nku, mus\u00edme nejprve p\u0159ipravit pracovn\u00ed prost\u0159ed\u00ed:<\/p>\n
    \n
  1. Nainstalujte a nastavte cluster OpenShift 4. V na\u0161ich p\u0159\u00edkladech pou\u017e\u00edv\u00e1me CodeReady Containers (CRD), pokyny k instalaci najdete zde<\/a><\/noindex>.<\/li>\n
  2. Jakmile bude cluster p\u0159ipraven, je t\u0159eba na n\u011bj nainstalovat Pipeline Operator. Nebojte se, je to snadn\u00e9, pokyny k instalaci zde<\/a><\/noindex>.<\/li>\n
  3. Na\u010d\u00edst Tekton CLI<\/a><\/noindex> (tkn) zde<\/a><\/noindex>.<\/li>\n
  4. Spus\u0165te n\u00e1stroj p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku create-react-app pro vytvo\u0159en\u00ed aplikace, kter\u00e1 bude n\u00e1sledn\u011b nasazena (je to jednoduch\u00e1 aplikace React<\/a><\/noindex>).<\/li>\n
  5. (Voliteln\u011b) Klonujte repozit\u00e1\u0159 pro lok\u00e1ln\u00ed spu\u0161t\u011bn\u00ed p\u0159\u00edkladu aplikace pomoc\u00ed p\u0159\u00edkazu npm install a pot\u00e9 npm start.<\/li>\n<\/ol>\n
    \nV repozit\u00e1\u0159i aplikace bude tak\u00e9 slo\u017eka k8s, kde budou um\u00edst\u011bny YAML soubory Kubernetes\/OpenShift pou\u017e\u00edvan\u00e9 pro nasazen\u00ed aplikace. Tam budou \u00fakoly, ClusterTasks, Resources a Pipelines, kter\u00e9 vytvo\u0159\u00edme v tomto repozit\u00e1\u0159e<\/a><\/noindex>.<\/p>\n
    Za\u010d\u00edn\u00e1me<\/h4>\n
    \nNejd\u0159\u00edve je t\u0159eba vytvo\u0159it nov\u00fd projekt v clusteru OpenShift pro n\u00e1\u0161 p\u0159\u00edklad. Nazveme tento projekt webapp-pipeline a vytvo\u0159\u00edme ho n\u00e1sleduj\u00edc\u00edm p\u0159\u00edkazem:<\/p>\n
    $ oc new-project webapp-pipeline\n<\/code><\/pre>\n
    \nD\u00e1le se toto jm\u00e9no projektu bude objevovat v k\u00f3du, tak\u017ee pokud se rozhodnete pojmenovat ho jinak, nezapome\u0148te odpov\u00eddaj\u00edc\u00edm zp\u016fsobem upravit k\u00f3d z p\u0159\u00edklad\u016f. Od t\u00e9to chv\u00edle se nebudeme \u0159\u00eddit shora dol\u016f, ale zdola nahoru: tedy nejprve vytvo\u0159\u00edme v\u0161echny komponenty pipeline a teprve potom samotnou pipeline.<\/p>\n
    Tak\u017ee, nejprve\u2026<\/p>\n
    \u00dakoly<\/h4>\n
    \nVytvo\u0159\u00edme p\u00e1r \u00faloh (tasks), kter\u00e9 potom pomohou nasadit aplikaci v r\u00e1mci na\u0161eho pipeline. Prvn\u00ed \u00faloha \u2013 apply_manifests_task \u2013 zaji\u0161\u0165uje aplikaci YAML soubor\u016f Kubernetes-rozsahu (service, deployment a route), kter\u00e9 se nach\u00e1z\u00ed ve slo\u017ece k8s na\u0161\u00ed aplikace. Druh\u00e1 \u00faloha \u2013 update_deployment_task \u2013 zaji\u0161\u0165uje aktualizaci ji\u017e nasazen\u00e9ho obrazu na ten, kter\u00fd vytv\u00e1\u0159\u00ed n\u00e1\u0161 pipeline.<\/p>\n
    Nebojte se, pokud to zat\u00edm nen\u00ed \u00fapln\u011b jasn\u00e9. Tyto \u00falohy jsou vlastn\u011b n\u011bco jako utility, podrobn\u011bji se jimi budeme zab\u00fdvat pozd\u011bji. Te\u010f si je jen vytvo\u0159\u00edme:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/tasks\/update_deployment_task.yaml\n$ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/tasks\/apply_manifests_task.yaml\n<\/code><\/pre>\n
    \nPak pomoc\u00ed p\u0159\u00edkazu tkn CLI zkontrolujeme, \u017ee \u00falohy byly vytvo\u0159eny:<\/p>\n
    $ tkn task ls\n\nNAME                AGE\napply-manifests     1 minute ago\nupdate-deployment   1 minute ago\n<\/code><\/pre>\n
    \nPozn\u00e1mka: Toto jsou lok\u00e1ln\u00ed \u00falohy va\u0161eho aktu\u00e1ln\u00edho projektu.<\/i><\/p>\n
    Klusterov\u00e9 \u00falohy Cluster tasks<\/h4>\n
    \nKlusterov\u00e9 \u00falohy jsou v podstat\u011b to sam\u00e9 jako jednoduch\u00e9 \u00falohy. To znamen\u00e1, \u017ee se jedn\u00e1 o opakovan\u011b pou\u017eiteln\u00e9 kolekce krok\u016f, kter\u00e9 se kombinuj\u00ed ur\u010dit\u00fdm zp\u016fsobem p\u0159i spu\u0161t\u011bn\u00ed konkr\u00e9tn\u00ed \u00falohy. Rozd\u00edl spo\u010d\u00edv\u00e1 v tom, \u017ee klusterov\u00e1 \u00faloha je dostupn\u00e1 kdekoli v r\u00e1mci klusteru. Abychom vid\u011bli seznam klusterov\u00fdch \u00faloh, kter\u00e9 se automaticky vytv\u00e1\u0159ej\u00ed p\u0159i p\u0159id\u00e1n\u00ed Pipeline Operator, znovu pou\u017eijeme p\u0159\u00edkaz tkn CLI:<\/p>\n
    $ tkn clustertask ls\n\nNAME                       AGE\nbuildah                    1 day ago\nbuildah-v0-10-0            1 day ago\njib-maven                  1 day ago\nkn                         1 day ago\nmaven                      1 day ago\nopenshift-client           1 day ago\nopenshift-client-v0-10-0   1 day ago\ns2i                        1 day ago\ns2i-go                     1 day ago\ns2i-go-v0-10-0             1 day ago\ns2i-java-11                1 day ago\ns2i-java-11-v0-10-0        1 day ago\ns2i-java-8                 1 day ago\ns2i-java-8-v0-10-0         1 day ago\ns2i-nodejs                 1 day ago\ns2i-nodejs-v0-10-0         1 day ago\ns2i-perl                   1 day ago\ns2i-perl-v0-10-0           1 day ago\ns2i-php                    1 day ago\ns2i-php-v0-10-0            1 day ago\ns2i-python-3               1 day ago\ns2i-python-3-v0-10-0       1 day ago\ns2i-ruby                   1 day ago\ns2i-ruby-v0-10-0           1 day ago\ns2i-v0-10-0                1 day ago\n<\/code><\/pre>\n
    \nA nyn\u00ed vytvo\u0159\u00edme dv\u011b klusterov\u00e9 \u00falohy. Prvn\u00ed bude generovat obraz S2I a odes\u00edlat jej do intern\u00edho registru OpenShift; druh\u00e1 \u2013 provede sestaven\u00ed na\u0161eho obrazu na z\u00e1klad\u011b NGINX, pou\u017e\u00edvaj\u00edc\u00ed jako obsah ji\u017e sestavenou aplikaci.<\/p>\n
    Vytv\u00e1\u0159\u00edme a odes\u00edl\u00e1me obraz<\/h4>\n
    \nP\u0159i vytv\u00e1\u0159en\u00ed prvn\u00ed \u00falohy si zopakujeme to, co jsme ji\u017e d\u011blali v p\u0159edchoz\u00edm \u010dl\u00e1nku o propojen\u00fdch sestaven\u00edch. P\u0159ipom\u00edn\u00e1me, \u017ee jsme pou\u017eili obraz S2I (ubi8-s2i-web-app), abychom 'sestavili' na\u0161i aplikaci, a nakonec jsme z\u00edskali obraz ulo\u017een\u00fd v intern\u00edm registru OpenShift. Nyn\u00ed pou\u017eijeme tento S2I obraz webov\u00e9 aplikace k vytvo\u0159en\u00ed DockerFile pro na\u0161i aplikaci, a pot\u00e9 nasad\u00edme Buildah, abychom provedli skute\u010dn\u00e9 sestaven\u00ed a poslali z\u00edskan\u00fd obraz do intern\u00edho registru OpenShift, proto\u017ee pr\u00e1v\u011b to OpenShift d\u011bl\u00e1, kdy\u017e nasazujete sv\u00e9 aplikace pomoc\u00ed NodeShift.<\/p>\n
    Pt\u00e1te se, odkud jsme to v\u0161echno vzali? Z \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 official Node.js<\/a><\/noindex>, jednodu\u0161e jsme jej zkop\u00edrovali a p\u0159izp\u016fsobili si ho.<\/p>\n
    Tak, a nyn\u00ed vytvo\u0159\u00edme clusterovou \u00falohu s n\u00e1zvem s2i-web-app:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/clustertasks\/s2i-web-app-task.yaml\n<\/code><\/pre>\n
    \nNebudeme to podrobn\u011b rozeb\u00edrat, pouze se zam\u011b\u0159\u00edme na parametr OUTPUT_DIR:<\/p>\n
    params:\n      - name: OUTPUT_DIR\n        description: M\u00edsto, kde se nach\u00e1z\u00ed v\u00fdstupn\u00ed adres\u00e1\u0159 sestaven\u00ed\n        default: build\n<\/code><\/pre>\n
    \nVe v\u00fdchoz\u00edm nastaven\u00ed m\u00e1 tento parametr hodnotu build, kam React ukl\u00e1d\u00e1 sestaven\u00fd obsah. V jin\u00fdch frameworc\u00edch se pou\u017e\u00edvaj\u00ed jin\u00e9 cesty, nap\u0159\u00edklad v Ember je to dist. V\u00fdstup na\u0161\u00ed prvn\u00ed clusterov\u00e9 \u00falohy bude obraz, kter\u00fd obsahuje HTML, JavaScript a CSS, kter\u00e9 jsme sestavili.<\/p>\n
    Sestavujeme obraz zalo\u017een\u00fd na NGINX<\/h4>\n
    \nPokud jde o na\u0161i druhou clusterovou \u00falohu, ta by m\u011bla sestavovat obraz na z\u00e1klad\u011b NGINX s vyu\u017eit\u00edm obsahu ji\u017e sestaven\u00e9 aplikace. V podstat\u011b jde o tu \u010d\u00e1st p\u0159edchoz\u00edho odd\u00edlu, kde jsme se zab\u00fdvali propojen\u00fdmi sestaven\u00edmi.<\/p>\n
    K tomu \u2013 p\u0159esn\u011b tak, jak jsme to ud\u011blali v\u00fd\u0161e \u2013 vytvo\u0159\u00edme clusterovou \u00falohu webapp-build-runtime:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/clustertasks\/webapp-build-runtime-task.yaml\n<\/code><\/pre>\n
    \nPokud se pod\u00edv\u00e1te na k\u00f3d t\u011bchto clusterov\u00fdch \u00faloh, uvid\u00edte, \u017ee tam nen\u00ed konkretizov\u00e1no Git repozit\u00e1\u0159, se kter\u00fdm pracujeme, nebo n\u00e1zvy obraz\u016f, kter\u00e9 vytv\u00e1\u0159\u00edme. Ur\u010dujeme pouze, co skute\u010dn\u011b p\u0159ed\u00e1v\u00e1me do Gitu, nebo n\u011bjak\u00fd obraz, kam je t\u0159eba vyexportovat v\u00fdsledn\u00fd obraz. Pr\u00e1v\u011b proto lze tyto clusterov\u00e9 \u00falohy op\u011btovn\u011b pou\u017e\u00edt i p\u0159i pr\u00e1ci s jin\u00fdmi aplikacemi.<\/p>\n
    A zde elegantn\u011b p\u0159ech\u00e1z\u00edme k dal\u0161\u00edmu bodu\u2026<\/p>\n
    Zdroje<\/h4>\n
    \nTak\u017ee, jak jsme pr\u00e1v\u011b \u0159ekli, clusteringov\u00e9 \u00fakoly by m\u011bly b\u00fdt co nejv\u00edce obecn\u00e9. Mus\u00edme vytvo\u0159it zdroje, kter\u00e9 budou pou\u017eity na vstupu (Git repozit\u00e1\u0159) a na v\u00fdstupu (kone\u010dn\u00e9 obrazy). Prvn\u00edm zdrojem, kter\u00fd pot\u0159ebujeme, je Git, kde se nach\u00e1z\u00ed na\u0161e aplikace, n\u011bco jako toto:<\/p>\n
    # This resource is the location of the git repo with the web application source\napiVersion: tekton.dev\/v1alpha1\nkind: PipelineResource\nmetadata:\n  name: web-application-repo\nspec:\n  type: git\n  params:\n    - name: url\n      value: https:\/\/github.com\/nodeshift-starters\/react-pipeline-example\n    - name: revision\n      value: master\n<\/code><\/pre>\n
    \nZde m\u00e1 PipelineResource typ git. Kl\u00ed\u010d url v sekci params ukazuje na konkr\u00e9tn\u00ed repozit\u00e1\u0159 a nastavuje v\u011btev master (to je voliteln\u00e9, ale p\u00ed\u0161eme to pro kompletnost).<\/p>\n
    Nyn\u00ed mus\u00edme vytvo\u0159it zdroj pro obraz, kam budou ukl\u00e1d\u00e1ny v\u00fdsledky vykon\u00e1n\u00ed \u00fakolu s2i-web-app, d\u011bl\u00e1 se to takto:<\/p>\n
    # This resource is the result of running "npm run build",  the resulting built files will be located in \/opt\/app-root\/output\napiVersion: tekton.dev\/v1alpha1\nkind: PipelineResource\nmetadata:\n  name: built-web-application-image\nspec:\n  type: image\n  params:\n    - name: url\n      value: image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/built-web-application:latest\n<\/code><\/pre>\n
    \nZde m\u00e1 PipelineResource typ image a hodnota parametru url ukazuje na intern\u00ed OpenShift Image Registry, konkr\u00e9tn\u011b na ten, kter\u00fd se nach\u00e1z\u00ed v prostoru webapp-pipeline. Nezapome\u0148te zm\u011bnit tento parametr, pokud pou\u017e\u00edv\u00e1te jin\u00fd prostor.<\/p>\n
    A kone\u010dn\u011b, posledn\u00ed zdroj, kter\u00fd budeme pot\u0159ebovat, bude tak\u00e9 m\u00edt typ image a to bude kone\u010dn\u00fd obraz NGINX, kter\u00fd bude pou\u017eit p\u0159i nasazen\u00ed:<\/p>\n
    # This resource is the image that will be just the static html, css, js files being run with nginx\napiVersion: tekton.dev\/v1alpha1\nkind: PipelineResource\nmetadata:\n  name: runtime-web-application-image\nspec:\n  type: image\n  params:\n    - name: url\n      value: image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/runtime-web-application:latest\n<\/code><\/pre>\n
    \nOp\u011bt si dejte pozor, \u017ee tento zdroj ukl\u00e1d\u00e1 obraz do intern\u00edho registru OpenShift ve jmenn\u00e9m prostoru webapp-pipeline.<\/p>\n
    Abychom mohli vytvo\u0159it v\u0161echny tyto zdroje najednou, pou\u017eijeme p\u0159\u00edkaz create:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/resources\/resource.yaml\n<\/code><\/pre>\n
    \nMo\u017en\u00e9 ov\u011b\u0159it, \u017ee byly zdroje vytvo\u0159eny, lze takto:<\/p>\n
    $ tkn resource ls\n<\/code><\/pre>\n
    <\/p>\n
    Pipeline<\/h4>\n
    \nTe\u010f, kdy\u017e m\u00e1me v\u0161echny pot\u0159ebn\u00e9 komponenty, slo\u017e\u00edme z nich pipeline t\u00edmto p\u0159\u00edkazem:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/pipelines\/build-and-deploy-react.yaml\n<\/code><\/pre>\n
    \nAle ne\u017e spust\u00edme tento p\u0159\u00edkaz, pod\u00edvejme se na tyto komponenty. Prvn\u00edm je n\u00e1zev:<\/p>\n
    apiVersion: tekton.dev\/v1alpha1\nkind: Pipeline\nmetadata:\n  name: build-and-deploy-react\n<\/code><\/pre>\n
    \nPot\u00e9 v sekci spec vid\u00edme ur\u010den\u00ed zdroj\u016f, kter\u00e9 jsme vytvo\u0159ili d\u0159\u00edve:<\/p>\n
    spec:\n  resources:\n    - name: web-application-repo\n      type: git\n    - name: built-web-application-image\n      type: image\n    - name: runtime-web-application-image\n      type: image\n<\/code><\/pre>\n
    \nPot\u00e9 vytv\u00e1\u0159\u00edme \u00fakoly, kter\u00e9 mus\u00ed n\u00e1\u0161 pipeline splnit. Nejd\u0159\u00edve mus\u00ed vykonat n\u00e1mi ji\u017e vytvo\u0159en\u00fd \u00fakol s2i-web-app:<\/p>\n
    tasks:\n    - name: build-web-application\n      taskRef:\n        name: s2i-web-app\n        kind: ClusterTask\n<\/code><\/pre>\n
    \nTento \u00fakol bere vstupn\u00ed (gir-zdroj) a v\u00fdstupn\u00ed (zdroj built-web-application-image) parametry. Tak\u00e9 j\u00ed p\u0159ed\u00e1v\u00e1me speci\u00e1ln\u00ed parametr, aby neov\u011b\u0159ovala TLS, proto\u017ee pou\u017e\u00edv\u00e1me self-signed certifik\u00e1ty:<\/p>\n
    resources:\n        inputs:\n          - name: source\n            resource: web-application-repo\n        outputs:\n          - name: image\n            resource: built-web-application-image\n      params:\n        - name: TLSVERIFY\n          value: \"false\"\n<\/code><\/pre>\n
    \nDal\u0161\u00ed \u00fakol je t\u00e9m\u011b\u0159 stejn\u00fd, jen zde se vol\u00e1 ji\u017e vytvo\u0159en\u00fd clusterov\u00fd \u00fakol webapp-build-runtime:<\/p>\n
    name: build-runtime-image\n    taskRef:\n      name: webapp-build-runtime\n      kind: ClusterTask\n<\/code><\/pre>\n
    \nStejn\u011b jako u p\u0159edchoz\u00edho \u00fakolu p\u0159ed\u00e1v\u00e1me zdroj, ale nyn\u00ed je to built-web-application-image (v\u00fdstup na\u0161eho p\u0159edchoz\u00edho \u00fakolu). A jako v\u00fdstup op\u011bt definujeme obraz. Proto\u017ee tento \u00fakol mus\u00ed b\u00fdt proveden po p\u0159edchoz\u00edm, p\u0159id\u00e1me pole runAfter:<\/p>\n
    resources:\n        inputs:\n          - name: image\n            resource: built-web-application-image\n        outputs:\n          - name: image\n            resource: runtime-web-application-image\n        params:\n        - name: TLSVERIFY\n          value: \"false\"\n      runAfter:\n        - build-web-application\n<\/code><\/pre>\n
    \nN\u00e1sleduj\u00edc\u00ed dv\u011b \u00fakoly odpov\u00eddaj\u00ed za aplikaci YAML soubor\u016f slu\u017eby, trasy a nasazen\u00ed, kter\u00e9 se nach\u00e1zej\u00ed v adres\u00e1\u0159i k8s na\u0161eho webov\u00e9 aplikace, a tak\u00e9 za aktualizaci tohoto nasazen\u00ed p\u0159i vytv\u00e1\u0159en\u00ed nov\u00fdch obraz\u016f. Tyto dv\u011b clusterov\u00e9 \u00fakoly jsme definovali na za\u010d\u00e1tku \u010dl\u00e1nku.<\/p>\n
    Spu\u0161t\u011bn\u00ed kan\u00e1lov\u00e9ho zpracov\u00e1n\u00ed<\/h4>\n
    \nTak\u017ee v\u0161echny \u010d\u00e1sti na\u0161eho pipeline jsou vytvo\u0159eny a spust\u00edme ji n\u00e1sleduj\u00edc\u00edm p\u0159\u00edkazem:<\/p>\n
    $ tkn pipeline start build-and-deploy-react\n<\/code><\/pre>\n
    \nV t\u00e9to f\u00e1zi se p\u0159\u00edkazov\u00fd \u0159\u00e1dek pou\u017e\u00edv\u00e1 v interaktivn\u00edm re\u017eimu a je t\u0159eba vyb\u00edrat odpov\u00eddaj\u00edc\u00ed zdroje v odpov\u011bdi na ka\u017ed\u00fd jeho dotaz: pro zdroj git vybereme web-application-repo, pot\u00e9 pro zdroj prvn\u00edho obrazu \u2013 built-web-application-image, a nakonec pro zdroj druh\u00e9ho obrazu \u2013 runtime-web-application-image:<\/p>\n
    ? Choose the git resource to use for web-application-repo: web-application-repo (https:\/\/github.com\/nodeshift-starters\/react-pipeline-example)\n? Choose the image resource to use for built-web-application-image: built-web-application-image (image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/built-web-\napplication:latest)\n? Choose the image resource to use for runtime-web-application-image: runtime-web-application-image (image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/runtim\ne-web-application:latest)\nPipelinerun started: build-and-deploy-react-run-4xwsr\n<\/code><\/pre>\n
    \nNyn\u00ed zkontrolujeme stav pipeline pomoc\u00ed n\u00e1sleduj\u00edc\u00edho p\u0159\u00edkazu:<\/p>\n
    $ tkn pipeline logs -f\n<\/code><\/pre>\n
    \nPot\u00e9, co pipeline spust\u00ed a aplikace se nasad\u00ed, po\u017e\u00e1d\u00e1me o zve\u0159ejn\u011bnou trasu n\u00e1sleduj\u00edc\u00edm p\u0159\u00edkazem:<\/p>\n
    $ oc get route react-pipeline-example --template='http:\/\/{{.spec.host}}'\n<\/code><\/pre>\n
    \nPro lep\u0161\u00ed vizualizaci m\u016f\u017eeme pod\u00edvat na na\u0161i pipeline v re\u017eimu Developer webov\u00e9 konzole v sekci Pipeline<\/b>, jak je zn\u00e1zorn\u011bno na Obr. 1.<\/p>\n
    \"Modern\u00ed<\/p>\n
    Obr.1. P\u0159ehled spu\u0161t\u011bn\u00fdch pipeline.<\/i><\/p>\n
    Kliknut\u00edm na spu\u0161t\u011bnou pipeline se zobraz\u00ed dal\u0161\u00ed informace, jak je zn\u00e1zorn\u011bno na Obr.2.<\/p>\n
    \"Modern\u00ed<\/p>\n
    Obr. 2. Dal\u0161\u00ed informace o pipeline.<\/i><\/p>\n
    Po dal\u0161\u00edch informac\u00edch si m\u016f\u017eeme prohl\u00e9dnout spu\u0161t\u011bn\u00e9 aplikace ve zobrazen\u00ed Topology<\/b>, jak je zn\u00e1zorn\u011bno na Obr.3.<\/p>\n
    \"Modern\u00ed<\/p>\n
    Obr 3. Spu\u0161t\u011bn\u00fd pod.<\/i><\/p>\n
    Kliknut\u00edm na kruhovou ikonu v prav\u00e9m horn\u00edm rohu ikony otev\u0159e na\u0161i aplikaci, jak je zn\u00e1zorn\u011bno na Obr.4.<\/p>\n
    \"Modern\u00ed<\/p>\n
    Obr. 4. Spu\u0161t\u011bn\u00e1 aplikace React.<\/i><\/p>\n
    Z\u00e1v\u011br<\/h3>\n
    \nTak\u017ee jsme uk\u00e1zali, jak spustit na OpenShift v\u00fdvojov\u00fd server pro svou aplikaci a synchronizovat jej s m\u00edstn\u00edm souborov\u00fdm syst\u00e9mem. Tak\u00e9 jsme se pod\u00edvali, jak simulovat chained-build template pomoc\u00ed OpenShift Pipelines. V\u0161echny k\u00f3dy p\u0159\u00edklad\u016f z tohoto \u010dl\u00e1nku najdete zde<\/a><\/noindex>.<\/p>\n
    Dal\u0161\u00ed zdroje (EN)<\/h3>\n
    <\/p>\n