{"id":76769,"date":"2020-04-04T13:42:27","date_gmt":"2020-04-04T11:42:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet"},"modified":"2020-04-04T13:42:27","modified_gmt":"2020-04-04T11:42:27","slug":"content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","title":{"rendered":"Tagovanie na z\u00e1klade obsahu vo werf: pre\u010do a ako to funguje?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Tagovanie na z\u00e1klade obsahu vo werf: pre\u010do a ako to funguje?\" src=\"\/wp-content\/uploads\/2020\/04\/494346bbee96cc2b6c838491ba1c67fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/werf.io\/\">werf<\/a><\/noindex> \u2014 n\u00e1\u0161 GitOps CLI n\u00e1stroj s otvoren\u00fdm k\u00f3dom na zostavovanie a dod\u00e1vanie aplik\u00e1ci\u00ed do Kubernetes. V <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/493170\/\">verzii v1.1<\/a><\/noindex> bola predstaven\u00e1 nov\u00e1 funkcia v zostavova\u010di obrazov: ozna\u010dovanie obrazov na z\u00e1klade obsahu alebo <i>content-based tagging<\/i>. Doteraz typick\u00e1 sch\u00e9ma ozna\u010dovania v werf predpokladala ozna\u010dovanie Docker obrazov na z\u00e1klade Git zna\u010diek, Git vetiev alebo Git commitov. Av\u0161ak v\u0161etky tieto sch\u00e9my maj\u00fa nedostatky, ktor\u00e9 s\u00fa \u00faplne vyrie\u0161en\u00e9 novou strat\u00e9giou ozna\u010dovania. Podrobnosti o nej a \u010do ju rob\u00ed takou dobrou \u2014 pod katom.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Nasadenie s\u00faboru mikroslu\u017eieb z jedn\u00e9ho Git repozit\u00e1ra<\/h2>\n<p>\n\u010casto sa vyskytuje situ\u00e1cia, ke\u010f je aplik\u00e1cia rozdelen\u00e1 na mno\u017estvo viac-menej nez\u00e1visl\u00fdch slu\u017eieb. Uvo\u013enenia t\u00fdchto slu\u017eieb m\u00f4\u017eu prebieha\u0165 nez\u00e1visle: naraz m\u00f4\u017ee by\u0165 uvo\u013enen\u00fd jeden alebo viacero slu\u017eieb, zvy\u0161n\u00e9 musia pritom na\u010falej fungova\u0165 bez ak\u00fdchko\u013evek zmien. Ale z poh\u013eadu ukladania k\u00f3du a spr\u00e1vy projektu je pohodlnej\u0161ie dr\u017ea\u0165 tak\u00e9to slu\u017eby aplik\u00e1cie v jednotnom repozit\u00e1ri.<\/p>\n<p>S\u00fa situ\u00e1cie, ke\u010f s\u00fa slu\u017eby skuto\u010dne nez\u00e1visl\u00e9 a nie s\u00fa spojen\u00e9 s jednou aplik\u00e1ciou. V takom pr\u00edpade bud\u00fa umiestnen\u00e9 v samostatn\u00fdch projektoch a ich uvo\u013enenie bude realizovan\u00e9 cez samostatn\u00e9 procesy CI\/CD v ka\u017edom z projektov.<\/p>\n<p>Av\u0161ak v skuto\u010dnosti v\u00fdvoj\u00e1ri \u010dasto rozde\u013euj\u00fa jednotn\u00fa aplik\u00e1ciu na nieko\u013eko mikroslu\u017eieb, ale zaklada\u0165 pre ka\u017ed\u00fa samostatn\u00fd repozit\u00e1r a projekt\u2026 \u2014 je zjavn\u00fd overkill. Pr\u00e1ve o tejto situ\u00e1cii bude \u010falej re\u010d: nieko\u013eko tak\u00fdchto mikroslu\u017eieb sa nach\u00e1dza v jednotnom repozit\u00e1ri projektu a uvo\u013enenia prebiehaj\u00fa prostredn\u00edctvom jedn\u00e9ho procesu v CI\/CD.<\/p>\n<h3>Ozna\u010dovanie pod\u013ea Git vetvy a Git zna\u010dky<\/h3>\n<p>\nPovedzme, \u017ee sa pou\u017e\u00edva najroz\u0161\u00edrenej\u0161ia strat\u00e9gia ozna\u010dovania \u2014 <i>tag-or-branch<\/i>. Pre Git vetvy s\u00fa obrazy ozna\u010dovan\u00e9 n\u00e1zvom vetvy, pre jednu vetvu existuje v jednom momente iba jeden publikovan\u00fd obraz s n\u00e1zvom tejto vetvy. Pre Git zna\u010dky s\u00fa obrazy ozna\u010dovan\u00e9 pr\u00edslu\u0161n\u00fdm menom zna\u010dky.<\/p>\n<p>Pri vytvoren\u00ed novej Git zna\u010dky \u2014 napr\u00edklad pri vydan\u00ed novej verzie \u2014 pre v\u0161etky obrazy projektu v Docker Registry bude vytvoren\u00fd nov\u00fd Docker tag:<\/p>\n<ul>\n<li> <code>myregistry.org\/myproject\/frontend:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice1:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice2:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice3:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice4:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice5:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/database:v1.1.10<\/code><\/li>\n<\/ul>\n<p>\nTieto nov\u00e9 n\u00e1zvy obrazov sa pren\u00e1\u0161aj\u00fa cez Helm \u0161abl\u00f3ny do konfigur\u00e1cie Kubernetes. Pri spusten\u00ed nasadenia pr\u00edkazom <code>werf deploy<\/code> sa aktualizuje pole <code>obr\u00e1zok<\/code> v manifestoch zdrojov Kubernetes a re\u0161tartuj\u00fa sa pr\u00edslu\u0161n\u00e9 zdroje kv\u00f4li zmenen\u00e9mu n\u00e1zvu obrazu.<\/p>\n<p><b>Probl\u00e9m<\/b>: v pr\u00edpade, \u017ee sa obsah obrazu re\u00e1lne nezmenil od predch\u00e1dzaj\u00faceho nasadenia (Git-tag), ale len jeho Docker-tag, doch\u00e1dza k <i>zbyto\u010dn\u00e9mu<\/i> re\u0161tartu tejto aplik\u00e1cie a m\u00f4\u017ee nastat nejak\u00fd v\u00fdpadok. Hoci neexistovali \u017eiadne skuto\u010dn\u00e9 d\u00f4vody na vykonanie tohto re\u0161tartu.<\/p>\n<p>Ako d\u00f4sledok, pri aktu\u00e1lnej sch\u00e9me zna\u010dkovania je potrebn\u00e9 ma\u0165 nieko\u013eko samostatn\u00fdch Git-repozit\u00e1rov a objavuje sa probl\u00e9m s organiz\u00e1ciou nasadenia t\u00fdchto viacer\u00fdch repozit\u00e1rov. Celkovo sa tak\u00e1 sch\u00e9ma jav\u00ed ako pre\u0165a\u017een\u00e1 a zlo\u017eit\u00e1. Je lep\u0161ie zl\u00fa\u010di\u0165 viac slu\u017eieb do jedn\u00e9ho repozit\u00e1ra a vytv\u00e1ra\u0165 tak\u00e9 Docker-tagy, aby sa zabr\u00e1nilo zbyto\u010dn\u00fdm re\u0161tartom.<\/p>\n<h3>Zna\u010dkovanie pod\u013ea Git-commit<\/h3>\n<p>\nV werf existuje aj strat\u00e9gia zna\u010dkovania s\u00favisiaca s Git-commitmi.<\/p>\n<p>Git-commit je identifik\u00e1tor obsahu Git-repozit\u00e1ra a z\u00e1vis\u00ed od hist\u00f3rie zmien s\u00faborov v Git-repozit\u00e1ri, preto sa zd\u00e1 logick\u00e9 pou\u017e\u00edva\u0165 ho na zna\u010dkovanie obrazov v Docker Registry.<\/p>\n<p>Av\u0161ak zna\u010dkovanie pod\u013ea Git-commitu m\u00e1 tie ist\u00e9 nev\u00fdhody ako pri Git-branch alebo Git-tagoch:<\/p>\n<ul>\n<li> Mohol by\u0165 vytvoren\u00fd pr\u00e1zdny commit, ktor\u00fd nemen\u00ed s\u00fabory, ale Docker-tag obrazu sa zmen\u00ed.<\/li>\n<li> Mohol by\u0165 vytvoren\u00fd merge-commit, ktor\u00fd nemen\u00ed s\u00fabory, ale Docker-tag obrazu sa zmen\u00ed.<\/li>\n<li> Mohol by\u0165 vytvoren\u00fd commit, ktor\u00fd men\u00ed tie s\u00fabory v Git, ktor\u00e9 sa do obrazu nepren\u00e1\u0161aj\u00fa, a Docker-tag obrazu sa op\u00e4\u0165 zmen\u00ed.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Zna\u010dkovanie pod\u013ea n\u00e1zvu Git-branch neodr\u00e1\u017ea verziu obrazu<\/h2>\n<p>\nExistuje aj \u010fal\u0161\u00ed probl\u00e9m s\u00favisiaci so strat\u00e9giou zna\u010dkovania pod\u013ea Git-branch.<\/p>\n<p>Zna\u010dkovanie pod\u013ea n\u00e1zvu vetvy funguje tak dlho, pokia\u013e s\u00fa commity tejto vetvy zhroma\u017e\u010fovan\u00e9 postupne v chronologickom porad\u00ed.<\/p>\n<p>Ak v aktu\u00e1lnom sch\u00e9me pou\u017e\u00edvate\u013e spust\u00ed prebudovanie star\u00e9ho commitu viazan\u00e9ho na ur\u010dit\u00fa vetvu, werf prep\u00ed\u0161e obraz pod\u013ea pr\u00edslu\u0161n\u00e9ho Docker-tag-u novou verziou obrazu pre star\u00fd commit. V\u0161etky nasadenia pou\u017e\u00edvaj\u00face tento tag od tohto momentu riskuj\u00fa, \u017ee po\u010das re\u0161tartu podov na\u010d\u00edtaj\u00fa in\u00fa verziu obrazu, \u010do sp\u00f4sob\u00ed, \u017ee na\u0161a aplik\u00e1cia strat\u00ed spojenie s CI syst\u00e9mom a dostane sa do desynchroniz\u00e1cie.<\/p>\n<p>Okrem toho, pri s\u00e9riov\u00fdch push-och do jednej vetvy s mal\u00fdm odstupom \u010dasu medzi nimi m\u00f4\u017ee star\u00fd commit by\u0165 spracovan\u00fd nesk\u00f4r ako nov\u0161\u00ed: star\u0161ia verzia obrazu prepisuje nov\u00fa pod\u013ea tagu Git-vetvy. Tak\u00e9to probl\u00e9my m\u00f4\u017ee rie\u0161i\u0165 CI\/CD syst\u00e9m (napr\u00edklad v GitLab CI pre s\u00e9riu commitov sa sp\u00fa\u0161\u0165a pipeline posledn\u00e9ho). Av\u0161ak, nie v\u0161etky syst\u00e9my to podporuj\u00fa a mal by existova\u0165 spo\u013eahlivej\u0161\u00ed sp\u00f4sob, ako zabr\u00e1ni\u0165 takejto z\u00e1kladnej probl\u00e9my.<\/p>\n<h2>\u010co je to ozna\u010dovanie na z\u00e1klade obsahu?<\/h2>\n<p>\nTak\u017ee, \u010do presne znamen\u00e1 ozna\u010dovanie na z\u00e1klade obsahu \u2014 tagovanie obrazov pod\u013ea obsahu.<\/p>\n<p>Na vytvorenie Docker-tagov sa nepou\u017e\u00edvaj\u00fa primit\u00edva Git-a (Git-vetva, Git-tag\u2026), ale kontroln\u00e1 suma spojen\u00e1 s:<\/p>\n<ul>\n<li> <i>obsahom obrazu<\/i>. Identifik\u00e1tor-tagu obrazu odr\u00e1\u017ea jeho obsah. Pri zostavovan\u00ed novej verzie tento identifik\u00e1tor nezmen\u00ed, ak sa v obraze nezmenili s\u00fabory;<\/li>\n<li> <i>hist\u00f3riou vytv\u00e1rania tohto obrazu v Gite<\/i>. Obrazy, ktor\u00e9 s\u00favisia s r\u00f4znymi Git-vetvami a r\u00f4znou hist\u00f3riou zostavovania prostredn\u00edctvom werf, bud\u00fa ma\u0165 r\u00f4zne tag-identifik\u00e1tory.<\/li>\n<\/ul>\n<p>\nAko tak\u00fd tag-identifik\u00e1tor sl\u00fa\u017ei tzv. <b>podpis f\u00e1z obrazu<\/b>.<\/p>\n<p>Ka\u017ed\u00fd obraz pozost\u00e1va z mno\u017einy f\u00e1z: <code>z<\/code>, <code>before-install<\/code>, <code>git-archive<\/code>, <code>install<\/code>, <code>imports-after-install<\/code>, <code>before-setup<\/code>,\u2026 <code>git-latest-patch<\/code> at\u010f. Ka\u017ed\u00e1 f\u00e1za m\u00e1 identifik\u00e1tor, ktor\u00fd odr\u00e1\u017ea jej obsah, \u2014 <b>podpis f\u00e1zy<\/b> <i>(podpis f\u00e1zy)<\/i>.<\/p>\n<p>Fin\u00e1lny obraz, pozost\u00e1vaj\u00faci z t\u00fdchto f\u00e1z, je tagovan\u00fd tzv. podpisom s\u00faboru t\u00fdchto f\u00e1z \u2014 <b>podpis f\u00e1z<\/b>, \u2014 ktor\u00fd je zov\u0161eobec\u0148uj\u00faci pre v\u0161etky f\u00e1zy obrazu.<\/p>\n<p>Ka\u017ed\u00fd obraz z konfigur\u00e1cie <code>werf.yaml<\/code> v z\u00e1sade bude ma\u0165 svoj vlastn\u00fd tak\u00fd podpis a, pod\u013ea toho, Docker-tag.<\/p>\n<p>Podpis f\u00e1z rie\u0161i v\u0161etky uveden\u00e9 probl\u00e9my:<\/p>\n<ul>\n<li> Je odoln\u00fd vo\u010di pr\u00e1zdnym Git-commitom.<\/li>\n<li> Je odoln\u00fd vo\u010di Git-commitom, ktor\u00e9 menia s\u00fabory, ktor\u00e9 nie s\u00fa relevantn\u00e9 pre obraz.<\/li>\n<li> Nevedie k probl\u00e9mu s prepisovan\u00edm aktu\u00e1lnej verzie obrazu pri op\u00e4tovnom spusten\u00ed zostaven\u00ed pre star\u00e9 Git-commity vetvy.<\/li>\n<\/ul>\n<p>\nTeraz je to odpor\u00fa\u010dan\u00e1 strat\u00e9gia tagovania a pou\u017e\u00edva sa predvolene v werf pre v\u0161etky CI syst\u00e9my.<\/p>\n<h2>Ako zapn\u00fa\u0165 a pou\u017e\u00edva\u0165 v werf<\/h2>\n<p>\nPr\u00edslu\u0161n\u00e1 mo\u017enos\u0165 sa objavila u pr\u00edkazu <code>werf publish<\/code>: <code>--tag-by-stages-signature=true|false<\/code><\/p>\n<p>V CI syst\u00e9me sa strat\u00e9gia tagovania nastavuje pr\u00edkazom <code>werf ci-env<\/code>. Predt\u00fdm bol pre \u0148u definovan\u00fd parameter <code>werf ci-env --tagging-strategy=tag-or-branch<\/code>. Teraz, ak je zadan\u00e9 <code>werf ci-env --tagging-strategy=stages-signature<\/code> alebo neud\u00e1va\u0165 t\u00fato mo\u017enos\u0165, werf predvolene pou\u017eije strat\u00e9giu ozna\u010dovania <code>stages-signature<\/code>. Pr\u00edkaz <code>werf ci-env<\/code> automaticky nastav\u00ed potrebn\u00e9 zna\u010dky pre pr\u00edkaz <code>werf build-and-publish<\/code> (alebo <code>werf publish<\/code>), preto nie je potrebn\u00e9 ud\u00e1va\u0165 \u017eiadne \u010fal\u0161ie mo\u017enosti pre tieto pr\u00edkazy.<\/p>\n<p>Napr\u00edklad pr\u00edkaz:<\/p>\n<pre><code class=\"plaintext\">werf publish --stages-storage :local --images-repo registry.hello.com\/web\/core\/system --tag-by-stages-signature<\/code><\/pre>\n<p>\n\u2026 m\u00f4\u017ee vytvori\u0165 nasleduj\u00face obrazy:<\/p>\n<ul>\n<li> <code>registry.hello.com\/web\/core\/system\/backend:4ef339f84ca22247f01fb335bb19f46c4434014d8daa3d5d6f0e386d<\/code><\/li>\n<li> <code>registry.hello.com\/web\/core\/system\/frontend:f44206457e0a4c8a54655543f749799d10a9fe945896dab1c16996c6<\/code><\/li>\n<\/ul>\n<p>\nTu <code>4ef339f84ca22247f01fb335bb19f46c4434014d8daa3d5d6f0e386d<\/code> \u2014 je to podpis f\u00e1zy obrazu <code>backend<\/code>, a <code>f44206457e0a4c8a54655543f749799d10a9fe945896dab1c16996c6<\/code> \u2014 podpis f\u00e1zy obrazu <code>frontend<\/code>.<\/p>\n<p>Pri pou\u017eit\u00ed \u0161peci\u00e1lnych funkci\u00ed <code>werf_container_image<\/code> a <code>werf_container_env<\/code> v \u0161abl\u00f3nach Helm nie je potrebn\u00e9 ni\u010d meni\u0165: tieto funkcie automaticky vygeneruj\u00fa spr\u00e1vne n\u00e1zvy obrazov.<\/p>\n<p>Pr\u00edklad konfigur\u00e1cie v CI syst\u00e9me:<\/p>\n<pre><code class=\"plaintext\">type multiwerf &amp;&amp; source &lt;(multiwerf use 1.1 beta)\ntype werf &amp;&amp; source &lt;(werf ci-env gitlab)\nwerf build-and-publish|deploy<\/code><\/pre>\n<p>\nViac inform\u00e1ci\u00ed o konfigur\u00e1cii je k dispoz\u00edcii v dokument\u00e1cii:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.werf.io\/v1.1\/documentation\/reference\/publish_process.html#%D1%82%D0%B5%D0%B3%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%BE%D0%B1%D1%80%D0%B0%D0%B7%D0%BE%D0%B2-%D0%BF%D0%BE-%D1%81%D0%BE%D0%B4%D0%B5%D1%80%D0%B6%D0%B8%D0%BC%D0%BE%D0%BC%D1%83\">Pr\u00edru\u010dka \u2192 Publikovanie (publish)<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.werf.io\/v1.1\/documentation\/reference\/plugging_into_cicd\/overview.html#stages-signature\">Pr\u00e1ca s CI\/CD \u2192 Z\u00e1kladn\u00e9 inform\u00e1cie \u2192 stages-signature<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.werf.io\/v1.1\/documentation\/guides\/gitlab_ci_cd_integration.html#gitlab-ciyml\">Integr\u00e1cia s GitLab CI\/CD \u2192 .gitlab-ci.yml<\/a><\/noindex>.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Spolu<\/h2>\n<p><\/p>\n<ul>\n<li> Nov\u00e1 mo\u017enos\u0165 <code>werf publish --tag-by-stages-signature=true|false<\/code>.<\/li>\n<li> Nov\u00e1 hodnota mo\u017enosti <code>werf ci-env --tagging-strategy=stages-signature|tag-or-branch<\/code> (ak nie je zadan\u00e9, predvolene bude <code>stages-signature<\/code>).<\/li>\n<li> Ak sa predt\u00fdm pou\u017e\u00edvali mo\u017enosti ozna\u010dovania pod\u013ea Git commitov (<code>WERF_TAG_GIT_COMMIT<\/code> alebo mo\u017enos\u0165 <code>werf publish --tag-git-commit COMMIT<\/code>), je nevyhnutn\u00e9 prepn\u00fa\u0165 na strat\u00e9giu ozna\u010dovania <i>stages-signature<\/i>.<\/li>\n<li> Nov\u00e9 projekty je najlep\u0161ie okam\u017eite prep\u00edna\u0165 na nov\u00fa sch\u00e9mu ozna\u010dovania.<\/li>\n<li> Star\u00e9 projekty pri prechode na werf 1.1 je vhodn\u00e9 prep\u00edna\u0165 na nov\u00fa sch\u00e9mu ozna\u010dovania, av\u0161ak star\u00e1 <i>tag-or-branch<\/i> je st\u00e1le podporovan\u00e1.<\/li>\n<\/ul>\n<p>\nOzna\u010dovanie zalo\u017een\u00e9 na obsahu vyrie\u0161i v\u0161etky probl\u00e9my uveden\u00e9 v \u010dl\u00e1nku:<\/p>\n<ul>\n<li> Odolnos\u0165 n\u00e1zvu Docker tagu proti pr\u00e1zdnym Git commitom.<\/li>\n<li> Odolnos\u0165 n\u00e1zvu Docker tagu proti Git commitom, ktor\u00e9 menia pre obraz irelevantn\u00e9 s\u00fabory.<\/li>\n<li> Nesp\u00f4sobuje probl\u00e9m s prep\u00edsan\u00edm aktu\u00e1lnej verzie obrazu pri op\u00e4tovnom spusten\u00ed zost\u00e1v pre star\u00e9 Git commity pre Git vetvy.<\/li>\n<\/ul>\n<p>\nPou\u017e\u00edvajte! A nezabudnite n\u00e1s nav\u0161t\u00edvi\u0165 na <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/flant\/werf\">GitHub<\/a><\/noindex>, aby ste vytvorili issue alebo na\u0161li u\u017e existuj\u00face, pridelili plus, vytvorili PR alebo jednoducho sledovali v\u00fdvoj projektu.<\/p>\n<h2>P.S.<\/h2>\n<p>\nPre\u010d\u00edtajte si tie\u017e na na\u0161om blogu:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/493170\/\">Vydanie werf 1.1: vylep\u0161enia v zostavova\u010di dnes a pl\u00e1ny do bud\u00facnosti<\/a><\/noindex>\u00bb<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/481306\/\">Predstavujeme werf 1.0 stable: ak\u00fd je vz\u0165ah k GitOps, status a pl\u00e1ny<\/a><\/noindex>\u00bb<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/460351\/\">werf \u2014 n\u00e1\u0161 n\u00e1stroj pre CI\/CD v Kubernetes (prezenta\u010dn\u00fd a video z\u00e1znam)<\/a><\/noindex>\u00bb;<\/li>\n<li> Cyklus pozn\u00e1mok o novink\u00e1ch vo werfe:\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/476646\/\">3-way merge v werf: nasadenie v Kubernetes s Helm \u201ena steroidoch\u201c<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468049\/\">Pou\u017e\u00edvanie werfu na nasadzovanie komplexn\u00fdch Helm chartov<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/465131\/\">Podpora monorepo a multirepo vo werf a ak\u00fd m\u00e1 s\u00favis s Docker Registry<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/463613\/\">S\u00fabory Docker teraz mo\u017eno vytv\u00e1ra\u0165 v werf aj pomocou be\u017en\u00e9ho Dockerfile<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/495112\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>werf \u2014 \u043d\u0430\u0448\u0430 GitOps CLI-\u0443\u0442\u0438\u043b\u0438\u0442\u0430 \u0441 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u043c \u043a\u043e\u0434\u043e\u043c \u0434\u043b\u044f \u0441\u0431\u043e\u0440\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0430\u0432\u043a\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439 \u0432 Kubernetes. \u0412 \u0440\u0435\u043b\u0438\u0437\u0435 v1.1 \u0431\u044b\u043b\u0430 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0432 \u0441\u0431\u043e\u0440\u0449\u0438\u043a\u0435 \u043e\u0431\u0440\u0430\u0437\u043e\u0432: \u0442\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u043e\u0431\u0440\u0430\u0437\u043e\u0432 \u043f\u043e \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u043c\u043e\u043c\u0443 \u0438\u043b\u0438 content-based tagging. \u0414\u043e \u0441\u0438\u0445 \u043f\u043e\u0440 \u0442\u0438\u043f\u0438\u0447\u043d\u0430\u044f \u0441\u0445\u0435\u043c\u0430 \u0442\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0432 werf \u043f\u0440\u0435\u0434\u043f\u043e\u043b\u0430\u0433\u0430\u043b\u0430 \u0442\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 Docker-\u043e\u0431\u0440\u0430\u0437\u043e\u0432 \u043f\u043e Git-\u0442\u0435\u0433\u0443, Git-\u0432\u0435\u0442\u043a\u0435 \u0438\u043b\u0438 Git-\u043a\u043e\u043c\u043c\u0438\u0442\u0443. \u041d\u043e \u0443 \u0432\u0441\u0435\u0445 \u044d\u0442\u0438\u0445 \u0441\u0445\u0435\u043c \u0435\u0441\u0442\u044c \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0438, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":76770,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-76769","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Content-based tagging \u0432 \u0441\u0431\u043e\u0440\u0449\u0438\u043a\u0435 werf: \u0437\u0430\u0447\u0435\u043c \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442? | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-04-04T11:42:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-04T11:42:27+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Ozna\u010dovanie zalo\u017een\u00e9 na obsahu v stavite\u013eovi werf: pre\u010do a ako to funguje? | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\udd47Content-based tagging \u0432 \u0441\u0431\u043e\u0440\u0449\u0438\u043a\u0435 werf: \u0437\u0430\u0447\u0435\u043c \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442? | ProHoster","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","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-04-04T11:42:27+00:00","article:modified_time":"2020-04-04T11:42:27+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"76769","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 17:30:22","updated":"2022-09-28 05:59:33","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/76769","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=76769"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/76769\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/76770"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=76769"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=76769"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=76769"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}