{"id":38648,"date":"2019-10-31T22:25:04","date_gmt":"2019-10-31T19:25:04","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kratkoe-vvedenie-v-kustomize\/"},"modified":"2019-10-31T22:25:04","modified_gmt":"2019-10-31T19:25:04","slug":"kratkoe-vvedenie-v-kustomize","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","title":{"rendered":"Stru\u010dn\u00e9 \u00favodn\u00e9 inform\u00e1cie o Kustomize","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Pozn. prekl.<\/b>: \u010cl\u00e1nok nap\u00edsal Scott Lowe \u2014 in\u017einier s bohat\u00fdmi sk\u00fasenos\u0165ami v IT, autor alebo spoluautor siedmich kn\u00edh (v\u00e4\u010d\u0161inou o VMware vSphere). V s\u00fa\u010dasnosti pracuje v jej dc\u00e9rskej spolo\u010dnosti VMware \u2014 Heptio (prevzat\u00e1 v roku 2016), \u0161pecializuj\u00facej sa na cloudov\u00e9 v\u00fdpo\u010dty a Kubernetes. Text sl\u00fa\u017ei ako \u00favod do spr\u00e1vy konfigur\u00e1ci\u00ed pre Kubernetes pomocou technol\u00f3gie <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/\">Kustomize<\/a><\/noindex>, ktor\u00e1 bola ned\u00e1vno integrov\u00e1na do K8s.<\/i><\/p>\n<p><img decoding=\"async\" alt=\"Stru\u010dn\u00e9 \u00favodn\u00e9 inform\u00e1cie o Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/099d2281c06d7a294532a816bb6aab21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKustomize je n\u00e1stroj, ktor\u00fd umo\u017e\u0148uje pou\u017e\u00edvate\u013eom \"prisp\u00f4sobova\u0165 jednoduch\u00e9 a bez\u0161abl\u00f3nov\u00e9 YAML s\u00fabory pre r\u00f4zne ciele, pri\u010dom p\u00f4vodn\u00fd YAML zost\u00e1va nedotknut\u00fd a pou\u017eite\u013en\u00fd\" (popis prevzat\u00fd priamo z <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\">repozit\u00e1ra kustomize na GitHub<\/a><\/noindex>). Kustomize je mo\u017en\u00e9 spusti\u0165 priamo alebo, po\u010dn\u00fac Kubernetes 1.14, pou\u017ei\u0165 <code>kubectl -k<\/code> na pr\u00edstup k jeho funkci\u00e1m (aj ke\u010f vo verzii Kubernetes 1.15 je samostatn\u00e1 bin\u00e1rka nov\u0161ia ako funkcie integrovan\u00e9 v kubectl). <i>(<b>Pozn. prekl.<\/b>: S ned\u00e1vnym vydan\u00edm <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/467477\/\">Kubernetes 1.16<\/a><\/noindex> kustomize <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/1177\">podporovan\u00e9<\/a><\/noindex> take v n\u00e1stroji kubeadm.)<\/i> V tejto publik\u00e1cii chcem obozn\u00e1mi\u0165 \u010ditate\u013eov so z\u00e1kladmi kustomize.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>V jednoduch\u0161ej forme pou\u017e\u00edvania je kustomize jednoducho sadou zdrojov (YAML s\u00faborov, ktor\u00e9 definuj\u00fa objekty Kubernetes: Deployments, Services at\u010f.) spolu so zoznamom pokynov na zmeny, ktor\u00e9 je potrebn\u00e9 vykona\u0165 na t\u00fdchto zdrojoch. Podobne ako make pou\u017e\u00edva s\u00fabor pokynov obsiahnut\u00fdch v <code>Makefile<\/code>, a Docker vytv\u00e1ra kontajner na z\u00e1klade pokynov z <code>Dockerfile<\/code>, kustomize vyu\u017e\u00edva <code>kustomization.yaml<\/code> na uchov\u00e1vanie predpisov o tom, ak\u00e9 zmeny chce pou\u017e\u00edvate\u013e vykona\u0165 na sade zdrojov.<\/p>\n<p>Tu je pr\u00edklad s\u00faboru <code>kustomization.yaml<\/code>:<\/p>\n<pre><code class=\"plaintext\">resources:\n- deployment.yaml\n- service.yaml\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\nNechcem sa pok\u00fa\u0161a\u0165 op\u00edsa\u0165 v\u0161etky mo\u017en\u00e9 polia v s\u00fabore <code>kustomization.yaml<\/code> (o tom je dobre nap\u00edsan\u00e9 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/fields.md\">tu<\/a><\/noindex>), ale poskytnem kr\u00e1tke vysvetlenie konkr\u00e9tneho pr\u00edkladu:<\/p>\n<ul>\n<li> Pole <code>resources<\/code> uveden\u00ed, ktor\u00e9 (ak\u00e9 zdroje) bude kustomize meni\u0165. V tomto pr\u00edpade bude h\u013eada\u0165 zdroje v s\u00faboroch <code>deployment.yaml<\/code> a <code>service.yaml<\/code> vo svojom adres\u00e1ri (pr\u00edpadne je mo\u017en\u00e9 uvies\u0165 \u00fapln\u00e9 alebo relat\u00edvne cesty).<\/li>\n<li> Pole <code>namePrefix<\/code> prikazuje kustomize'u prida\u0165 konkr\u00e9tny prefix (v tomto pr\u00edpade \u2014 <code>dev-<\/code>) k atrib\u00fatu <code>name<\/code> v\u0161etk\u00fdch zdrojov definovan\u00fdch v poli <code>resources<\/code>. Tak\u017ee ak s\u00fa v Deployment'e pr\u00edtomn\u00e9 <code>name<\/code> s hodnotou <code>nginx-deployment<\/code>, kustomize z neho sprav\u00ed <code>dev-nginx-deployment<\/code>.<\/li>\n<li> Pole <code>namespace<\/code> prikazuje kustomize'u prida\u0165 dan\u00fd n\u00e1zov priestoru ku v\u0161etk\u00fdm zdrojom. V tomto pr\u00edpade sa Deployment a Service dostan\u00fa do priestoru n\u00e1zvu <code>v\u00fdvoj<\/code>.<\/li>\n<li> Nakoniec, pole <code>commonLabels<\/code> obsahuje s\u00fabor \u0161t\u00edtkov, ktor\u00fd bude pridan\u00fd ku v\u0161etk\u00fdm zdrojom. V na\u0161om pr\u00edklade kustomize prirad\u00ed zdrojom \u0161t\u00edtok s n\u00e1zvom <code>environment<\/code> a hodnotou <code>v\u00fdvoj<\/code>.<\/li>\n<\/ul>\n<p>\nAk pou\u017e\u00edvate\u013e vykon\u00e1 <code>kustomize build .<\/code> v adres\u00e1ri s s\u00faborom <code>kustomization.yaml<\/code> a potrebn\u00fdmi zdrojmi (t.j. s\u00fabormi <code>deployment.yaml<\/code> a <code>service.yaml<\/code>), dostane na v\u00fdstupe text s zmenami, ktor\u00e9 s\u00fa uveden\u00e9 v <code>kustomization.yaml<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"Stru\u010dn\u00e9 \u00favodn\u00e9 inform\u00e1cie o Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/f15c7ccb5f200c7e9b5a25142c364cb8.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Pozn. prekl.<\/b>: Ilustr\u00e1cia z dokument\u00e1cie projektu o \u201ejednoduchom\u201c pou\u017e\u00edvan\u00ed kustomize<\/i><\/p>\n<p>V\u00fdstup je mo\u017en\u00e9 presmerova\u0165, ak je potrebn\u00e9 zafixova\u0165 zmeny:<\/p>\n<pre><code class=\"bash\">kustomize build . &gt; custom-config.yaml<\/code><\/pre>\n<p>\nV\u00fdstupy s\u00fa deterministick\u00e9 (pri rovnak\u00fdch vstupn\u00fdch \u00fadajoch bud\u00fa v\u00fdsledky na v\u00fdstupe rovnak\u00e9), preto nie je potrebn\u00e9 uklada\u0165 v\u00fdsledok do s\u00faboru. Namiesto toho sa m\u00f4\u017ee okam\u017eite posla\u0165 do in\u00e9ho pr\u00edkazu:<\/p>\n<pre><code class=\"bash\">kustomize build . | kubectl apply -f -<\/code><\/pre>\n<p>\nPr\u00edstup k funkci\u00e1m kustomize je mo\u017en\u00e9 z\u00edska\u0165 aj cez <code>kubectl -k<\/code> (od verzie 1.14 Kubernetes). Av\u0161ak majte na pam\u00e4ti, \u017ee samostatn\u00fd bal\u00edk kustomize sa aktualizuje r\u00fdchlej\u0161ie ne\u017e integrovan\u00fd v kubectl (aspo\u0148 to je situ\u00e1cia s vydan\u00edm Kubernetes 1.15).<\/p>\n<p>\u010citatelia sa m\u00f4\u017eu p\u00fdta\u0165: \u201ePre\u010do s\u00fa v\u0161etky tieto komplik\u00e1cie, ak m\u00f4\u017eem upravova\u0165 s\u00fabory priamo?\u201c. V\u00fdborn\u00e1 ot\u00e1zka. V na\u0161om pr\u00edklade je naozaj <i>mo\u017en\u00e9<\/i> modifikova\u0165 s\u00fabory <code>deployment.yaml<\/code> a <code>service.yaml<\/code> priamo, ale \u010do ak s\u00fa forkmi niekoho projektu? Priame \u00fapravy s\u00faborov s\u0165a\u017euj\u00fa (ak nie \u00faplne znemo\u017e\u0148uj\u00fa) rebase forku, ke\u010f sa vykon\u00e1vaj\u00fa zmeny v zdroji\/zdrojovom k\u00f3de. Pou\u017e\u00edvanie kustomize umo\u017e\u0148uje centralizova\u0165 tieto zmeny v s\u00fabore <code>kustomization.yaml<\/code>, pri\u010dom p\u00f4vodn\u00e9 s\u00fabory zost\u00e1vaj\u00fa nedotknut\u00e9 a tak u\u013eah\u010duje pri potreby rebase p\u00f4vodn\u00fdch s\u00faborov.<\/p>\n<p>V\u00fdhody kustomize sa st\u00e1vaj\u00fa zrejm\u00fdmi vo zlo\u017eitej\u0161\u00edch pr\u00edpadoch pou\u017eitia. V uvedenom pr\u00edklade <code>kustomization.yaml<\/code> a zdroje s\u00fa v rovnakom adres\u00e1ri. Kustomize v\u0161ak podporuje scen\u00e1re pou\u017eitia, ke\u010f existuje z\u00e1kladn\u00e1 konfigur\u00e1cia a mno\u017estvo jej variantov, tie\u017e zn\u00e1mych ako <i>overlays<\/i>. Napr\u00edklad pou\u017e\u00edvate\u013e sa rozhodol vzia\u0165 Deployment a Service pre nginx, ktor\u00e9 som pou\u017eil ako pr\u00edklad, a vytvori\u0165 v\u00fdvojov\u00e9, stagingov\u00e9 a produk\u010dn\u00e9 verzie (alebo varianty) t\u00fdchto s\u00faborov. Na to potrebuje vy\u0161\u0161ie uveden\u00e9 overlay a samotn\u00e9 z\u00e1kladn\u00e9 zdroje.<\/p>\n<p>Na ilustr\u00e1ciu konceptu overlays a z\u00e1kladn\u00fdch zdrojov <i>(z\u00e1kladn\u00e9 zdroje)<\/i>, predpokladajme, \u017ee adres\u00e1re maj\u00fa nasleduj\u00facu \u0161trukt\u00faru:<\/p>\n<pre><code class=\"plaintext\">- base\n  - deployment.yaml\n  - service.yaml\n  - kustomization.yaml\n- overlays\n  - dev\n    - kustomization.yaml\n  - staging\n    - kustomization.yaml\n  - prod\n    - kustomization.yaml<\/code><\/pre>\n<p>\nV s\u00fabore <code>base\/kustomization.yaml<\/code> pou\u017e\u00edvatelia pomocou po\u013ea <code>resources<\/code> jednoducho vyhlasuj\u00fa zdroje, ktor\u00e9 by mal kustomize zahrn\u00fa\u0165.<\/p>\n<p>V ka\u017edom z s\u00faborov <code>overlays\/{dev,staging,prod}\/kustomization.yaml<\/code> pou\u017e\u00edvatelia odkazuj\u00fa na z\u00e1kladn\u00fa konfigur\u00e1ciu v poli <code>resources<\/code>, a potom uv\u00e1dzaj\u00fa konkr\u00e9tne zmeny pre <i>toto prostredie<\/i>. Napr\u00edklad s\u00fabor <code>overlays\/dev\/kustomization.yaml<\/code> m\u00f4\u017ee vyzera\u0165 ako pr\u00edklad uveden\u00fd vy\u0161\u0161ie:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/..\/base\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\nZ\u00e1rove\u0148 s\u00fabor <code>overlays\/prod\/kustomization.yaml<\/code> m\u00f4\u017ee by\u0165 \u00faplne in\u00fd:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/..\/base\nnamePrefix: prod-\nnamespace: production\ncommonLabels:\n  environment: production\n  sre-team: blue<\/code><\/pre>\n<p>\nKe\u010f pou\u017e\u00edvate\u013e spust\u00ed <code>kustomize build .<\/code> v adres\u00e1ri <code>overlays\/dev<\/code>, kustomize vygeneruje variant development. Ak sa v\u0161ak spust\u00ed <code>kustomize build .<\/code> v adres\u00e1ri <code>overlays\/prod<\/code> , v\u00fdsledkom bude variant production. A toto v\u0161etko \u2014 bez ak\u00fdchko\u013evek zmien v p\u00f4vodn\u00fdch <i>(z\u00e1kladn\u00fdch)<\/i> s\u00faboroch, a to v\u0161etko \u2014 deklarat\u00edvne a deterministicky. Je mo\u017en\u00e9 commita\u0165 z\u00e1kladn\u00fa konfigur\u00e1ciu a overlay adres\u00e1re priamo do syst\u00e9mu spr\u00e1vy verzi\u00ed, s vedom\u00edm, \u017ee na z\u00e1klade t\u00fdchto s\u00faborov je mo\u017en\u00e9 kedyko\u013evek reprodukova\u0165 potrebn\u00fa konfigur\u00e1ciu.<\/p>\n<p><img decoding=\"async\" alt=\"Stru\u010dn\u00e9 \u00favodn\u00e9 inform\u00e1cie o Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/959af6422f6ae4c1b8d755e9c5728d38.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Pozn. prekl.<\/b>: Ilustr\u00e1cia z dokument\u00e1cie projektu o pou\u017eit\u00ed overlays v kustomize<\/i><\/p>\n<p>Kustomize zvl\u00e1dne <i>ove\u013ea<\/i> viac, ako je uveden\u00e9 v tomto \u010dl\u00e1nku. D\u00fafam v\u0161ak, \u017ee posl\u00fa\u017ei ako dobr\u00fd \u00favod.<\/p>\n<h2>\u010eal\u0161ie zdroje<\/h2>\n<p>\nExistuje mno\u017estvo dobr\u00fdch \u010dl\u00e1nkov a publik\u00e1ci\u00ed o kustomize. Tu je nieko\u013eko, ktor\u00e9 som pova\u017eoval za zvl\u00e1\u0161\u0165 u\u017eito\u010dn\u00e9:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/levelup.gitconnected.com\/kubernetes-change-base-yaml-config-for-different-environments-prod-test-6224bfb6cdd6\">Zmena z\u00e1kladnej YAML konfigur\u00e1cie pre r\u00f4zne prostredia prod\/test pomocou Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.stack-labs.com\/code\/kustomize-101\/\">Kustomize \u2014 Spr\u00e1vny sp\u00f4sob, ako robi\u0165 templating v Kubernetes<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/manage-kubernetes-objects\/kustomization\/\">Deklarat\u00edvne riadenie objektov Kubernetes pomocou Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/testingclouds.wordpress.com\/2018\/07\/20\/844\/\">Prisp\u00f4sobovanie upstream Helm grafov pomocou Kustomize<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\n<i><b>Pozn. prekl.<\/b>: Takisto m\u00f4\u017eem odporu\u010di\u0165 blok odkazov, publikovan\u00fdch ako <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/#resources\">Zdroje<\/a><\/noindex> na str\u00e1nke n\u00e1stroja a n\u00e1sledn\u00fa kolekciu vide\u00ed s posledn\u00fdmi predn\u00e1\u0161kami o kustomize.<\/i><\/p>\n<p>Ak m\u00e1te ak\u00e9ko\u013evek ot\u00e1zky alebo n\u00e1vrhy na zlep\u0161enie tohto materi\u00e1lu, som v\u017edy otvoren\u00fd sp\u00e4tnej v\u00e4zbe. Spoji\u0165 sa so mnou m\u00f4\u017eete v <noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/scott_lowe\">Twitter<\/a><\/noindex> alebo na <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.slack.com\/\">Slack kan\u00e1li Kubernetes<\/a><\/noindex>. U\u017eite si prisp\u00f4sobenie svojich manifestov pomocou kustomize!<\/p>\n<h2>P.S. od prekladate\u013ea<\/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\/462707\/\">N\u00e1stroje pre v\u00fdvoj\u00e1rov aplik\u00e1ci\u00ed be\u017eiacich v Kubernetes<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/445196\/\">Kubernetes 1.14: preh\u013ead hlavn\u00fdch noviniek<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468259\/\">P\u00e4\u0165 hlavn\u00fdch z\u00e1verov Helm Summit 2019 v Amsterdame<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/420437\/\">Praktick\u00e9 obozn\u00e1menie sa so spr\u00e1vcom bal\u00edkov pre Kubernetes \u2013 Helm<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/469179\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere). \u0421\u0435\u0439\u0447\u0430\u0441 \u043e\u043d \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0432 \u0435\u0451 \u0434\u043e\u0447\u0435\u0440\u043d\u0435\u0439 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 VMware \u2014 Heptio (\u043f\u043e\u0433\u043b\u043e\u0449\u0435\u043d\u0430 \u0432 2016 \u0433\u043e\u0434\u0443), \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0437\u0438\u0440\u0443\u044f\u0441\u044c \u043d\u0430 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f\u0445 \u0438 Kubernetes. \u0421\u0430\u043c \u0436\u0435 \u0442\u0435\u043a\u0441\u0442 \u0441\u043b\u0443\u0436\u0438\u0442 \u0451\u043c\u043a\u0438\u043c \u0438 \u043f\u0440\u043e\u0441\u0442\u044b\u043c \u0434\u043b\u044f \u043f\u043e\u043d\u0438\u043c\u0430\u043d\u0438\u044f \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435\u043c \u0432 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u044f\u043c\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28991,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38648","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=\"description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere).\" \/>\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\/kratkoe-vvedenie-v-kustomize\" \/>\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\udd47\u041a\u0440\u0430\u0442\u043a\u043e\u0435 \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 Kustomize | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere).\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize\" \/>\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=\"2019-10-31T19:25:04+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:25:04+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\udd47Stru\u010dn\u00fd \u00favod do Kustomize | ProHoster","description":"Pozn\u00e1mka: \u010cl\u00e1nok nap\u00edsal Scott Lowe \u2014 in\u017einier s bohat\u00fdmi sk\u00fasenos\u0165ami v IT, ktor\u00fd je autorom\/spoluautorom siedmich tla\u010den\u00fdch kn\u00edh (predov\u0161etk\u00fdm o VMware vSphere).","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","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\udd47\u041a\u0440\u0430\u0442\u043a\u043e\u0435 \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 Kustomize | ProHoster","og:description":"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere).","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","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":"2019-10-31T19:25:04+00:00","article:modified_time":"2019-10-31T19:25:04+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38648","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":"2026-01-23 22:54:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:05:23","updated":"2026-01-23 22:54:19","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\/38648","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=38648"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/38648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/28991"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=38648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=38648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=38648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}